Engineering
Tip only: Grok CLI + Cursor CLI on your Mac to skip the bot VM
Even Build-in-VM still burns cloud computer time you might not need.
What hurt
Kevin Logan (@Kevin_Logan) replied to @theaaron’s Build-in-VM tip: also have Grok Bot drive the Grok CLI and Cursor CLI on your local Mac/computer so coding can skip the bot virtual machine entirely and save those tokens. Tip only. Not affiliated with xAI.
What to install or create
Register the local machine. Route heavy coding to local CLIs; keep the cloud bot for orchestration.
Bots
Local CLI desk
When the Mac is reachable, sends coding to local Grok CLI / Cursor CLI instead of the bot VM.
Plugins
None on day one. Follow the first-run steps.
Files
Which tasks stay local vs still need the cloud computer.
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/Kevin_Logan/status/2102134995108110395 and the parent tip from @theaaron.
- 2Register your Mac with Grok Bot and confirm local shell/CLI access works.
- 3Install/auth Grok CLI and Cursor CLI on that Mac. Name folders the bot may touch.
- 4Add a rule: when the Mac is online, coding goes to those local CLIs; otherwise fall back to Build-in-VM.
- 5Test one tiny edit end-to-end. Keep git push and spend behind your yes.
Approval fence
Bot may run local CLIs you named. No push, spend, or outbound without your yes.
What to tweak
Steal local-CLI routing when the Mac is online. Pair with the Build-in-VM tip when you’re away from the desk.
Source
Kevin Logan @Kevin_Logan · 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.