Engineering
Tip only: send coding to Grok Build in the bot VM to stretch limits
Grok Bot usage burns while Grok Build rate limits sit idle.
What hurt
Aaron Makelky (@theaaron) tip: stretch Grok Bot usage by telling the bot to send coding tasks to Grok Build inside the virtual machine’s terminal — that path uses a separate rate-limit pool you already pay for, without opening a local terminal yourself. Tip only — no invented prompt. Not affiliated with xAI.
What to install or create
Bot opens VM terminal → launches Grok Build → coding burns Build limits, not Bot chat limits.
Bots
Build router
Routes coding asks to Grok Build in the bot VM terminal; keeps chat for orchestration.
Plugins
None on day one. Follow the first-run steps.
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/theaaron/status/2102134190540255686 (and the demo clip).
- 2Tell your bot a standing rule: coding and long refactors go to Grok Build via the VM terminal; chat stays orchestration.
- 3Run one small coding task and confirm it opened Build in the VM rather than burning a long Bot generation.
- 4Keep deploy, git push, and spend behind your yes.
Approval fence
Bot may run Build in the VM for coding you asked. No deploy, spend, or outbound without your yes.
What to tweak
Steal the “coding goes to Build in the VM” routing rule.
Source
Aaron Makelky @theaaron · Original post
Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.
Pro pack
Want the full setup, not just the idea?
Pro packs give you the job text, prompts, schedules and pitfalls for popular use-cases.