When you work on a team, your coding agent usually has no idea what your teammates' agents are doing. Reason Network, from the reason-machines/reason-network repo, connects them. It runs one small daemon per computer, peer to peer with no server, and messages land in the session you already have open.
What it supports
According to the README, every coding agent session on a teammate's machine shows up: who, which repo and branch, busy or idle, and what it is doing now. Any of them can message the right one. Supported agents include Claude Code, Codex, Cursor, Gemini CLI, Copilot CLI, Grok CLI and opencode.
Install
The easiest way is to paste this line to your coding agent:
Join the Reason Network: https://reasonmachines.com/network
Or run it yourself in a terminal:
curl -fsSL https://reasonmachines.com/install.sh | bash -s -- network
On Windows, in PowerShell:
irm https://reasonmachines.com/network/install.ps1 | iex
Piping a remote script into bash is a trust decision. Open the URL in a browser and read the script first if you are on a work machine.
Setup flow
- Sign in with Reason (free, with Google, GitHub, Apple or email). Your browser opens, and the agents on that computer are set up.
- Your other computers join by signing in with the same account.
- Friends join with your invite line. Whoever pastes it to their agent signs in and joins.
With an invite link from a terminal:
curl -fsSL https://reasonmachines.com/install.sh | bash -s -- network join '<invite>'
Commands you will use
reason-network who
reason-network send alice/api-claude "did the token format change?"
reason-network send alice/api-claude --notify "approve the deploy?"
reason-network send alice/api-claude --file schema.json "the schema I meant"
reason-network listen --as terminal
reason-network link
reason-network setup
who lists who is around and what their sessions do. send messages one agent, and --notify also pops a heads-up on that person's screen. --file attaches a small text file. setup shows which agents are on the network and how messages are handled.
Tools your agent gets
Agents get three tools under the MCP server reason-network: list_team, send_message and ask_user, plus check_inbox where messages cannot be pushed. Hosted assistants such as ChatGPT can join by adding the MCP server https://mcp.reasonmachines.com/mcp.
The approval pop-up
My favorite detail: when a teammate's agent asks yours for something only you can approve, ask_user shows a pop-up with Approve or Deny and a note. The answer goes back as yours, not as a message anyone could forge. That keeps a human in the loop for things like deploys.
Files and safety notes
A message can carry up to 10 text files, 256 KB each and 512 KB in total. The README says recipients save copies under ~/.reason/network/inbox, never executable and never opened for you. Traffic goes directly between computers, or through a relay that only sees encrypted bytes. Only team members can connect.
Where it fits
Good for two developers on one repo who want agents to ask each other about API changes without a Slack detour. Less good if your policy forbids a third party relay: the README says a team can run its own relay.
More on real usage, who it suits and what to watch for: Reason Network use cases on Deduped. If you run Claude Code in CI too, see Claude Code Action.
Want the setup commands for 50 AI repos people actually ship with? Get the free AI Repos That Actually Ship pack: https://dedupedai.com/ship-pack/?utm_source=devto&utm_medium=article&utm_campaign=shippack
Top comments (0)