Files

Richard Palethorpe 18364d169e fix(ui): Don't convert form inputs from string

Action, connector, MCP, dynamic prompts and anything else that is
stored as an array in the config; their fields are always stored
as string by the backend.

Signed-off-by: Richard Palethorpe <io@richiejp.com>

2025-04-07 14:02:38 +01:00

.vite/deps

feat(ui): Add dynamic prompt config

2025-04-01 14:36:33 +01:00

public

chore(README): update (#133 )

2025-04-03 17:35:07 +02:00

src

fix(ui): Don't convert form inputs from string

2025-04-07 14:02:38 +01:00

.gitignore

feat(ui): Add React based UI for the vibes at /app

2025-03-26 06:34:32 +00:00

bun.lockb

feat(ui): Add React based UI for the vibes at /app

2025-03-26 06:34:32 +00:00

eslint.config.js

feat(ui): Add React based UI for the vibes at /app

2025-03-26 06:34:32 +00:00

index.html

chore(README): update (#133 )

2025-04-03 17:35:07 +02:00

package.json

feat(ui): Add React based UI for the vibes at /app

2025-03-26 06:34:32 +00:00

README.md

feat(ui): Add React based UI for the vibes at /app

2025-03-26 06:34:32 +00:00

vite.config.js

fix(ui): Loading .env

2025-04-01 14:36:33 +01:00

README.md

React + Vite

This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.

Currently, two official plugins are available:

@vitejs/plugin-react uses Babel for Fast Refresh
@vitejs/plugin-react-swc uses SWC for Fast Refresh

Expanding the ESLint configuration

If you are developing a production application, we recommend using TypeScript and enable type-aware lint rules. Check out the TS template to integrate TypeScript and typescript-eslint in your project.