autopilot-codex

Use when running an active autopilot-codex session — explains the plan→implement→review→verdict cycle, state machine, and termination conditions. Required reading when status='running' and the implementer needs to act inside the loop.

Use when interpreting state mutations during plan/review/verdict transitions — explains exactly which fields the bridge writes when, so the implementer can debug 'why is current_task suddenly T3' or 'why is base_sha old'.

Use when deciding whether a question warrants spawning a Codex turn or you can answer locally — covers the cost/value matrix and which subagent or command is the right entry point for each kind of consultation.

Use whenever you're about to run a destructive Bash command, push code, or spend Codex tokens — explains every cap and denylist this plugin enforces and how to extend them.

Use whenever the user invokes /autopilot-codex:* in this repo, OR mentions "autopilot", "Codex manager", "Codex architect", or asks Codex to plan/review for them. Establishes the role split — OpenAI Codex is manager/architect, Claude Code is implementer — and the operating contract.