/rescue
Hand a stuck or open-ended problem to Codex for an independent investigation or rescue pass
$ npx -y skills add greenpolo/cc-multi-cli-plugin --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/rescue
Context preview
What this command does when you run it.
Hand a stuck or open-ended problem to Codex for an independent investigation or rescue pass
Command definition
rescue.mddescription: Hand a stuck or open-ended problem to Codex for an independent investigation or rescue pass
argument-hint: "[--background|--wait] [--resume|--fresh] [--model <model>] [--effort <low|medium|high|xhigh>] <what you're stuck on>"
allowed-tools: AskUserQuestion, Agent
Invoke the `multi:codex-rescue` subagent via the `Agent` tool, forwarding the user's request as the prompt.
The subagent runs Codex in open-ended rescue mode — hand it a stuck problem, a confusing bug, or a substantial unbounded task and it investigates independently.
This is distinct from `/codex:execute` (structured execution of a clear plan step) and `/codex:review` (read-only review). Use `/codex:rescue` when Claude is stuck, wants a second opinion, or needs a deeper root-cause investigation.
Raw user request: $ARGUMENTS
Execution:
- For a small, clearly bounded rescue, invoke the subagent in the foreground (blocking) — the result comes back inline.
- For an open-ended, multi-step, or long-running investigation, invoke the subagent with the `Agent` tool's `run_in_background: true`. The subagent runs Codex to completion in the foreground, so the harness wakes you with a `<task-notification>` the moment Codex finishes, errors, OR the inactivity watchdog kills a hang — even after this turn ends. This is the path that surfaces failures instead of stalling silently.
- Do NOT add the companion's `--background` flag to get this — that detaches a worker the harness cannot see (no notification). Reserve `--background` for explicit fire-and-forget the user wants to poll via `/multi:status`.
- Preserve `--model`, `--effort`, `--resume`, `--fresh` for the forwarded command — the subagent reads them.
- If the user passes `--resume`, the subagent continues the latest Codex thread for this repo; otherwise it starts fresh.
- If the request includes no prompt text, ask what Codex should investigate before proceeding.
Return Codex's output verbatim once the subagent completes.
Read more
description: Hand a stuck or open-ended problem to Codex for an independent investigation or rescue pass argument-hint: "[--background|--wait] [--resume|--fresh] [--model <model>] [--effort <low|medium|high|xhigh>] <what you're stuck on>" allowed-tools: AskUserQuestion, Agent
Invoke the `multi:codex-rescue` subagent via the `Agent` tool, forwarding the user's request as the prompt.
The subagent runs Codex in open-ended rescue mode — hand it a stuck problem, a confusing bug, or a substantial unbounded task and it investigates independently.
This is distinct from `/codex:execute` (structured execution of a clear plan step) and `/codex:review` (read-only review). Use `/codex:rescue` when Claude is stuck, wants a second opinion, or needs a deeper root-cause investigation.
Raw user request: $ARGUMENTS
Execution:
- For a small, clearly bounded rescue, invoke the subagent in the foreground (blocking) — the result comes back inline.
- For an open-ended, multi-step, or long-running investigation, invoke the subagent with the `Agent` tool's `run_in_background: true`. The subagent runs Codex to completion in the foreground, so the harness wakes you with a `<task-notification>` the moment Codex finishes, errors, OR the inactivity watchdog kills a hang — even after this turn ends. This is the path that surfaces failures instead of stalling silently.
- Do NOT add the companion's `--background` flag to get this — that detaches a worker the harness cannot see (no notification). Reserve `--background` for explicit fire-and-forget the user wants to poll via `/multi:status`.
- Preserve `--model`, `--effort`, `--resume`, `--fresh` for the forwarded command — the subagent reads them.
- If the user passes `--resume`, the subagent continues the latest Codex thread for this repo; otherwise it starts fresh.
- If the request includes no prompt text, ask what Codex should investigate before proceeding.
Return Codex's output verbatim once the subagent completes.
If you have access to multiple AI coding CLIs (Codex, Cursor, Antigravity, and OpenCode), this plugin lets Claude Code delegate to whichever one is best for the task — without you having to switch tools or run them yourself.
Repo: greenpolo/cc-multi-cli-plugin
Other commands on cc-multi-cli-plugin.
- /explore
Fast codebase exploration with Antigravity's agy CLI (Gemini 3.5 Flash, read-only). EXPERIMENTAL.
Open command - /research
Deep external research with Antigravity's agy CLI (Gemini 3.5 Flash — web search + synthesis, read-only). EXPERIMENTAL.
Open command - /adversarial-review
Adversarial design/code review with Codex — challenges the approach, not just the diff (read-only)
Open command - /execute
Delegate execution of a specific plan or plan step to Codex
Open command - /review
Run a Codex code review of your working tree or a branch (read-only)
Open command - /delegate
Delegate an implementation task or plan step to Cursor (agentic, writes code; default Auto model)
Open command