Operate
Start with the live operating surfaces
| Surface | Use it for | Operator check |
|---|---|---|
| Control | Concierge-assisted coordination, workflow drafts, queues, and intervention. | Confirm the selected workspace and project before launching or changing work. |
| Workflow Manager | Canvas and inspector for first-class workflow runs (/workflow-manager), stage progress, and execution-map detail. | Opened from Control navigation; keep project scope in the query string. |
| Dashboard | Workspace summary, attention signals, provider readiness, and recent activity. | Use it for orientation, then open the owning record for action. |
| Agents | Agent identity, team, task, capabilities, runtime route, readiness, and status. | Do not equate an online heartbeat with complete spawn or repository readiness. |
| Roles | Built-in responsibilities and the operating expectations assigned to agents. | Use roles for responsibility boundaries; use Teams for project staffing. |
| Fleets | Team topology, capacity, leadership, activity, and fleet health. | Separate stale heartbeat signals from agents that are intentionally idle. |
| Concierge | Persistent operator conversations and permissioned workspace tools. | Provider access and workspace tool policy must be ready before write actions work. |
Deliver
Use durable records for the delivery path
| Surface | Source of truth | What belongs there |
|---|---|---|
| Projects and Epics | Scope and planned outcomes. | Repository context, owner, acceptance criteria, dependencies, and related work. |
| People | Workspace participants and their membership context. | Use Settings and Team Members for membership administration. |
| Handoffs | Responsibility transfer between people and agents. | Current owner, acceptance context, required evidence, and completion state. |
| Workflows: Runs, Observability, and Settings | Execution history, current health signals, and workflow configuration inventory. | Use Runs for diagnosis, Observability for measured health and instrumentation gaps, and Settings for owned configuration links. |
| Claims | Leased work scope. | Files, branches, tasks, or runtime areas currently owned by an agent. |
| Blockers and Approvals | Stopped decisions and risk gates. | The missing input, decision owner, resolution, and evidence needed to continue. |
| PRs | Repository delivery evidence. | Review state, CI, merge readiness, and linked work context. |
| Logs and Metrics | Operational evidence. | Runtime events, trends, latency, throughput, and health signals. |
Configure
Connect providers, repositories, and runtime infrastructure
| Surface | Use it for | Related guide |
|---|---|---|
| Providers | Provider credentials, model availability, runtime grants, and readiness. | Check readiness before starting an agent or Concierge session. |
| Integrations | GitHub, Slack, and other external connection state. | Repositories and PATs |
| Infrastructure | Runtime bundle, endpoints, route checks, host registration, and repair actions. | Provisioning and runtime operations |
| System Map | Super-admin-only Tools surface for live service topology, dependency edges, and redacted request flow. | Hidden unless is_super_admin is enabled for the participant. |
| Deployments | Deployment targets and observed deployment state. | Treat repository CI and environment evidence as the final proof. |
| Settings | Workspaces, Team Members, Workspace policy, Notifications, API Keys, and Review Policy. | API and auth |
Visibility is not permission.
A page may show an object that your role cannot change. Destructive, credential, infrastructure, and approval actions remain subject to participant role, API-key scope, workspace policy, and explicit confirmation.