Skip to content
UsecaseBoard
← All use cases
blogGrok-Bot

Grok Bot orchestrates; Grok Build (or Cursor) does the heavy coding

At a glance

Common xAI stack pattern (confirmed by @grok replies and power users): keep Grok Bot as the always-on teammate that plans, researchs, and hands off; route multi-file coding to Grok Build CLI (`curl -fsSL https://x.ai/cli/install.sh | bash`—plan mode, parallel subagents, skills) or Cursor cloud agents. Bot’s cloud computer can still clone/run code, but dedicated local/repo coding stays cheaper and more controlled on Build. This workflow is listed under Grok-Bot, Grok-Build, orchestration, coding-agents, hand-off.

Agents / tools
Grok Bot, Grok Build, Cursor

Building a tool for these workflows? Sponsor / inquire.

Save ideas in this browser. Upvotes count across the board.

Prompt excerpt

Bot: plan [feature], then hand implementation to Grok Build on this repo with plan-mode review. Keep send/merge/spend approvals with me.
Explore all →
productGrok-Bot

roborev: continuous local code review that drives Grok Build

MIT Go daemon + git hook reviews every commit with the CLIs you already pay for—Codex, Claude Code, Cursor, OpenCode, and first-class Grok Build (grok / grok-build). Findings stay in a ledger until closed; agent hooks push open review IDs back into the session for /roborev-fix before context goes cold. Reviews stay on your machine.

roborevGrok BuildGrok Bot+3
Source ↗
xGrok-Bot

Lingxi’s Engineer Bot: board work, launch cloud agents, watch PRs

Night Orders Studio’s Grok Bot Chief of Staff describes the same hybrid SpaceXAI ships: hand coding to Cursor cloud agents and a Grok Build terminal, while a desk of agents (Build, Legal, Tester, App Store) checks every build and one human signs off. Lingxi Li’s Engineer Bot on the Grok Bot Marketplace packages the supervisor lane—board work on the repo you name, launch cloud agents, watch PRs ~every 30 minutes, only ask you to merge.

Grok BotLingxi's Engineer BotGrok Build+1
Source ↗
docsGrok-Bot

Grok Bot templates: share a bot as a recipe, not a clone

Official xAI guide: Share as Template packages instructions, skills, routines and first-party plugins into an anonymized blueprint (team or public link)—no secrets, custom code, MCP servers, logins or history. Installers get a fresh bot that must re-approve plugins; encode setup steps for API keys and custom MCP so others can reproduce the workflow.

Grok BotGrok Bot MarketplaceCursor
Source ↗
blogGrok-Bot

Ledger Agent Intent: Grok Bot and Muse propose, you approve on hardware

Ledger’s Agent Intent queue lets background agents (Grok Bot, Muse, Hermes, OpenClaw, Dots) prepare actions—e.g. Grok Bot watches an inbox and drafts an invoice payment—while you review asynchronously and physically confirm on a Ledger signer Secure Screen. Agents never hold signing keys; coding agents can use Agent Stack CLI/skills too.

Ledger Agent IntentGrok BotMeta Muse+3
Source ↗