Cursor rule

1---
2description: Delegate investigation, an explicit fix request, or follow-up
3  rescue work to the Codex rescue subagent
4alwaysApply: true
5---
6 
7Invoke the `codex:codex-rescue` subagent via the `Agent` tool (`subagent_type: "codex:codex-rescue"`), forwarding the raw user request as the prompt.
8`codex:codex-rescue` is a subagent, not a skill — do not call `Skill(codex:codex-rescue)` (no such skill) or `Skill(codex:rescue)` (that re-enters this command and hangs the session). The command runs inline so the `Agent` tool stays in scope; forked general-purpose subagents do not expose it.
9The final user-visible response must be Codex's output verbatim.
10 
11Raw user request:
12$ARGUMENTS
13 
14Execution mode:
15 
16- If the request includes `--background`, run the `codex:codex-rescue` subagent in the background.
17- If the request includes `--wait`, run the `codex:codex-rescue` subagent in the foreground.
18- If neither flag is present, default to foreground.
19- `--background` and `--wait` are execution flags for Claude Code. Do not forward them to `task`, and do not treat them as part of the natural-language task text.
20- `--model` and `--effort` are runtime-selection flags. Preserve them for the forwarded `task` call, but do not treat them as part of the natural-language task text.
21- If the request includes `--resume`, do not ask whether to continue. The user already chose.
22- If the request includes `--fresh`, do not ask whether to continue. The user already chose.
23- Otherwise, before starting Codex, check for a resumable rescue thread from this Claude session by running:
24 
25```bash
26node ".forgecat/profiles/@forgecat/openai_codex-plugin-cc_codex/scripts/codex-companion.mjs" task-resume-candidate --json
27```
28 
29- If that helper reports `available: true`, use `AskUserQuestion` exactly once to ask whether to continue the current Codex thread or start a new one.
30- The two choices must be:
31  - `Continue current Codex thread`
32  - `Start a new Codex thread`
33- If the user is clearly giving a follow-up instruction such as "continue", "keep going", "resume", "apply the top fix", or "dig deeper", put `Continue current Codex thread (Recommended)` first.
34- Otherwise put `Start a new Codex thread (Recommended)` first.
35- If the user chooses continue, add `--resume` before routing to the subagent.
36- If the user chooses a new thread, add `--fresh` before routing to the subagent.
37- If the helper reports `available: false`, do not ask. Route normally.
38 
39Operating rules:
40 
41- The subagent is a thin forwarder only. It should use one `Bash` call to invoke `node ".forgecat/profiles/@forgecat/openai_codex-plugin-cc_codex/scripts/codex-companion.mjs" task ...` and return that command's stdout as-is.
42- Return the Codex companion stdout verbatim to the user.
43- Do not paraphrase, summarize, rewrite, or add commentary before or after it.
44- Do not ask the subagent to inspect files, monitor progress, poll `/codex:status`, fetch `/codex:result`, call `/codex:cancel`, summarize output, or do follow-up work of its own.
45- Leave `--effort` unset unless the user explicitly asks for a specific reasoning effort.
46- Leave the model unset unless the user explicitly asks for one. If they ask for `spark`, map it to `gpt-5.3-codex-spark`.
47- Leave `--resume` and `--fresh` in the forwarded request. The subagent handles that routing when it builds the `task` command.
48- If the helper reports that Codex is missing or unauthenticated, stop and tell the user to run `/codex:setup`.
49- If the user did not supply a request, ask what Codex should investigate or fix.
50