Reason Network connects coding agents across teammates' computers, peer to peer
Reason Network is a peer-to-peer tool, Apache-2.0 or MIT, that lets a team's coding agents message each other across teammates' computers through a small daemon on each machine and the iroh transport, with no central server.
Image: GitHub
Why it mattersA team whose coding agents already run in parallel can route a question to the right teammate's agent directly, with the owner approving anything that needs their sign-off.
A coding agent only knows what you tell it, so a question for a teammate's agent still goes through the teammate first.
Reason Network, a peer-to-peer tool released two days ago, lets a team's coding agents send messages to each other across teammates' computers without a central server. The author is Lars Talian, an engineer at Reason Machines, and the project replaces an earlier one of theirs called tincan. On GitHub the repository has 399 stars, is licensed MIT or Apache-2.0, and the README says it runs on macOS, Linux and Windows.
How it is set up
One small daemon runs on each computer. The README names ten coding agents it adds itself to: Claude Code, Codex, Cursor, Gemini CLI, Copilot CLI, Grok CLI, opencode, pi, DeepSeek Harness and Reason. The daemon registers an MCP server called reason-network that gives each agent three tools, list_team, send_message and ask_user, plus a check_inbox tool for agents whose runtime cannot be pushed to. Claude Code, Codex, opencode, pi and Reason get messages mid-session; Cursor, Gemini, Copilot and Grok at their next step; DeepSeek Harness when it next looks.
How it moves data
Each computer talks to each other computer directly over iroh, the peer-to-peer transport from n0. The README says that when a direct link cannot be made the traffic falls back to a relay that only sees encrypted bytes, and that a team can run its own relay to avoid n0 entirely. Only team members can connect, each computer can only speak for its own person, and messages for someone offline wait until they come back. State is stored under ~/.reason/network.
When a teammate's agent needs permission
The ask_user tool pops a question up on the owner's screen with Approve and Deny buttons, so a teammate's agent can ask for a sign-off that only the owner can give, and the answer travels back marked as the owner's answer so other agents cannot forge it. On macOS a menu bar icon shows who is online and what each session is doing. The author says Reason Network can be installed without a Reason account, through a shareable team link; signing in with a Reason workspace is the other option.
A team that has three or four engineers each running one or two agent sessions already has a routing problem, and today it is solved by walking to the person's desk or sending a chat message. The pitch here is that an agent can ask the right one of its teammates' agents directly, with the owner's permission tool for anything that needs it.
Source
This item was written by an AI system from the linked source. Reveneau is responsible for what it publishes.
Get AI News in your inbox
New developer tools, model and agent releases, and how teams are actually using them to release software. Short, and only when there is something worth reading.
