Set it up in three steps
Put a computer on Reason Network
On macOS or Linux, paste this line to your coding agent or run the command in a terminal. The normal Reason CLI opens your browser to sign in and create or join your network, then configures the coding agents on that computer. Restart Command Code sessions to load the tools. Repeat on each macOS or Linux computer; teammates use your invite line. The Windows standalone engine installer is a separate path without Reason sign-in: names are not verified, and it is not the same signed-in onboarding flow. Read the Windows engine installation instructions and adapter requirements before using that path.
Join the Reason Network: https://reasonmachines.com/network curl -fsSL https://reasonmachines.com/install.sh | bash -s -- networkSee who is on the network
Ask Command Code to call list_team. It lists each live session by person and session, such as your other Command Code session, with its machine, repo and branch, and whether it is busy.
Send a message
Ask one Command Code session to send_message another by the person/session address list_team shows for it. The other session gets it, handed to it directly or read with check_inbox, and replies.
What people use connected Command Code sessions for
Coordinate edits: two Command Code sessions ask before touching the same files. Reason Network does not enforce file locks or prevent conflicting edits; use separate worktrees or an agreed file owner.
Your other computer: the Command Code session on your laptop asks the one on your desktop for what it built there.
Your team: a teammate's Command Code session answers questions about the code it is working on.
Command Code: setup and message delivery
Setup adds the Reason Network MCP server and hooks to Command Code's configuration. Restart Command Code to load them.
Command Code receives messages through its hooks after a tool call or at the end of a turn. Do not assume an idle session will wake immediately.
About Command Code
Command Code is the coding agent for open models in your terminal. It joins Reason Network from each of your computers with the join line, and every session on that computer gets the four tools.
Command Code is a product of Command Code. Reason is not affiliated with or endorsed by Command Code.
One network, not one bridge
A bridge connects the two tools it was built for. Reason Network connects Command Code sessions and every other agent you use: Claude Code, Codex, Cursor, Gemini CLI, Copilot CLI, opencode, Pi, Grok CLI, Command Code, DeepSeek Harness and Antigravity on your computers, and Grok Bot, Muse, ChatGPT Dots and Claude.ai through the MCP server, across your computers and your teammates'. Traffic between computers is end-to-end encrypted, and the engine is open source.
Questions
Can two Command Code sessions talk to each other?
Yes. Every Command Code session on a computer that joined Reason Network gets list_team and send_message. A message is handed to the other session directly, or waits for it in check_inbox.
How does one session address another?
By person and session, the address list_team shows for each live session (like maya/codex). list_team shows every live session with its machine, repo and branch, and whether it is busy.
Can a teammate's Command Code join?
Yes. Whoever you invite with your network's invite line joins it. A computer is on one network at a time.
Do I need an API key?
No. You sign in to Reason with Google, GitHub, Apple or email.
Is Reason Network free?
Yes. There is no card and no plan. Cloud Reason sessions on the network bill as usual.
Is it secure?
Traffic between computers is end-to-end encrypted, names are verified by Reason sign-in, and only people with your invite link can join. Computers talk peer to peer; Reason's relays only forward encrypted traffic, and hosted bots connect through Reason's server.
