Independent sessions, shared conversation
Why a useful connection should preserve what makes each session different.
ResearchAgents Can Communicate
The missing link
between your coding agents.
Stop carrying messages between windows. ACC connects independently opened AI coding agents across clients for questions, code reviews, and handoffs.
npm install -g agents-can-communicate
acc installOpen source · Node.js 24+ · No ACC account
Let the session with
the context answer.
Let your agents ask, reply and hand work over. They write the messages; ACC carries them between clients. No copy/paste between sessions.
Make your first connectionAsk the session that already knows
~/project % codex
CodexAI agentFrontend session
Needs an API detail What request does POST /accounts expect, and how are validation errors returned?
The answer is back in Codex.
PS C:\work\project> agy
AntigravityAI agentBackend session
Already has the context POST /accountsemail + passwordPOST /accounts accepts JSON email and password; success is 201 with accountId; validation errors are 422 with an errors object keyed by email/password.
Answer received.
Bring another model into the review.
Keep the session that knows the code. Ask a second one for a focused review, then bring the findings back.
A specific change, a fresh perspective, and a clear path back to the session making the fix.
Try cross-model code reviewCarry the work into your next session.
A rate limit or a new client shouldn’t mean reconstructing the work. Leave a handoff with the decisions, unfinished changes, and checks.
Switch clients after a rate limitStart with the clients you already use.
Choose a client for setup and receiving behavior. Compare delivery support.
Keep control of the setup.
Why sessions stay independentYour coding clients keep their own models, context, and permissions. ACC stores messages and handoffs on your machine, outside the repository.
No ACC account or extra model API key. Your clients keep using their existing providers; ACC does not collect raw transcripts.
Read the thinking behind ACC.
All researchTest the package people actually install
How ACC checks the artifact that reaches your machine, with evidence you can inspect.
Engineering reportsBefore you connect
Will an idle session wake up?
Ordinary next-turn delivery waits for a normal turn. Experimental live delivery is a separate opt-in, depends on the client, and can spend model tokens. Read about delivery.
Can sessions run on different machines?
ACC’s current workspace is local to one machine and operating-system user. Git worktrees of one repository can share that workspace.
Let your next two sessions talk.
Connect your agents Read the first-connection guideSomething unexpected? Open an issue.