/rescue

description: Delegate investigation, an explicit fix request, or follow-up rescue work to the Gemini rescue subagent
argument-hint: "[--background|--wait] [--resume|--fresh] [--model <pro|flash|flash-lite>] [what Gemini should investigate, solve, or continue]"
context: fork
allowed-tools: Bash(node:*), AskUserQuestion

Route this request to the `gemini:gemini-rescue` subagent. The final user-visible response must be Gemini's output verbatim.

Raw user request: $ARGUMENTS

Execution mode:

• If the request includes `--background`, run the `gemini:gemini-rescue` subagent in the background.
• If the request includes `--wait`, run the `gemini:gemini-rescue` subagent in the foreground.
• If neither flag is present, default to foreground.
• `--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.
• `--model` is a runtime-selection flag. Preserve it for the forwarded `task` call, but do not treat it as part of the natural-language task text.
• If the request includes `--resume`, do not ask whether to continue. The user already chose.
• If the request includes `--fresh`, do not ask whether to continue. The user already chose.
• Otherwise, before starting Gemini, check for a resumable rescue thread from this Claude session by running:

node "${CLAUDE_PLUGIN_ROOT}/scripts/gemini-companion.mjs" task-resume-candidate --json

• If that helper reports `available: true`, use `AskUserQuestion` exactly once to ask whether to continue the current Gemini thread or start a new one.
• The two choices must be:
• `Continue current Gemini thread`
• `Start a new Gemini thread`
• 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 Gemini thread (Recommended)` first.
• Otherwise put `Start a new Gemini thread (Recommended)` first.
• If the user chooses continue, add `--resume` before routing to the subagent.
• If the user chooses a new thread, add `--fresh` before routing to the subagent.
• If the helper reports `available: false`, do not ask. Route normally.

Operating rules:

• The subagent is a thin forwarder only. It should use one `Bash` call to invoke `node "${CLAUDE_PLUGIN_ROOT}/scripts/gemini-companion.mjs" task ...` and return that command's stdout as-is.
• Return the Gemini companion stdout verbatim to the user.
• Do not paraphrase, summarize, rewrite, or add commentary before or after it.
• Do not ask the subagent to inspect files, monitor progress, poll `/gemini:status`, fetch `/gemini:result`, call `/gemini:cancel`, summarize output, or do follow-up work of its own.
• Leave model unset unless the user explicitly asks for one. If they ask for `pro`, map it to `gemini-2.5-pro`. If they ask for `flash`, map it to `gemini-2.5-flash`. If they ask for `flash-lite`, map it to `gemini-2.5-flash-lite`.
• Leave `--resume` and `--fresh` in the forwarded request. The subagent handles that routing when it builds the `task` command.
• If the helper reports that Gemini is missing or unauthenticated, stop and tell the user to run `/gemini:setup`.
• If the user did not supply a request, check for a saved review from `/gemini:review` or `/gemini:adversarial-review`:

node "${CLAUDE_PLUGIN_ROOT}/scripts/gemini-companion.mjs" last-review --json

• Parse the JSON output. If `available: true`: use `AskUserQuestion` once with two options:
• `Fix issues from last review (Recommended)` — use the `content` field from the JSON as context for the rescue task
• `Describe a new task` — ask what Gemini should investigate or fix
• If the user chooses to fix from last review, include the review content verbatim prefixed with: "The following issues were found in a prior Gemini review. Please fix them:\n\n"
• If `available: false`: ask what Gemini should investigate or fix.