Connect Claude Code to Other AI Coding Agents
Connect Claude Code to Codex, Antigravity, Gemini CLI, and other coding agents with ACC. Compare native messaging and configure the supported delivery mode.
Claude Code already has its own cross-session messaging. If every session in your workflow is Claude Code, try that native feature first.
ACC becomes useful when a Claude Code session needs to talk to an independent session in another client: Antigravity, Codex, Kimi Code, Gemini CLI, or a participant using explicit inbox access.
Each side keeps its own conversation and permissions. A message supplies context rather than authority. For the first exchange, follow the cross-client connection guide and the setup for the other receiver, such as Codex or Gemini CLI.
Activate the integration#
acc install --adapter claude_code
Complete the installation instructions and start a new Claude Code session in the project. Trusted hooks provide the session's own ACC identity and coordination context.
The next-turn evidence was captured on Claude Code 2.1.233. That receiving path waits for a user prompt. It does not itself wake an idle session.
Choose whether idle sessions may wake#
Experimental live delivery uses the inbox Claude Code opens for its session. The captured minimum is 2.1.282. Start Claude Code with the ordinary command; ACC does not require a launcher wrapper for this path.
An idle wake starts a turn. A busy receiver can take it between tool calls. Inbound policy matters: a bypass-permissions session can hold each wake for approval unless its cross-session inbound setting accepts it. A refusal can drop wakes.
Live delivery requires recorded opt-in and may spend model tokens.
Distinguish Claude.app surfaces#
The repository includes a capture of a local Code session in Claude.app using the same inbox mechanism on Claude Code 2.1.286.
Cloud, SSH, and Cowork sessions are not the same local execution environment. ACC's boundary is one machine and operating-system user; native Claude messaging has its own scope.
Ask for a peer review#
For a Claude Code implementer:
Ask the available Kimi or Codex review session through ACC to inspect the identified change. Include the exact checkout and revision. Request blocking defects with evidence, then verify the findings before editing.
See the full review workflow for target selection and follow-up.
If your need is specifically to call Codex from inside Claude Code, also consider the official Codex plugin. ACC addresses the broader workflow of sessions you run separately.
Sources#
Reviewed against the documentation and recorded evidence for ACC 0.11.1.