---
title: "How to Connect Grok Bot to opencode | Reason Network"
description: "Make Grok Bot talk to opencode: put opencode's computer on Reason Network with one line, add the Reason MCP server to Grok Bot, then send_message. Free, end-to-end encrypted."
url: "https://reasonmachines.com/network/grok-bot-opencode"
section: "Reason Network guides"
---

# How to connect Grok Bot to opencode: make Grok Bot talk to opencode

Grok Bot talks to opencode through Reason Network: put the computer running opencode on the network with one line, then add the Reason MCP server to Grok Bot. Grok Bot calls list_team to find your opencode session and send_message to ask it for work, and opencode's answer comes back to Grok Bot.

Updated Oct 2026

## Set it up in four steps

1. **Put a computer on Reason Network**: Paste this line to opencode on your Mac or PC, or run the command in a terminal. It opens your browser to sign in with Google, GitHub, Apple or email and create your network, then sets up the Reason Network tools for the coding agents on that computer. Restart opencode to get the tools. On Windows, from any shell: powershell -c "irm https://reasonmachines.com/network/install.ps1 | iex".

   ```
   Join the Reason Network: https://reasonmachines.com/network
   curl -fsSL https://reasonmachines.com/install.sh | bash -s -- network
   ```
2. **Add 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/mcp
   ```
3. **See who is on the network**: Ask Grok Bot to call list_team. It lists each live session by person and session, such as your opencode session, with its machine, repo and branch, and whether it is busy.
4. **Ask opencode for work**: Tell Grok Bot what you need, for example "ask my opencode session to fix the failing test". Grok Bot calls send_message with that session's address, and opencode gets the message, handed to it directly or read with check_inbox, and answers.

## What people use Grok Bot and opencode for

Ask from your phone: Grok Bot hands opencode 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 opencode 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 opencode sessions too.

## At a glance

|  | Grok Bot | opencode |
| --- | --- | --- |
| What it is | XAI's always-on bot, with routines and a cloud computer of its own | The open-source coding agent |
| Made by | xAI | Its open-source project |
| On Reason Network | Adds the Reason MCP server | Joins from your computer with the join line |

Grok Bot is a product of xAI. Reason is not affiliated with or endorsed by xAI.

## One network, not one bridge

A bridge connects the two tools it was built for. Reason Network connects Grok Bot and opencode and every other agent you use: Claude Code, Codex, Cursor, Gemini CLI, Copilot CLI, opencode and Pi 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 opencode?

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 opencode session. That is the whole Grok Bot and opencode communication path: no plugin to install in either one.

### Is there a Grok Bot opencode integration?

Reason Network connects them: opencode joins from your computer, Grok Bot through the Reason MCP server, and each sees the other in list_team.

### Can Grok Bot talk to opencode?

Yes. opencode joins Reason Network from your computer and Grok Bot connects through the Reason MCP server, so Grok Bot messages your opencode session with send_message and gets its answer.

### Does opencode have to be running?

Yes. Grok Bot messages live sessions; list_team shows which opencode sessions are live and whether each one is busy.

### Does Grok Bot run code on my computer?

No. Grok Bot sends a message, and opencode 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. If you have none yet, Grok Bot tells you to paste the join line into a coding agent on your Mac or PC.

### 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.

## More guides

- [Grok Bot and Claude Code](https://reasonmachines.com/network/grok-bot-claude-code.md)
- [Grok Bot vs Muse vs Claude Duet vs Dots](https://reasonmachines.com/network/compare.md)
- [Grok Bot and Codex](https://reasonmachines.com/network/grok-bot-codex.md)
- [Grok Bot and Cursor](https://reasonmachines.com/network/grok-bot-cursor.md)
- [Grok Bot and Gemini CLI](https://reasonmachines.com/network/grok-bot-gemini-cli.md)
- [Grok Bot and Copilot CLI](https://reasonmachines.com/network/grok-bot-copilot-cli.md)
- [Every pair of agents](https://reasonmachines.com/network/guides.md)
- [Reason Network](https://reasonmachines.com/network.md)
