gemini

 gemini-companion

Delegate rescues and code reviews to Gemini CLI from inside Claude Code.
One CLI talking to another. No broker, no protocol dance, no magic.

If this saves you an afternoon, star the repo ⭐

/gemini:setup
/gemini:rescue investigate why the auth middleware drops cookies on logout
/gemini:review

That's the whole thing. You type a slash command, Claude hands the work over to Gemini CLI, and you get Gemini's answer back without Claude paraphrasing it.

Table of Contents

• What you get
• Why this exists
• Requirements
• Install
• Usage
  • /gemini:setup
  • /gemini:rescue
  • /gemini:review
  • /gemini:adversarial-review
  • /gemini:status
  • /gemini:result
  • /gemini:cancel
• Typical flows
• Feature parity with codex-plugin-cc
• The --effort flag (how it actually works)
• Gemini integration
• State layout
• Skills that ship with the plugin
• Environment variables
• Development
• FAQ
• Attribution
• License

What you get

• /gemini:review — a read-only code review. The plugin collects git status/diff/changed files locally, then runs Gemini in --approval-mode plan so it physically cannot edit your workspace
• /gemini:adversarial-review — a steerable review with structured JSON findings
• /gemini:rescue — hand any task off to Gemini through a thin subagent
• /gemini:status, /gemini:result, /gemini:cancel — manage background jobs without leaving Claude
• /gemini:setup — health check the runtime and toggle the optional stop-time review gate

Everything is Gemini doing the work. This plugin just makes sure the output comes back to you clean, the state is persisted, and cancellation actually cancels.

Why this exists

I wanted codex-plugin-cc's workflow but pointed at Google's Gemini CLI.

There's an existing community Gemini plugin for Claude Code built on top of Gemini's experimental ACP (Agent Client Protocol) mode. I tried it, ran into bugs, and decided to go a different way.

Gemini CLI's --output-format stream-json turned out to be a clean, flat event stream: an init with session id + model, then message events (user / assistant, with a delta: true flag for partials), tool_use / tool_result events, and a final result envelope carrying stats and exit status. That made the port easy. It's also way easier to debug than ACP: every event is a newline of JSON, so I can tail -f and pipe through jq while things are misbehaving.

The tradeoff is that every task spawns a fresh gemini process instead of reusing a persistent one. Cold start is 0.5 to 2 seconds. That's invisible for rescue and review workflows and I am not going to over-engineer a broker to save a second per call.

Requirements