Cockpit docs
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.
Getting started
- Overview
What Cockpit is, who it is for, and how the screens are organized.
- Core concepts
Agents propose, humans approve, and the objects Cockpit keeps in between.
- Quickstart
Sign in, create a task, and open the approval queue.
Features
- Approvals
How agent cards work, and how to approve or reject them.
- Meetings and extraction
Where meetings show up, and how extraction proposals get reviewed.
- Workflows
Workflow templates, what a trigger does today, and how to run one.
- Deals and pipeline
The deal board, the campaign pipeline, and the fields on a deal.
- Search
Name search in the top bar versus semantic search over indexed text.
- Connecting agents
Runtimes, personal access tokens, and the MCP endpoint.
- Users and members
Workspace roles, invites, and what a member can do.
Reference
- MCP tools
Every MCP tool, its scope, and the parameters you pass.
- Permissions and API keys
Personal access tokens, scopes, permission sets, and who can resolve a card.
- Entity fields
Allowed fields and values for approval cards and the main records.
- HTTP API
Session routes under /cockpit/api, plus the MCP and ingest endpoints.