Once several coding agents are working in parallel, “what should run next?” stops being a prompt and becomes a control-plane question. Chat history is a poor source of truth for dependencies, decisions, stale handoffs, and work that is technically ready but unsafe to dispatch.

Agent Cockpit stores that state in the repository that owns the work. It reads versioned work orders, dependencies, decisions, handoffs, and health checks, then separates hard blockers from degraded signals. A missing approval can stop dispatch; a stale but noncritical signal can warn without freezing everything.

The CLI and synthetic demo exercise the model, including checks against the repository’s own GitHub Actions state. It does not run agents, coordinate writes across repositories, or claim production adoption. Its job is narrower: make dispatch readiness inspectable and reviewable before another agent starts changing code.

Read the design

• Quick start and live-check behavior
• Trust-state dispatch semantics
• Repository-local execution boundary
• Subagent dispatch standard