mirror of https://github.com/rennf93/roboco.git synced 2026-08-03 07:23:24 +02:00

Files

T

Renn F d25994f87b fix(panel): dedupe notifications by id in the store

addNotification prepended every delivery and re-incremented unreadCount /
pendingAckCount, so a re-fetched or replayed notification stacked duplicates
and re-inflated the counts — already-acknowledged notifications re-surfaced to
the CEO and the pending badge kept climbing. Dedupe by id: update in place on
re-delivery; only add + count a genuinely new notification.

2026-06-04 06:47:30 +02:00

lib

fix(lifecycle): unblock a never-claimed task to pending, not branchless in_progress

2026-06-04 02:01:09 +02:00

public

I mean, it's at a good place rn...

2026-04-20 15:10:54 +02:00

src

fix(panel): dedupe notifications by id in the store

2026-06-04 06:47:30 +02:00

.dockerignore

I mean, it's at a good place rn...

2026-04-20 15:10:54 +02:00

.gitignore

I mean, it's at a good place rn...

2026-04-20 15:10:54 +02:00

components.json

I mean, it's at a good place rn...

2026-04-20 15:10:54 +02:00

eslint.config.mjs

I mean, it's at a good place rn...

2026-04-20 15:10:54 +02:00

next.config.ts

I mean, it's at a good place rn...

2026-04-20 15:10:54 +02:00

package.json

Many fixes and cleanups

2026-05-09 03:15:09 +02:00

pnpm-lock.yaml

I mean, it's at a good place rn...

2026-04-20 15:10:54 +02:00

pnpm-workspace.yaml

Many fixes and cleanups

2026-05-09 03:15:09 +02:00

postcss.config.mjs

I mean, it's at a good place rn...

2026-04-20 15:10:54 +02:00

README.md

I mean, it's at a good place rn...

2026-04-20 15:10:54 +02:00

tsconfig.json

I mean, it's at a good place rn...

2026-04-20 15:10:54 +02:00

README.md

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.