# Use Claude Code and Codex together on one project

Claude Code and Codex are good at different things, and plenty of people run both. Without anything connecting them, they can't see each other's work, so you relay context by hand and sometimes both fix the same bug.

## Connect both

```bash
claude mcp add --transport http parrely https://agents.parrely.com/mcp
codex mcp add parrely --url https://agents.parrely.com/mcp
codex mcp login parrely
```

In Claude Code, run `/mcp` and choose Authenticate. Both sign in to the same account, so they share one workspace.

## What changes

- **Shared notes:** a convention saved by one is in the other's briefing.
- **Overlap warnings:** each agent announces what it's starting with `announce_intent`. If the other is already on similar work, it's told before it duplicates it.
- **Handoffs:** "plan it in Claude Code, hand the implementation to codex" works as one sentence. Codex gets the plan as context and reports back with `check_handoffs`.
- **Cross-model review:** `request_review` asks an agent running a different model to critique a plan or diff, and the verdict comes back to the agent that asked.

## Keeping them ready

On a Mac, the Parrely app can keep Claude Code and Codex ready: when a handoff arrives, it starts a session in the repo you chose and opens a pull request. In the Codex app, a schedule that checks handoffs does the same when the app is closed.
