# AI use cases for Agents Can Communicate (automatis-tools/agents-can-communicate)

Repo: [automatis-tools/agents-can-communicate](https://github.com/automatis-tools/agents-can-communicate) | Use cases: 3 | Page: https://dedupedai.com/use-cases/automatis-tools-agents-can-communicate/

Agents Can Communicate (ACC) is a local, open source tool that lets AI coding sessions in different clients, such as Claude Code and Codex, send questions, reviews and handoffs to each other.

This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL.

- Split one feature between Claude Code and Codex: https://dedupedai.com/use-cases/automatis-tools-agents-can-communicate/split-one-feature-across-claude-code-and-codex/
- Get a code review from the other vendor's model: https://dedupedai.com/use-cases/automatis-tools-agents-can-communicate/get-a-cross-vendor-code-review/
- Hand off a feature to another client mid-task: https://dedupedai.com/use-cases/automatis-tools-agents-can-communicate/hand-off-a-feature-when-a-client-hits-its-limit/

## How to split one feature between Claude Code and Codex with Agents Can Communicate

Repo: [automatis-tools/agents-can-communicate](https://github.com/automatis-tools/agents-can-communicate) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

Run two sessions on one feature and let them ask each other for shared details.

**Who it is for:** A developer with Claude Code and Codex open in the same project who wants both to work on one feature at once.

**The problem:** Each client works in its own session, so details like an API request shape have to be copied between them by hand.

**The outcome:** Each session builds its own part, and the session that needs a detail asks the other one through ACC and gets the answer at its next turn.

### Steps

1. Run `npm install -g agents-can-communicate` to install ACC.
2. Run `acc install`, follow its activation instructions, and review any required hook or plugin trust.
3. Restart Claude Code and Codex from the project directory.
4. Ask Codex for the backend part, such as an account-registration endpoint, and ask Claude Code for the matching screen.
5. When a session needs a shared detail, let it ask the other session through ACC, and check whether the question was delivered and answered.

### Prompt to paste into your agent

```text
In the agents-can-communicate repo (https://github.com/automatis-tools/agents-can-communicate), install ACC and connect Claude Code and Codex in the project at <project-path>. Give each session one part of <feature-name> and report the answer from the session that needed a shared detail. Verify that the question sent between the two sessions shows as delivered and answered.
```

### Caveat

The agents decide when to coordinate, and ACC does not guarantee they will notice every dependency.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/automatis-tools-agents-can-communicate/split-one-feature-across-claude-code-and-codex/

## How to get a code review from the other vendor's model with Agents Can Communicate

Repo: [automatis-tools/agents-can-communicate](https://github.com/automatis-tools/agents-can-communicate) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

Have Codex review a change that Claude Code just wrote, and send findings back.

**Who it is for:** A developer who wants a second opinion from a different model on a change their Claude Code session just made.

**The problem:** The session that wrote the code is the only one that reviews it, and asking another model usually means copying files and findings manually.

**The outcome:** The session that made the change requests a review of named files through ACC, and the other session sends its findings back to it.

### Steps

1. Run `npm install -g agents-can-communicate` to install ACC.
2. Run `acc install`, follow its activation instructions, and review any required hook or plugin trust.
3. Restart Claude Code and Codex from the project directory, then open both in the same project.
4. In the session that made the change, ask it to request a review from the other session in ACC, naming the files.
5. Ask the other session to answer the review request, then check the findings in the session that wrote the code.
6. If a peer is missing or delivery is not what you expect, run `acc doctor` from the project.

### Prompt to paste into your agent

```text
In the agents-can-communicate repo (https://github.com/automatis-tools/agents-can-communicate), set up ACC so the session in <project-path> that wrote the change can request a review of <file-list> from a Codex session. Expected output: the review findings returned to the author session. Verify that the request and the answer both appear in ACC before accepting the findings.
```

### Caveat

ACC carries the review request and answer, but the quality of the review depends on the model and the session that receives it.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/automatis-tools-agents-can-communicate/get-a-cross-vendor-code-review/

## How to hand off a feature to another client mid-task with Agents Can Communicate

Repo: [automatis-tools/agents-can-communicate](https://github.com/automatis-tools/agents-can-communicate) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

Move unfinished work from Claude Code to Codex with a short handoff note.

**Who it is for:** A developer whose Claude Code limit is nearly used up and who wants to continue the same feature in Codex.

**The problem:** A full transcript is too long to carry into a new client, and the next session loses decisions and verified work.

**The outcome:** The new session starts from a handoff listing decisions, unfinished work and what was verified, instead of a transcript.

### Steps

1. Run `npm install -g agents-can-communicate` to install ACC.
2. Run `acc install`, follow its activation instructions, and review any required hook or plugin trust.
3. When the Claude Code session approaches its limit, ask it to leave a handoff with decisions, unfinished work and what was verified.
4. Open Codex in the same project so it can pick up the handoff and continue the feature.
5. If the handoff does not show up, run `acc doctor` from the project.

### Prompt to paste into your agent

```text
In the agents-can-communicate repo (https://github.com/automatis-tools/agents-can-communicate), use ACC to hand off <feature-name> from a Claude Code session in <project-path> to a Codex session. Expected output: a handoff that lists decisions, unfinished work and what was verified. Verify that the Codex session reads the handoff and confirms the next steps before continuing.
```

### Caveat

The handoff is only as complete as what the outgoing session records, so the receiving session still needs to check the code.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/automatis-tools-agents-can-communicate/hand-off-a-feature-when-a-client-hits-its-limit/