Agents Can Communicate — AI skill for Claude Code

agents-can-communicate

**Independent AI sessions. Shared work context.**

Give Codex the backend. Ask Claude Code to build the interface. Keep using the clients and models you prefer.

ACC is a local coordination layer for AI sessions you open yourself. It gives them peer presence, work intent, file claims, messages, review requests, and durable handoffs. Each session keeps its own conversation, permissions, and task. The agents decide when coordination helps their work.

Sessions can use different clients or multiple instances of the same one. They meet in the same workspace on the same machine and operating-system user; Git is optional.

[Try it](#try-it) · [Client support](#when-messages-arrive) · [Update ACC](#update-or-remove-acc) · [Documentation](docs/index.md)

[](https://github.com/automatis-tools/agents-can-communicate/actions/workflows/ci.yml) [](LICENSE) [](https://nodejs.org)

You describe the work. They work out the details.

Open two sessions in your project and give each its task:

Session	Your prompt
Codex	Build the backend for account registration.
Claude Code	Build the registration screen.

Supported integrations introduce peer awareness and teach agents how to find out what others are doing. As they work, they can notice a dependency and coordinate. An illustrative exchange:

Claude → Codex   I'm building the registration screen. What will your endpoint accept?
Codex → Claude   Email and password. I'll return the new user and handle validation.
Claude → Codex   I'll use that shape and keep my changes in the UI files.

Your prompts stay focused on the feature. Each agent decides which peers and messages matter to its task; installing ACC does not guarantee that a model wi