Mission Control Debug

Mission Control Debug

Purpose

Diagnose stuck or failed orchestration and surface recovery options.

The Codex chat agent is not the Mission Control Manager. It is the bridge between the user and the Mission Control Manager.

Use when

• The user says the run is stuck or broken.
• Status looks stalled.
• Approvals, diagnostics, or event summaries need to be correlated.

Workflow

1. Fetch status with mission_control_get_status.
2. Fetch pending decisions with mission_control_get_pending_decisions.
3. Fetch diagnostics and recent event digest.
4. Ask Mission Control for a recovery plan if available.
5. Summarize blocker, likely causes, and next options.

Mission Control calls

Tools:

• mission_control_get_status
• mission_control_get_pending_decisions
• mission_control_get_event_digest
• mission_control_request_recovery_plan

Resources:

• mission-control://projects/{project_id}/status
• mission-control://projects/{project_id}/diagnostics
• mission-control://projects/{project_id}/pending-decisions

User-facing output

• State the main blocker, supporting evidence, pending approvals, and recommended next options.
• Keep diagnostics summarized; do not paste raw logs by default.

Approval behavior

If recovery choices may retry commands, widen scope, or restart work, relay the decision to the user before acting.

Never do

• Do not freehand a recovery action that Mission Control has not approved.
• Do not dump raw logs or secrets.
• Do not say the system is healthy when diagnostics disagree.

Failure and fallback

If recovery tooling is missing, summarize the failure from status, diagnostics, and events, and clearly mark recovery-plan tooling as expected or future.

Example invocation

Mission Control looks stuck. Diagnose it and show my options.