roboco/panel

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-kit for 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 reload
• pnpm build — production build (outputs .next/standalone/)
• pnpm start — run the standalone build
• pnpm lint — ESLint

Where things live

• src/app/ — Next.js App Router pages
• src/components/ — React components (organized by feature: tasks, agents, channels, …)
• src/lib/api/ — typed API client (thin wrappers over fetch)
• src/lib/ — constants, utilities, WebSocket hooks
• src/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.