The cockpit-agent bridge uses server-injected context; the server also adds bin/ to panel PATH. Run it inside a Cockpit terminal associated with a mission:
cockpit-agent list
cockpit-agent tasks
cockpit-agent task builder "Implement form validation"
cockpit-agent delegate reviewer "Review form" --description "Check changed files and the contract; report findings with file and line."
cockpit-agent send <PANEL_ID> "Implementation ready for review"
cockpit-agent wait <TASK_ID>
cockpit-agent result <RUN_ID> completed "Describe delivery and checks actually performed"
| Action | Usage |
|---|---|
list | Mission panels. |
tasks | Mission tasks. |
task <role> <title> | Create a task with a suggested role. |
delegate <panel-or-role> <title> [--description <context>] | Delegate within connections and limits. Description is one quoted argument at the end. |
send <panel> <message> | Message a member. |
wait <task> | Wait for in-review, complete, failed, or blocked; inspect the returned state. |
inspect <run> | Read a mission delivery's workspace, baseline, and persisted review diff. |
review <run> <approved|changes_requested|rejected> <reason> | Maestro, Reviewer, Verifier, or Security records an evidence-based decision on another agent's delivery. No self-review. |
result <run> <state> <summary> | States: completed, blocked, failed, cancelled. |
Use completed when task criteria are met, blocked for an impediment, failed for failure, and cancelled for authorized cancellation. Run results, reviews, and task completion are separate steps. Escape external text correctly before passing it to a shell.
MCP's cockpit_wait stays pending until delivery, blocking, or failure. Transport checks happen inside the bridge without returning intermediate states to the model. Canceling the call stops waiting without canceling specialist work. New Codex sessions receive mcp_servers.cockpit.tool_timeout_sec=86400 (24 hours); existing sessions must reconnect the bridge and load new settings. Other MCP clients must permit long waits or renew timeouts on progress notifications.
cockpit_team includes current roles and roles permitted for autonomous creation. cockpit_delegate accepts expectedDeliverable, acceptanceCriteria, allowedFiles, and dependencies. Specialists receive workspace, baseline, task, deliverables, and explicit restrictions. In Directed/Autonomous modes, only Maestro delegates; specialists use cockpit_send to communicate needs. Architect works read-only and sends designs to Maestro for Builder to implement.
cockpit_inspect and cockpit_review connect team review to the existing gate: a completed delivery stays in-review until a decision is recorded. The executor's report never triggers automatic approval. Contracts guide agents; they are neither runner write isolation nor automatic proof of acceptance criteria.