Engineering
First install: turn off Run on this computer (and traffic forwarding)
Phone → cloud bot → your Mac agent feels magical until prompt injection owns your desk.
What hurt
范凯说AI (@fankaishuoai) warns against letting cloud Grok Bot drive a Mac agent with skip-permissions: mail/web/X content can inject shell commands, local agents see SSH keys/.env/browser sessions, and the phone→remote path has no gate. His fix: turn off desktop "Run on this computer" and traffic forwarding; cloud bot only hands task notes; local agent decides how; sync via GitHub files—not reverse remote control. Not affiliated with xAI.
What to install or create
Lock desktop local-exec off; isolate cloud task notes from local execution via files.
Bots
Cloud dispatcher
Writes task notes only; never runs shell on your Mac.
Plugins
GitHub
Optional
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/fankaishuoai/status/2111978651797569600 (credit @fankaishuoai).
- 2In the Grok Bot desktop app: turn off Run on this computer and traffic forwarding through this Mac.
- 3Keep cloud bots on cloud computer only; put task briefs in a GitHub (or shared) file the local agent reads.
- 4If you need phone remote for a local agent, use a dedicated encrypted path—not cloud Grok Bot as a shell relay.
- 5Never enable skip-permissions for anything driven by untrusted mail/web/X content.
Approval fence
Anything that touches your Mac stays under a local gate you control. Never skip-permissions for cloud-driven shells.
What to tweak
Steal the install checklist: local execute off, no traffic forward, GitHub handoff only.
Source
范凯说AI @fankaishuoai · 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.