Overview
Cockpit is the control plane for a workspace where agents do the work and people decide. Agents propose records, drafts, and task changes. A person approves or rejects those proposals. The database keeps the decision.
Cloudbeast.io LLC publishes Cockpit for technical operators and builders. There is no managed service in this version. You run it yourself: a Next.js app on top of your own Supabase project (Postgres, Auth, and Edge Functions). Feature behavior is the same on every install. There are no edition splits.
What you use it for
- Review a queue of agent proposals, one card at a time or as a list.
- Track tasks across a board, assign them to people or agent runtimes, and close them with an explicit human gate when you want one.
- Keep accounts, contacts, deals, campaigns, and projects in one place, with an activity history behind them.
- Connect agents over MCP with personal access tokens, and wake them from desks and routines.
- Search records by name from the top bar, and ask questions over indexed text from chat.
The app
After you sign in, the sidebar is the map. The home redirect sends an authenticated session to /dash unless the deploy sets COCKPIT_HOME.
| Section | Screens |
|---|---|
| Quick | Dash, Goals, Approvals, Calendar |
| Relationships | Accounts, Contacts, Activities, Territories |
| Marketing | Content, ICP, Assets |
| Sales | Campaigns, Pipeline, Deals, Products |
| Work | Desks, Tasks, Work Items, Pull requests |
| Support | Cases |
| Agents | Agents, Routines, Knowledge, Queues, Logs |
| Automations | LLMs, Classifiers, Decision flows, Decisions, Workflows |
| Admin | Integrations, API keys, Users, Permission sets, Domains, Approval types, KG Health, Meeting pipeline, Notifications |
A few surfaces are not in the sidebar. /chat is the knowledge-graph chat. Comments are the handoff inbox between people and agents. Most lists open an entity drawer for the record you click.
Two Automations screens are early. LLMs is a placeholder. Classifiers shows usage stats and does not yet edit classifier definitions. Decision flows lists declared flows; the graph editor is on /decisions/<flowKey>.
How the pieces fit
The app never writes the database tables directly from the browser. It calls a session API under /cockpit/api. Agents call a separate MCP endpoint with a bearer token. Both sides land on the same Postgres functions, so a card you approve in the UI is the same row an agent created.
Read Core concepts for the object model, then Quickstart for the first session. Self-host install is in preview and is not linked from these pages.