Engineering
Bot as dispatcher: hire Grok Build for the hard thinking
You burn Bot usage making the manager think like the specialist.
What hurt
Ryan Burt argues most people who hit a Grok Bot wall buy a higher plan or mint more bots — neither fixes the leak. Grok Bot is hands + a Linux box with no model picker; Grok Build (and other paid brains) already sit on the same credit card. Use the Bot as a dispatcher.
What to install or create
Teach one narrow job first (official order: successful task → skill → test → routine). Standing rule: do not think the expensive thought — collect files, hit sites, ask you to approve send, then hire Grok Build headless. Install Build on the Bot computer (`curl -fsSL https://x.ai/cli/install.sh | bash`), pin `default = "grok-4.6"` in config.toml, keep durable files in `/workspace`, reinstall after image rebuilds. Headless only — staring at the TUI double-bills. Caps on shared VM keys. After a real task, Bot usage should tick lightly while Build jumps.
Bots
Dispatcher
Hands and connectors. Collects context, hires Grok Build headless, returns a short result + file. Does not write the essay in chat.
Plugins
None on day one. Follow the first-run steps.
Files
Grok Build on the Bot Linux computer; durable work under /workspace.
Routines
None on the first run. Watch one manual pass first.
The prompt
This is a tip, not a pasteable system prompt. The author did not publish one. Follow the first-run steps.
First run
- 1Read https://x.com/RyanBURTio/status/2096343708073345175 and the Article “You already paid for the brain. Stop making Grok Bot use its own.”
- 2Pick one narrow job. Run it once successfully, save a skill only after zero fixes, test on a different input, then consider a routine.
- 3Install Grok Build on the Bot computer and pin grok-4.6 in config.toml. Keep work in /workspace. Add “if grok missing, reinstall” to the skill.
- 4Rewrite the standing rule: Bot collects and dispatches; Build thinks headless; chat reply stays about five lines + an attachment.
- 5Re-run a task that burned Bot credits last week. Confirm Bot usage barely moves while Build moves.
Approval fence
Do not send, spend, or paste secrets into chat. Cap keys on the shared VM. You approve irreversible steps.
What to tweak
One account, one Bot pool — more name tags are not more quota. Never schedule attempt #1. Dashboard-watching stays on the Bot; essay-length reasoning goes to Build.
Source
Ryan Burt @RyanBURTio · Original post
Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.