Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/openai/codex-plugin-cc/llms.txt

Use this file to discover all available pages before exploring further.

​
How thread tracking works

The plugin tracks Codex task threads per repository. Each time a /codex:rescue task completes, its threadId is stored in the repository’s job state. This lets you continue the same Codex thread in a later request rather than always starting from scratch.
Thread resumption only applies to task threads (from /codex:rescue). Review jobs (/codex:review, /codex:adversarial-review) are always one-shot and are never resumable.

​
Resuming automatically

When you run /codex:rescue without --resume or --fresh, the plugin checks whether a resumable thread exists for the current Claude session. If one is found, it asks exactly once:
  • “Continue current Codex thread”
  • “Start a new Codex thread”
For follow-up phrasing like “continue”, “keep going”, “apply the top fix”, or “dig deeper” — the Continue option is recommended automatically. Otherwise, Start a new thread is recommended.

​
Explicit resume

Use --resume to skip the prompt and always continue the last thread: 
/codex:rescue --resume apply the top fix from the last run

​
Explicit fresh start

Use --fresh to skip the prompt and always start a new thread: 
/codex:rescue --fresh start over with a clean investigation

​
Resuming in Codex directly

After any task finishes, /codex:result includes the Codex session ID. Use it to open that run directly in the Codex interface: 
codex resume <session-id>
This lets you review what Codex did or continue the work with the full Codex interface — outside of Claude Code.
If a task is still queued or running, attempting to resume it will error. Run /codex:status first to confirm the task has finished before continuing.

Build docs developers (and LLMs) love

Get started for freeTalk to us