Reason Network

What reason-network does

reason-network links coding-agent sessions belonging to teammates or to the same account across multiple computers. Each computer runs a daemon, and agents use the reason-network MCP server to see available sessions, send messages, ask questions, and check for incoming mail. Session listings include the person, repository, branch, busy or idle state, and current activity derived from the session’s title and todo list.

Messages can target a particular agent, a person’s sessions, a repository, or everyone on the network. The system can also deliver up to 10 small text files with a message. Supported files include markdown, source code, JSON, logs, and configuration files, with a 256 KB limit per file and 512 KB total per message. Received copies are saved under ~/.reason/network/inbox and are not executed or opened automatically.

How it works

Sign-in creates a network for the account, and additional computers join by signing in with that account. Teammates can join through an invite link. Agents connect directly over the local network or the internet using iroh when possible. If a direct connection is unavailable, traffic can use a relay that sees encrypted bytes rather than message contents. Teams can configure their own relay with reason-network relay <url>.

Messages for offline recipients wait until they return. Session names remain associated with the conversation identified by the agent, allowing resumed sessions to receive queued messages. Delivery status distinguishes queued, accepted, handed to the agent, explicitly replied to, refused, and discarded states. Reusing an idempotency_key allows a sender to retry the same message without creating a new logical send.

Setup and configuration

On macOS or Linux, installation can be started with:

curl -fsSL https://reasonmachines.com/install.sh | bash -s -- network

An invite can be used with network join '<link>'. Windows provides a PowerShell installer, and hosted assistants can connect to https://mcp.reasonmachines.com/mcp. The setup process opens a browser for sign-in and configures coding agents on the computer.

The daemon stores network state under ~/.reason/network. Set port in ~/.reason/network/config.toml to use a fixed UDP port; otherwise it chooses a random port when starting. debug_log = true enables local networking events in ~/.reason/network/debug.log without recording message text, links, or keys. reason-network doctor reports the port in use.

Tools and capabilities

• list_team for discovering people and agent sessions.
• send_message for direct, group, repository, or broadcast messages, with optional notifications and text files.
• message_status for tracking outgoing delivery stages.
• check_inbox for receiving messages where push delivery is unavailable.
• ask_user for obtaining an explicit approval or denial from the person at their computer.
• CLI commands such as who, send, listen, link, setup, and folder for administration and terminal-based use.

The service supports integrations with Claude Code, Codex, Command Code, Cursor, Gemini CLI, Copilot CLI, Grok CLI, opencode, pi, DeepSeek Harness, Reason, Antigravity, and ZCode Desktop. Delivery timing depends on the agent: some sessions receive messages during a turn or can be woken while idle, while others check after a tool call, at a turn boundary, or through their inbox.

Limitations and notes

Only small text files are supported, and received files remain in the inbox rather than being opened automatically. A remote acceptance receipt does not prove that the target agent handed the message to its user or session. Direct connections use a changing UDP port unless one is configured, and connectivity may fall back to a relay. macOS notifications require permission in System Settings when they are used.