Dashboard & frontend integration

Audience: UI/UX engineers and frontend contributors; also useful for anyone documenting what ships in adros-app vs what is live on app.adros.ai after deploy.

Backend endpoints (verify on `https://api.adros.ai/api/v1`)

Chat agent

POST /chat — send a message and get full response
WS /ws/chat — streaming chat response
GET /chat/memories — memory debug endpoint
Auth: Authorization: Bearer <user_mcp_token> (and routing variants as documented in OpenAPI)

Command Center / orchestration

GET /projects — list projects
GET /projects/{id}/tasks — list tasks with subtasks
GET /tasks/{id}/events — task activity feed (confirm ordering/limit behavior against OpenAPI and production)
POST /audits/trigger — trigger audit
POST /tasks/{id}/approve — approve task
POST /tasks/{id}/reject — reject task with feedback
GET /approvals/pending — pending approvals queue
WS /ws/events/{task_id}?token=<mcp_token> — real-time event stream (when enabled)

Files (R2)

File APIs are implemented in backend (api/services/file_storage.py and routes under /api/v1/files — see live OpenAPI). The dashboard Files page targets these endpoints for upload and browse.

Until your environment has R2 env vars configured (R2_ACCOUNT_ID, R2_ACCESS_KEY_ID, R2_SECRET_ACCESS_KEY, bucket), uploads will fail with a clear configuration error — not a missing-route404.

Audit quality track

Scorecards, guardrails, and artifact persistence depend on migration + AUDIT_QUALITY_TRACK_ENABLED. Treat as deploy-dependent; verify on staging/production before documenting customer-facing guarantees.

Reference: routes and source files

Use this page for routing and API alignment. Visual design may live in your own design system; the paths below map product areas to adros-app entrypoints.

Frontend implementation snapshot (`adros-app`)

Primary routes are declared in client/src/App.tsx:

Command Center: CommandCenter at /dashboard and /command-center
Strategy Workspace: Workspace at /workspace
Chat panel (in Command Center layout): client/src/components/command-center/ChatPanel.tsx
Campaign metrics: client/src/pages/Campaigns.tsx
Approvals page: client/src/pages/Approvals.tsx (/approvals)
Files: client/src/pages/Files.tsx (/files)
CEO: client/src/pages/Ceo.tsx (/ceo)
API Keys / MCP + provider BYOK setup: client/src/pages/ApiKeys.tsx (/api-keys)
API helpers: client/src/lib/api.ts
Sidebar / nav: client/src/components/DashboardLayout.tsx

Legacy or parallel: client/src/pages/Dashboard.tsx may still exist in some branches; the routed Command Center entrypoint is CommandCenter.tsx.

Rollback safety

If your repo keeps backup snapshots under adros-app/backups/, use them only for emergency rollback — prefer git history for normal work.

Immediate next step

Run local build/smoke on adros-app and hit the routes above against your target API base URL.
After Railway/Vercel deploy, confirm Files upload + Command Center timeline + Campaigns scope notices on a real test client.

REST — Dashboard & Orchestration Onboarding Flows