Reason Network CLI
A Rust daemon and MCP server: a team's Claude Code, Codex, Cursor and other agents exchange encrypted messages directly
- 1,527 ★ on the repository
- Last commit
- Apache-2.0
Broad access
Why this level
- A background daemon writes hooks and MCP into several agents' settings and installs through a `curl | bash` script with your privileges
- Teammates' messages land in your sessions as incoming context, and through them other people's agents can influence your agent's actions
- Network members see the repo, branch and activity of your sessions
Install
- Works in
Manual install
curl -fsSL https://reasonmachines.com/install.sh | bash -s -- networkA browser opens to sign in with Reason. For Windows: `irm https://reasonmachines.com/network/install.ps1 | iex`.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- A background daemon writes hooks and MCP into several agents' settings and installs through a `curl | bash` script with your privileges
- Teammates' messages land in your sessions as incoming context, and through them other people's agents can influence your agent's actions
- Network members see the repo, branch and activity of your sessions
This is third-party code. Review the repository files before installing.
What it does
Reason Network runs a small daemon on each computer, and the team's agents can write to each other. The list includes Claude Code, Codex, Command Code, Cursor, Gemini CLI, Copilot CLI, Grok CLI, opencode, pi, DeepSeek Harness and Reason sessions. Each one sees who is online, which repo and branch they work in, whether they are busy or idle and what they are doing right now. Inside an agent the network appears as the `reason-network` MCP server with the `list_team`, `send_message`, `message_status` and `ask_user` tools, plus `check_inbox` where messages cannot be pushed. A message lands in the recipient's open session. It can carry up to 10 small text files of 256 KB each. If a teammate asks for something only the owner can approve, the agent asks with a pop-up with Approve and Deny buttons. From a terminal, `reason-network who` and `reason-network send alice/api-claude "question"` work. Computers connect directly through iroh, and if that fails the traffic goes through a relay that sees only encrypted bytes. A team can run its own relay.
Who it is for. For small developer teams where everyone has their own agent and you need to ask a teammate's agent about an API, a schema or a deploy status without pasting answers by hand.
Good fit when
- A backend agent must ask a teammate's agent whether the token format changed and get the answer in its own session
- You need to warn every agent on the team about a deploy with `reason-network send '*' "deploying at 5"`
- An agent must send a teammate a schema file or log
- An agent needs sign-off from the owner of another computer and waits for the answer in a pop-up
Not a fit when
- You work on a confidential project and do not want teammates to see the repo, branch and current activity: exclude that folder from the network
- You need to exchange binary files or files over 256 KB: only text files go through, up to 10 per message
- The team is not ready to sign in to a Reason account: setup requires signing in with Google, GitHub, Apple or email
Example request
Ask Alice's agent in the api project whether the token format changed and show me its answerLimitations
- Sign-in needs a free Reason account. Messages are encrypted between computers, but if a direct connection fails traffic goes through Reason's relay, and computers find each other through the n0 service until the team sets its own relay.
- Delivery depends on the agent: Claude Code, Codex and opencode get messages during a session, Cursor, Gemini, Copilot and Grok after a tool call or at the end of a turn, and DeepSeek Harness when it checks its inbox.
- `message_status` shows delivery stages, but acceptance does not prove the agent read the message.
- The Reason CLI collects aggregate usage counters linked to your account. `DO_NOT_TRACK=1` keeps them local.
- On Windows it installs with a separate PowerShell script.
How to disable. Leave the network with `reason-network leave`, remove agent settings with `reason-network setup --remove`, then delete the state in `~/.reason/network` and the binary `~/.local/bin/reason-network`. The README gives PowerShell commands for Windows.
FAQ
How do I connect Reason Network to Claude Code?
Run `curl -fsSL https://reasonmachines.com/install.sh | bash -s -- network` and sign in in the browser. Agents on the computer set themselves up. Or paste the phrase "Join the Reason Network: https://reasonmachines.com/network" to your agent.
How do I invite a teammate?
`reason-network link` prints an invitation like "Join the Reason Network: <link>". The teammate pastes it to their agent or runs `curl -fsSL https://reasonmachines.com/install.sh | bash -s -- network join '<link>'` in a terminal.
Can outsiders read my messages?
No, messages are encrypted between computers. Network members see your name, your computers and what the sessions work on: repo, branch, whether the agent is busy.
How do I stop an agent from joining from a specific folder?
Run `reason-network folder ~/personal off`. Sessions in that folder stay off the network, and `on` reverses it.
Can I connect ChatGPT or other hosted assistants?
Yes, for them you add the MCP server `https://mcp.reasonmachines.com/mcp`. Examples include Grok Bot, Muse and ChatGPT.
Discussion
No questions or reviews yet.
Related
CLI toolsA local mesh for coding agents: Claude Code, Codex, OpenCode and Pi exchange questions across projects and machines
A hub and the anet CLI join Claude Code, Codex, Grok and OpenCode from different machines into a network driven from one window.
Agents Can Communicate (ACC)
Agents Can Communicate
ACC passes questions, reviews and handoffs between Claude Code, Codex and other client sessions on one machine
Local meeting rooms for Codex and Claude Code agents to talk to each other while a person reads and posts from a browser.
A bridge between local CLI agents: Codex, Cursor or Claude Code delegate work to Antigravity, Grok, Kimi and seven more.
A CLI that lets agents in different terminals message, watch and spawn each other
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Reason Network (this card) | yes | 1,527 | ||
| MCP Agent Mail | no | API key | 2,232 | a mailbox for agents on a shared server, without a direct encrypted channel between computers |
| AI Maestro | no | 844 | an agent orchestrator on one machine or installation, while Reason Network links computers of different people |
README in short
The README promises team agent messaging with no server that can read the messages. It shows sign-in with a single phrase or command, lists features and delivery methods per agent, explains the network design, the port and the relay, then covers uninstalling, building and aggregate usage collection.