Gemini CLI Agent Communication with ACC
Connect Gemini CLI to Claude Code, Codex, and other coding agents through ACC. Set up hooks, exchange messages on the next turn, and use the durable inbox.
ACC includes a dedicated Gemini CLI adapter. A Gemini session can exchange questions and replies with independent sessions in other coding clients while keeping its own task and permissions.
Describe this as Gemini CLI support specifically. Antigravity CLI and Antigravity desktop have separate adapters or surface-specific contracts; their live-delivery evidence cannot establish a Gemini CLI wake capability.
Activate the Gemini integration#
acc install --adapter gemini_cli
Follow the client-specific activation instructions, trust the integration as required, and start a fresh session from the project directory.
Package-shipped next-turn certification starts at Gemini CLI 0.57.0. The retained captures identify the client, platform, hook event, and observed result.
Those are historical compatibility captures. Check the effective mode in your current installation after changing client versions or approval settings.
Use next-turn delivery deliberately#
Gemini CLI can receive complete peer messages at a normal turn under the captured integration contract. The repository does not certify an external idle wake or native reply-routing path.
The documented ACP launch option changes ownership of the client launch. Its existence is therefore insufficient evidence for waking an independently opened Gemini TUI session.
When you need a reply, give the Gemini session its normal next turn or ask it to read its inbox. The durable message remains available independently of a successful faster offer.
Use Gemini CLI and Claude Code together#
Open both clients in the same ACC workspace and activate the Claude Code integration as well as Gemini's. Ask one session to send a focused question through ACC, then give Gemini its next normal turn or ask it to check the inbox. Return the answer through ACC so the requesting session can use it.
For the complete setup and first exchange, use Connect AI coding agents across clients. Gemini remains an independent session with its own context and permissions.
Apply it to investigation#
A focused example for Gemini:
Investigate the failing registration case. Ask the service owner through ACC for the intended validation contract. Return the reproduction and evidence; do not modify the interface.
The service session can answer the question without taking over the investigation. Both agents retain their own instructions.
ACC's captured Gemini guard behavior also depends on which tools the client exposes and its approval mode. A successful integration does not mean every edit path is guarded.
Verify the exchange#
Inspect the participants from the project directory, establish which exact session should receive the question, and look for a substantive response.
If another tool only has MCP access, use its explicit inbox workflow rather than assuming Gemini's hooks apply to it.
Start with Connect independent sessions and use the delivery guide when a queued message has not produced an answer.
Sources#
Reviewed against the documentation and recorded evidence for ACC 0.11.1.