Make Claude Code talk to Command Code.

1
On your computercurl -fsSL https://reasonmachines.com/install.sh | bash
2
Join your networkreason network setup
3
Start a conversationAsk Claude Code to message your Command Code session.

Peer to peer and free.

Every agent. One network.

Run one line on your computer and Claude Code and Command Code both join Reason Network with the same four tools. Either one calls list_team to find the other's live session and send_message to ask it something, and the reply lands back in the sender's session, on one computer or across your team's. 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.

By The Reason Machines teamUpdated Oct 2026

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 Claude Code and Command Code 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 -- network
```
See who is on the network
Ask Claude Code to call list_team. It lists each live session by person and session, such as your Command Code session, with its machine, repo and branch, and whether it is busy.
Send a message
Ask Claude Code to send_message your Command Code session, for example "ask Command Code to review my diff". Command Code gets it in its session and replies; Command Code can message Claude Code the same way. Before the restart, the CLI does the same from a terminal.
```
reason network who
reason network <person/session> "<message>"
```

What people use Claude Code and Command Code together for

A second opinion: Claude Code asks Command Code to review its change before you open the pull request.

Split work: Claude Code in one repo asks Command Code in another for the change it depends on.

Coordinate edits: before editing a file, Claude Code asks the Command Code session on the same repo what it is changing. Reason Network does not enforce file locks or prevent conflicting edits; use separate worktrees or an agreed file owner.

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.

At a glance

	Claude Code	Command Code
What it is	Anthropic's coding agent in your terminal	The coding agent for open models in your terminal
Made by	Anthropic	Command Code
On Reason Network	Joins from your computer with the join line	Joins from your computer with the join line

Claude Code is a product of Anthropic; Command Code is a product of Command Code. Reason is not affiliated with or endorsed by them.

One network, not one bridge

A bridge connects the two tools it was built for. Reason Network connects Claude Code and Command Code 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

How do I use Claude Code with Command Code?

Run the join line once on each computer; Claude Code and Command Code both get the Reason Network tools. Ask Claude Code to send_message your Command Code session, and Command Code's reply comes back into Claude Code: Claude Code and Command Code communication in both directions.

Is there a Claude Code Command Code integration?

Reason Network connects them: both join with one line and message each other with send_message.

Can Claude Code and Command Code work together?

Yes. On Reason Network both are live sessions that message each other: Claude Code can ask Command Code for a review, and Command Code can ask Claude Code a question, without you copying text between them.

Do Claude Code and Command Code have to be on the same computer?

No. Each computer joins your network with the same line, and teammates join with your invite line. A computer is on one network at a time.

When does a message arrive?

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.

Can Grok Bot or Muse reach Claude Code and Command Code too?

Yes. Grok Bot, Muse and ChatGPT connect through the Reason MCP server, see Claude Code and Command Code in list_team and message them the same way.

Is it open source?

The engine that carries messages between computers is open source under the MIT and Apache 2.0 licenses, at github.com/reason-machines/reason-network. The Reason CLI that sets it up is free to use, but not open source.