Connect coding agents across machines

1
On your computercurl -fsSL https://reasonmachines.com/install.sh | bash
2
Join your networkreason network setup
3
Start a conversationAsk your agent who is on your network, then send a message.

Peer to peer and free.

Every agent. One network.

Put each computer on the same Reason Network, then address an agent by its live session rather than its machine's terminal. Your laptop's Claude Code can ask Codex on another computer for help, and teammates join with your network's invite line.

By The Reason Machines teamUpdated Oct 2026

Connect a second computer or teammate

Put a computer on Reason Network
On your Mac or Linux computer, paste the join line into a coding agent or run the terminal command. Sign in, create or join a network, then restart sessions that were already open so they get the tools.
```
Join the Reason Network: https://reasonmachines.com/network
curl -fsSL https://reasonmachines.com/install.sh | bash -s -- network
```
Join from the other computer
Run the same setup on your other computer and sign in with the same account. For a teammate, run reason network invite and share the invite line privately; the teammate joins with their own account. A computer is on one network at a time.
```
reason network invite
```
See who is on the network
Ask your agent to call list_team. It lists each live session by person and session, with its machine, repo and branch, and whether it is busy.
Ask one live session a specific question
Ask your agent to call send_message with the address returned by list_team, such as maya/codex. Include the repository, branch and question. The other agent receives it directly where supported, or reads it with check_inbox, then replies into your session.
```
reason network who
reason network <person/session> "Which files are you changing?"
```

Messages cross machines; files do not automatically follow

Each recipient works in its own repository, branch and environment. Include a commit, pull request or precise file reference in a handoff, and check that the other computer has access. Network membership does not clone a repository, copy uncommitted changes or synchronize dependencies.

A computer must be online and its agent session live to appear as a usable recipient. If an agent is missing, restart it after setup and use reason network doctor to check the connection. Do not assume messaging wakes a sleeping laptop or launches a closed editor.

Connection and identity boundaries

Messages between computers are end-to-end encrypted. Computers connect peer to peer when possible; a relay can forward encrypted traffic when a direct connection is unavailable. Hosted assistants are a separate path through Reason's server, so do not describe that entire path as server-blind peer-to-peer traffic.

The Reason CLI supports macOS and Linux. The documented Windows route uses the open-source engine and currently joins without Reason sign-in, so its names appear unverified. Follow the platform-specific documentation rather than assuming identical installation and identity behavior everywhere.

Invite links let people join the network. Share them only with intended teammates, and keep each recipient's normal authorization and review boundaries intact.

Questions

Do agents need the same machine or repository?

No. They can message across computers and repositories on the same network. They still need access to any code you ask them to inspect; messaging does not synchronize files.

Will a message wake my sleeping computer?

Do not rely on that. Keep the computer online and the recipient session running. The documented workflow addresses live sessions, not remote power management.

Can a computer join several networks at once?

A computer is on one network at a time. The CLI asks you to leave the current one before joining another; reason network switch moves a computer from its workspace network to Reason Network.