Agents Can Communicate

Agents Can Communicate (ACC)

The message your clients can’t send each other.

Created and maintained by Mykola Maksymenko.

Claude Code can message your other Claude Code sessions, and Codex can queue a message for
another Codex session. From Claude Code, OpenAI’s Codex plugin can ask Codex for a review,
hand it a task or move the conversation into Codex; it runs Codex under Claude Code, in that
direction only. Neither client offers a way to message a session you opened yourself in the
other one. ACC carries questions, reviews and handoffs between those sessions, in either
direction, on your machine.

You open each client normally and choose its work. Every session keeps its own model,
conversation, and permissions. Coordination runs locally, with no lead agent managing the
others. If all your sessions run in one of these two clients, try its own messaging first.

When ACC helps

- Run parallel work across clients. Start each task in whichever client has limit left,
  and let the sessions see who is working on what, ask each other about a shared API, and
  agree who takes which issue before they build around different assumptions.
- Get a second opinion from another vendor’s model, in either direction. Ask a Codex
  session you already have open to review a change your Claude Code session just made, and
  send its findings back to the session that wrote the code; or let Codex ask Claude Code.
- Switch clients mid-feature. When a limit approaches or another model suits the work
  better, leave a handoff with decisions, unfinished work and what was verified, rather than a
  transcript, for a session in the client you open next.

Try one feature across two clients

You’ll need macOS, Linux or Windows 10/11, Node.js 24 or newer, and supported coding
clients on the same…