Your agents, working together
You have Claude Code open in one window and Codex in another, maybe OpenCode on your desktop. They work on the same
code and don't know the others exist, so you end up copying messages between windows.
With telepathy, every session can see the others, message them and hand them work. Two agents on the same repo
notice each other, agree on who changes what, and from then on ask each other for what they need. You don't relay a
thing.
Get started
npm install -g telepathy-cli && telepathy setup
telepathy setup finds every coding agent on your machine and installs telepathy in each one. Restart the sessions
you already had open, then ask one agent about another:
Ask the Codex session what it's working on.
| Agent | Install |
|---|
| Claude Code | claude plugin marketplace add Winterrks/telepathy && claude plugin install telepathy@telepathy |
| Codex | codex plugin marketplace add Winterrks/telepathy && codex plugin add telepathy@telepathy, then approve its hooks in /hooks |
| OpenCode | opencode plugin add telepathy@git+https://github.com/Winterrks/telepathy.git |
| Kilo Code | add "git:github.com/Winterrks/telepathy" to plugin in ~/.config/kilo/kilo.json |
| Copilot CLI | copilot plugin marketplace add Winterrks/telepathy && copilot plugin install telepathy@telepathy |
| Qwen Code | qwen extensions install https://github.com/Winterrks/telepathy/archive/refs/heads/main.tar.gz --auto-update |
| Grok | grok plugin install Winterrks/telepathy#plugin --trust |
| Devin | devin plugins install Winterrks/telepathy#plugin |
| Antigravity | agy plugin install https://github.com/Winterrks/telepathy/tree/main/antigravity |
| Cursor | cursor-agent plugin marketplace add https://github.com/Winterrks/telepathy, then install it from /plugin |
| Kimi Code | /plugins install https://github.com/Winterrks/telepathy in a Kimi Code session |
You need Node.js 20 or newer. Each agent's page has its update command and its quirks.
What it does
Agents message each other
Any session can reach any other: Claude Code to Codex, Codex to OpenCode, Copilot to Claude. The message lands in
the other agent's conversation, clearly labeled as coming from another agent, and in Claude Code, Codex, OpenCode
and others it wakes an idle session up on its own. In Claude Code, the built-in ListAgents and SendMessage reach
the other agents too.
Tell the Codex session working on the API that the schema migration landed.
Delivery you can count on
A message counts as sent only once it is in the other agent's conversation. If it can't get there, the sender is
told so and the message is withdrawn, so it never turns up later as a surprise.
They stay out of each other's way
When an agent starts on files that another running session has just been editing, telepathy tells it which session
that is and suggests asking first. Two agents in one repo split the work instead of colliding.
Is anyone else working in this repo? If so, tell them which files you're about to change.
Hand work to any agent
One agent can start another as its helper: Claude Code can start Codex for a review, Codex can start OpenCode to
write the tests. The helper works in the background, in its own git worktree if you like, and its report comes back
by itself. In Claude Code it is a background task, with no model in between, that you can follow and stop like
Claude's own.
Have Codex review the diff on this branch in a worktree while you keep going on the UI.
Across all your devices
Run the bridge on each device and the sessions on your laptop and your desktop join one network, over Tailscale or
your local network. Devices on your own tailnet trust each other right away. Anything else pairs once with a 6-digit
code that both screens show.
Ask the Codex on my desktop whether the training run finished.
Start agents on your other machines
New in 0.13: start an agent on another of your devices, where it runs with that machine's files, sign-ins and
hardware. Its report comes back to the session that asked. Only devices you allow can start one.
Run the GPU tests on my desktop with Codex.
Any agent, instantly
Some agents only pick messages up when their next turn starts. Start one with telepathy run <agent> and every
message reaches it the moment it is sent, even while it is idle.
Grok Bot joins from the cloud
Connect a Grok Bot routine with telepathy grokbot connect and the Bot becomes a session like any other: a message
starts a run with the message in hand, and the Bot can answer.
Set up once, stays current
telepathy setup installs telepathy in every agent it finds and approves its hooks. After that, every copy updates
itself, and your devices move to a new version together.
Private by default
No telemetry, and no server of ours in the middle. Messages stay on your machine unless you start the bridge or
connect a Grok Bot, and the bridge only talks to your own devices. What leaves your machine, and when.
Works with
Under telepathy run, every agent with an ACP mode gets messages the moment they arrive.
Which versions are tested, and what isn't supported yet.
Learn more
How telepathy behaves, one topic per page, in docs/behaviour:
- How it works: the tools every agent gets, and what runs underneath
- Sessions: addresses, names, statuses, and resuming a session
- Messages: when a message counts as delivered, and what the receiver sees
- Agents: each agent's install, update and quirks
- The telepathy command:
setup, update, run and the rest
- Devices: the bridge, pairing, and devices that can't accept connections
- Subagents:
start_agent, on this machine or another
- Privacy and security
- Configuration and troubleshooting
- Development
telepathy is young, and some agents have quirks. An interrupted Codex, for one, waits for your next prompt before it
picks up messages. If you find one, open an issue.
License
MIT © Winterrks
