Agents Can Communicate (ACC) CLI
Agents Can Communicate
ACC passes questions, reviews and handoffs between Claude Code, Codex and other client sessions on one machine
- 175 ★ on the repository
- Last commit
Extended access
Why this level
- Changes client settings: installs hooks and plugins, and automatic updates are enabled on first install
- Live delivery can wake sessions and spend model tokens, and is off by default
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/agents-can-communicateDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Changes client settings: installs hooks and plugins, and automatic updates are enabled on first install
- Live delivery can wake sessions and spend model tokens, and is off by default
This is third-party code. Review the repository files before installing.
What it does
Agents Can Communicate (ACC) is an npm tool that links sessions of different coding agents in one project. Claude Code can already message its own other sessions, and Codex queues a message for another Codex. ACC adds a channel between sessions from different clients in both directions. Integrations cover Antigravity CLI, Claude Code, Codex, Grok and Kimi Code, and other clients connect through MCP. You open the clients as usual and choose the work yourself. Each session keeps its own model, conversation and permissions, and there is no lead agent. Sessions see who is working on what, ask each other about a shared API and agree who takes a task. One agent can ask another, for example Codex, to review a change Claude Code just wrote and send the findings back to the author. When you switch clients mid-task you leave a handoff: what is done, which decisions were made, what is unfinished and what was verified, with no transcript. Messages and handoffs live in local app data outside the project, and ACC never collects or shares raw session transcripts.
Who it is for. Developers who run Claude Code and Codex in parallel on one feature and carry messages between windows themselves when one agent needs an answer from the other.
Good fit when
- Claude Code writes the frontend, Codex builds the endpoint, and the request shape must be agreed without you relaying
- You want a second opinion from another vendor's model on a fresh change, with the answer returning to the author
- One client is near its limit and work moves to another client with a ready handoff
- Two sessions might take the same task and need to see each other and split the work
- Another client joins the exchange over MCP following the documentation
Not a fit when
- All sessions run in one client: Claude Code and Codex have their own message passing between their sessions
- You need a lead agent that hands out tasks to the rest: ACC works without a leader
- You need data passed between machines or users: exchange happens on one machine under one OS user
- Node.js 24 is not available: npm install needs version 24 or newer
Example request
Ask the Codex session in this project what response shape the registration endpoint returns, and build the registration screen from its answerLimitations
- macOS, Linux or Windows 10 and 11, Node.js 24 or newer and supported clients on one machine under one OS user are required. Windows works without WSL.
- The installer connects clients it finds, after which review hook and plugin trust prompts and restart clients from the project folder.
- Automatic delivery depends on client version and platform. Experimental live delivery that wakes sessions is off by default, opt-in, and can spend model tokens.
- Agents decide when to coordinate, and ACC does not guarantee they will notice every dependency.
How to disable. The `acc uninstall` command removes integrations, and `acc update --auto off` turns off automatic updates enabled on first install. Messages and handoffs live in local app data outside the project and can be deleted by hand. The package is removed with `npm uninstall -g agents-can-communicate`.
FAQ
How do I install ACC?
Run `npm install -g agents-can-communicate`, then `acc install`. The installer connects clients it finds, after which restart them from the project folder and confirm trust for hooks and plugins.
How does ACC differ from messaging inside Claude Code or Codex?
Those work between sessions of one client, while ACC adds a channel between sessions of different clients in both directions. If all sessions run in one client, start with its own messaging.
Which clients are supported?
Antigravity CLI, Claude Code, Codex, Grok and Kimi Code. Other clients connect through MCP with their own configuration and instructions.
What is a handoff?
A note for the session in the next client: what is done, which decisions were made, what remains and what was verified. It is a brief summary rather than a transcript.
What if the second participant is not visible?
Run `acc doctor` from the project folder: it shows what is missing and how delivery differs from expectations. Then check the troubleshooting guide.
Discussion
No questions or reviews yet.
Related
CLI toolsA bridge between local CLI agents: Codex, Cursor or Claude Code delegate work to Antigravity, Grok, Kimi and seven more.
A CLI that lets agents in different terminals message, watch and spawn each other
A tmux-based TUI that runs Claude Code, Codex and other agents in one list: status, quick prompts, worktrees and diff review
A skill for messaging between Claude Code, Codex, Gemini CLI and other CLI agents through a shared local SQLite database, written in bash
A local bridge linking Claude Code and Codex in one session so the agents message each other and review each other's work
A hub and the anet CLI join Claude Code, Codex, Grok and OpenCode from different machines into a network driven from one window.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Agents Can Communicate (ACC) (this card) | no | 175 | ||
| MCP Agent Mail (Rust) | no | not required | 234 | a mail server for agents on one repository with file reservations, while ACC focuses on different clients and handoffs |
| Shared Sessions for Claude Code | no | 854 | shares a Claude Code session with a colleague instead of linking different agents on one machine |
README in short
The README explains the gap: messaging works within a client but not between clients. It then gives a diagram, three use cases, a trial run of one feature across two clients with ready phrases for both, client support, data locality and a list of the author's related projects.