resume

name	resume
description	Continue a previous Codex thread with a follow-up instruction. Use for "/codex-bridge:resume [thread-id|--last] <follow-up>".
argument-hint	[<thread-id> | --last] [--write] <follow-up instruction>
disable-model-invocation	true
allowed-tools	Bash(node:*), Read

Continue an existing Codex thread so Codex keeps its own context instead of re-reading everything.

Steps

1. Parse $ARGUMENTS: an optional thread id (uuid-like) or --last, optional --write, and the follow-up text. Default to --last.
2. If the last run was ephemeral, resume --last fails with a clear error; explain that only persisted threads (implement preset, or --persist) can be resumed, and offer to run the task fresh.
3. Run:

   node "${CLAUDE_PLUGIN_ROOT}/scripts/codex-bridge.mjs" resume <id|--last> [--write] --task "<follow-up>"
   

   Use run_in_background: true when the follow-up is an implementation step.
4. Present summary, files_changed, and the thread_id for further follow-ups.