rescue

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

Raw user request: $ARGUMENTS

Execution mode:

• If the request includes both --background and --stream, stop and tell the user to choose one.
• If the request includes --stream, do not route through the gemini:rescue subagent. Run the companion task command directly in the foreground.
• If the request includes --background, run the gemini:rescue subagent in the background.
• If the request includes --wait, run the 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.
• --stream, --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.
• 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 session or start a new one.
• The two choices must be:
  • Continue current Gemini session
  • Start a new Gemini session
• 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 session (Recommended) first.
• Otherwise put Start a new Gemini session (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:

• In --stream mode, bypass the subagent and use direct command execution syntax so incremental Gemini stdout is not buffered by the subagent or Bash tool layer: !node "${CLAUDE_PLUGIN_ROOT}/scripts/gemini-companion.mjs" task "$ARGUMENTS"

• In --stream mode, return that direct command output verbatim and do not route to the subagent.

• 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.

• --stream forces foreground execution and conflicts with --background.

• In stream mode, the task prints raw Gemini text incrementally instead of waiting for the final buffered output.

• 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 --effort unset unless the user explicitly asks for a specific reasoning effort.

• Leave the model unset unless the user explicitly asks for one. If they ask for spark, map it to flash for compatibility.

• 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, ask what Gemini should investigate or fix.