Renn F
48aa4f7c14
openStream registered listeners for the server-sent event kinds but not the EventSource's own transport-level error. The 'error' kind IS in LIVE_EVENT_KINDS, so a server-sent event:error (JSON MessageEvent) was handled — but a dropped connection / dead session fires a plain Event with NO data, which JSON.parse(undefined) swallowed in the try/catch, so the stream 'stayed open' (EventSource loop-reconnected a session that no longer existed) and isSending stayed true — the composer was permanently disabled. Fix: route the 'error' event by payload. A MessageEvent with string data is a server-sent error → handleEvent (unchanged). A no-data Event is a transport error → handleTransportError: clear streamingId/activity, set isSending false, add a 'connection lost' error message, keep a draft/batch preview up (so the human can still act on a proposed card) else land on 'chatting', and close the dead stream so EventSource stops loop-reconnecting. Tests: renderHook + a jsdom EventSource double that fires a transport error (plain Event, no data) vs a server-sent error (MessageEvent + JSON). RED: transport error left isSending true; GREEN: resets to false, surfaces the message, closes the stream. The server-sent-JSON path is unchanged. Full panel suite (129) green; eslint/typecheck/prettier clean.
RoboCo Control Panel
Next.js 16 control panel for the RoboCo AI agent system. Formerly a separate repository (rennf93/roboco-panel), now vendored under panel/ in this monorepo so docker compose up -d brings up the whole stack from one place.
Stack
- Next.js 16 (App Router, standalone output)
- TypeScript
- Tailwind CSS
- Radix UI primitives
dnd-kitfor drag/drop (kanban)- pnpm for package management
Running in production (the normal path)
Use the root-level Docker Compose:
# from the repo root (one level up from this directory)
docker compose up -d
The panel is built as part of the compose stack via docker/panel.Dockerfile and served internally on port 3000. Nginx (also in the compose stack) is the single externally-exposed service on http://localhost:3000 and routes:
/api/*and/ws/*→ orchestrator (FastAPI, port 8000)- everything else → the Next.js panel
The panel uses relative URLs (/api/v1, /ws) so nothing here needs a backend URL in .env.
Running the panel alone for UI development
cd panel
pnpm install
pnpm dev
That gives you Next dev-server on localhost:3000, but you still need the orchestrator reachable at localhost:8000 (or via nginx) for API calls to work. Easiest: docker compose up -d the backend services, then run pnpm dev against that.
Build scripts
pnpm dev— development server with hot reloadpnpm build— production build (outputs.next/standalone/)pnpm start— run the standalone buildpnpm lint— ESLint
Where things live
src/app/— Next.js App Router pagessrc/components/— React components (organized by feature: tasks, agents, channels, …)src/lib/api/— typed API client (thin wrappers overfetch)src/lib/— constants, utilities, WebSocket hookssrc/types/— shared TypeScript types mirroring backend schemas
Backend schema changes
When the backend changes response shapes, mirror them in src/types/ and the relevant src/lib/api/ module. Keep API paths relative so nginx routing keeps working.