Telephone
Every Agent Gets a Number
Telephone lets the Claude Code and Codex sessions on your machine find each other and talk. A model from one company can review another's plan, hand it work, or wait on its answer, without you copying text between terminals.
Telephone gives every Claude Code and Codex session running on your machine an address, and gives the agents three tools: one to see who else is running, one to send a message, and one to check for replies. That's enough for a Codex thread to find the Claude session working in the same repository, ask it a question, and get the answer back as part of its own conversation.
Each of these tools is built to work alone. Claude Code can start subagents, but they're more Claude, with the same training and the same blind spots. Getting a second model's opinion used to mean me copying a plan out of one terminal, pasting it into another, and carrying the answer back. Telephone takes me out of the middle. The agents can reach across the line between companies and models on their own, and I can give them work that needs more than one of them.
A second opinion
The example on the homepage is the one I use most. Claude is writing a plan in one terminal, Codex is in another, and I tell Codex: find the Claude session working in this project, read its latest plan, check it against the code, send feedback, and ask for a reply. Telephone does the finding and the delivery. The agents do the reading and arguing. Models trained by different companies miss different things, so this catches more than asking the same model to look again. When Codex reviewed Telephone's own first version, which Claude wrote, it came back with four high-priority bugs and seven medium ones, each with a reproduction.
Teams that mix models
I've run Codex and Claude as one team overnight. For Shelf Goblin, my audiobook catalog, a Codex session in one repository was the lead and two Claude Code sessions in another were the workers. I told the Claude sessions to treat the lead's instructions as if they were mine and went to bed. The lead handed out tasks as requests, the workers reported back with replies, and most of the reader-facing app was built by morning. I've used the same setup for Jeeves and Autoperf. A brief for a team like this names each member by its address, says which of them can redirect work, and says what done means.
Agents asking each other
Workers don't have to go through a lead. One Claude session can ask another which files it's touching before it edits them, or a session that's stuck can ask one that already solved the same problem. None of that needs me.
Using it
cargo install telephone --locked
telephone install # prints the MCP config for Claude Code and Codex
After that, you mostly ask your agent in plain words: find the Codex thread working on this repo and ask it to review my change. Under that are three MCP tools, list_agents, send_message and check_inbox, and a CLI that mirrors them (telephone list, send, inbox), plus doctor for when something doesn't arrive.
An address is the runtime and its own ID: claude:24207 for a Claude session's process, or codex: and a thread UUID. There's no registration step and no sender to configure. Telephone works out who's calling from the process tree or from the thread ID Codex sends with every MCP call. A message is an inform by default, a request when the sender needs an answer, or a reply that points back at the request it answers.
How a message gets through
Neither Claude Code nor Codex documents a way for outside programs to talk to a running session, so Telephone uses what each one already has.
Claude Code has its own peer messaging under the hood. Each live session writes a record to ~/.claude/sessions/<pid>.json, keeps a private token next to it, and listens on a Unix socket. Telephone writes to that socket, and the message shows up in Claude's conversation as a new turn, even if the session was sitting idle. Codex keeps a registry of its threads in SQLite and has a codex queue command that puts a message in a thread's queue. Codex picks it up the next time that thread runs.
Those native routes can wake an agent up, but they have a gap. An agent that sent a request and is waiting for the answer is in the middle of a turn, and Codex won't read its queue until the turn ends. So Telephone also keeps its own inbox, which an agent can poll with check_inbox. To choose between them, each inbox check counts as evidence that the agent is listening there, and the evidence lasts fifteen seconds. Sending a request counts too, so a fast reply lands in the inbox before the sender's first check. A new message goes to the inbox while the evidence is fresh, and to the native route otherwise. Nobody has to pick a route by hand.
Caveats
- One machine, one user. Addresses are routing hints, not identities, and nothing authenticates the sender. A message from another agent arrives marked as untrusted text. It can't grant permissions, and the receiving agent still follows its own user's rules. A conversation stops after eight hops, so two agents can't bounce messages forever. The README opens with a warning I meant: unsafe, experimental software. One agent's message can lead another to run commands or change files.
- Sent isn't read. A Claude socket write isn't confirmed, and a successful
codex queuemeans the message was queued, not seen. Before v0.2.0, a Shelf Goblin worker's status messages sat in the Codex queue while the lead polled an empty inbox. The agents fell back to leaving handoff notes in the repository. Telephone now says which channel each message took, andtelephone doctorshows the evidence behind the choice. - Codex can't say it's running.
telephone listmarks a Claude sessionlivewhen its process checks out. A Codex thread only getsrecent?, because nothing outside Codex can tell whether a thread is running or exited a second after its last write. - Undocumented interfaces. Both routes rely on internals that Anthropic and OpenAI haven't promised to keep. Any release of either tool could break them.
- Long conversations cost context. Agents that talk all night fill their context windows fast, so an optional hook reminds Claude to compact at 250k and again at 300k tokens.
For a few days Telephone also tried to reach OpenCode, Zed and Delta. Version 0.2.0 took all of that out to make the two runtimes I use work well, and it got easier to use.
Going further than one machine would need authenticated senders and real permissions first. Until then it's a phone line inside your own house, which turns out to be most of what I wanted: the agents I already run, from two companies, working on the same problem without me relaying between them.