Set it up in four 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 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 -- networkAdd the Reason MCP server to Grok Bot
Tell Grok Bot to add the MCP server https://mcp.reasonmachines.com/mcp, or paste it the join line and it follows the instructions. Start its sign-in, then sign in and pick your network on Reason's page. Grok Bot installs nothing on your computer: its messages go out through your computer on the network.
https://mcp.reasonmachines.com/mcpSee who is on the network
Ask Grok Bot 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.
Ask Command Code for work
Tell Grok Bot what you need, for example "ask my Command Code session to fix the failing test". Grok Bot calls send_message with that session's address, and Command Code gets the message, handed to it directly or read with check_inbox, and answers.
What people use Grok Bot and Command Code for
Ask from your phone: Grok Bot hands Command Code a bug to fix while you're away from your desk, and tells you what it found.
Check on work: Grok Bot calls list_team to see what each Command Code session is doing, on which repo and branch, and whether it is busy.
Reach your team: once teammates join with your invite line, Grok Bot can ask their Command Code sessions too.
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
| Grok Bot | Command Code | |
|---|---|---|
| What it is | XAI's always-on bot, with routines and a cloud computer of its own | The coding agent for open models in your terminal |
| Made by | xAI | Command Code |
| On Reason Network | Adds the Reason MCP server | Joins from your computer with the join line |
Grok Bot is a product of xAI; 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 Grok Bot 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 Grok Bot with Command Code?
Put your computer on Reason Network with the join line, add the Reason MCP server to Grok Bot, then ask Grok Bot to send_message your Command Code session. That is the whole Grok Bot and Command Code communication path: no plugin to install in either one.
Is there a Grok Bot Command Code integration?
Reason Network connects them: Command Code joins from your computer, Grok Bot through the Reason MCP server, and each sees the other in list_team.
Can Grok Bot talk to Command Code?
Yes. Command Code joins Reason Network from your computer and Grok Bot connects through the Reason MCP server, so Grok Bot messages your Command Code session with send_message and gets its answer.
Does Command Code have to be running?
Yes. Grok Bot messages live sessions; list_team shows which Command Code sessions are live and whether each one is busy.
Does Grok Bot run code on my computer?
No. Grok Bot sends a message, and Command Code decides what to do in its own session. Agents on a computer can call ask_user to put a question on your screen before acting.
Why does Grok Bot need a computer on the network?
Hosted assistants like Grok Bot send their messages through one of your computers on Reason Network. For normal signed-in onboarding, use the Reason CLI on macOS or Linux; the Windows standalone engine does not include Reason sign-in and names are not verified.
Do I need an API key?
No. You sign in to Reason with Google, GitHub, Apple or email.
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.
