Files

Richard Palethorpe b5a12a1da6 feat(ui): Structured observability/status view (#40 )

* refactor(ui): Make message status SSE name more specific

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

* feat(ui): Add structured observability events

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

---------

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

2025-04-18 17:32:43 +02: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

feat(ui): Structured observability/status view (#40 )

2025-04-18 17:32:43 +02:00

.gitignore

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

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

bun.lock

feat(ui): Structured observability/status view (#40 )

2025-04-18 17:32:43 +02: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): Structured observability/status view (#40 )

2025-04-18 17:32:43 +02: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): Proxy avatars endpoint in dev mode (#32 )

2025-04-14 16:09:57 +02: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.