Work
Closing the laptop doesn't stop your bot: 5 checks before you walk away
Grok Bot runs on a cloud computer, so closing the app is leaving the room, not switching off the worker.
What hurt
kocer (@kocer_eth) posted a five-item walk-away checklist: what is in flight, what can start later, what must wait for you, how to stop, and proof it stopped. A bot saying “understood” is not proof. Not affiliated with xAI.
What to install or create
Before stepping away, walk the five checks against each bot's active tasks and routine settings, not against what the bot says.
Bots
No new bot. Follow the first-run steps.
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/kocer_eth/status/2106813447069708663 (credit @kocer_eth).
- 2Work in flight: check each bot's active tasks and decide what should keep running.
- 3Work that can start later: review scheduled and event-triggered routines and pause any you don't want running while you're away.
- 4Actions that must wait: confirm sending, publishing, payments, deletion, and account changes still need your approval.
- 5Stop and verify: use the app's stop controls, pause routines separately, then inspect task status and routine settings to see what finished, what is still active, and what needs you.
Approval fence
Keep sending, publishing, payments, deletion, and account changes behind approval while you are away, and check the real approval settings.
What to tweak
Steal the checklist and keep it next to your bots. A closed laptop is not a cancelled job.
Source
kocer @kocer_eth · 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.