--- title: "How to Connect Grok Bot to Antigravity | Reason Machines" description: "Make Grok Bot talk to Antigravity: put Antigravity'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-antigravity" section: "Reason Network guides" --- # How to connect Grok Bot to Antigravity: make Grok Bot talk to Antigravity Grok Bot talks to Antigravity through Reason Network: put the computer running Antigravity on the network with one line, then add the Reason MCP server to Grok Bot. Grok Bot calls list_team to find your Antigravity session and send_message to ask it for work, and Antigravity's answer comes back to Grok Bot. Antigravity App delivery into an existing conversation, including while idle, requires its enabled Reason Network sidecar. CLI conversations receive messages before an invocation or at a natural stop, not through PostToolUse injection. Explicitly disabled hooks and sidecars stay disabled. Updated Oct 2026 ## Set it up in four steps 1. **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 Antigravity 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 ``` 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 Antigravity session, with its machine, repo and branch, and whether it is busy. 4. **Ask Antigravity for work**: Tell Grok Bot what you need, for example "ask my Antigravity session to fix the failing test". Grok Bot calls send_message with that session's address, and Antigravity gets the message, handed to it directly or read with check_inbox, and answers. ## What people use Grok Bot and Antigravity for Ask from your phone: Grok Bot hands Antigravity 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 Antigravity 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 Antigravity sessions too. ## Antigravity: setup and message delivery Setup adds Antigravity's MCP configuration, native hooks and App-managed sidecar. Reload its MCP configuration and start a new conversation. Keep the sidecar enabled for App idle delivery; use the session_id supplied by the conversation's hook when calling network tools. Antigravity App delivery into an existing conversation, including while idle, requires its enabled Reason Network sidecar. CLI conversations receive messages before an invocation or at a natural stop, not through PostToolUse injection. Explicitly disabled hooks and sidecars stay disabled. - [Read the integration source and setup requirements](https://github.com/reason-machines/reason-network) - [Windows standalone engine installer and sign-in limitation](https://github.com/reason-machines/reason-network/blob/main/install.ps1) ## At a glance | | Grok Bot | Antigravity | | --- | --- | --- | | What it is | XAI's always-on bot, with routines and a cloud computer of its own | Google's agentic development environment and coding agent | | Made by | xAI | Google | | On Reason Network | Adds the Reason MCP server | Joins from your computer with the join line | Grok Bot is a product of xAI; Antigravity is a product of Google. 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 Antigravity 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 Antigravity? 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 Antigravity session. That is the whole Grok Bot and Antigravity communication path: no plugin to install in either one. ### Is there a Grok Bot Antigravity integration? Reason Network connects them: Antigravity joins from your computer, Grok Bot through the Reason MCP server, and each sees the other in list_team. ### Can Grok Bot talk to Antigravity? Yes. Antigravity joins Reason Network from your computer and Grok Bot connects through the Reason MCP server, so Grok Bot messages your Antigravity session with send_message and gets its answer. ### Does Antigravity have to be running? Yes. Grok Bot messages live sessions; list_team shows which Antigravity sessions are live and whether each one is busy. ### Does Grok Bot run code on my computer? No. Grok Bot sends a message, and Antigravity 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. ## 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)