Engineering
The bot computer is a snapshot — save durable copies outside
Reset, Recover, and Update rebuild from the last saved copy; if the only copy was on the box, it's gone.
What hurt
@Y3510X argues demos treated the Bot computer as where work lives, but the computer is a snapshot. He treats Grok Bot as ephemeral: durable copies go to Notion, Drive, Docs, or GitHub as part of the run — e.g. a design-researcher bot's instruction includes where to save results. Tip/lesson. Not affiliated with xAI.
What to install or create
Treat computer as ephemeral · every run writes durable copy outside · path in the instruction.
Bots
Any research/build bot
Ends each run by saving results to the external store named in its instruction.
Plugins
None on day one. Follow the first-run steps.
Files
Instruction line: where durable results must be saved.
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/Y3510X/status/2113778771140747322 and the Article (credit @Y3510X).
- 2Pick a durable store you already use (Notion, Drive, Docs, or GitHub).
- 3Add to each important bot's instruction: where to save the durable copy as part of the run.
- 4Run one real task and confirm the external file exists after Reset would not matter.
- 5Keep treating the bot computer as a snapshot, not the archive.
Approval fence
You choose the durable store; bot writes there as instructed.
What to tweak
Steal the habit: external save is part of the run, not a later chore.
Source
Jesse @Y3510X · 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.