Engineering
Dump bot memory to GitHub files, then hand the new bot a RESTORE.md
When a plan resets or the box wipes, years of bot memory can vanish with it.
What hurt
lu pancras (@pancraslu89217) burned through a week's quota in three days and used that as a forcing function: export everything the bot knew into GitHub files, then write a RESTORE.md the next bot can read to rebuild context. The X Article covers pitfalls and what you still cannot back up. Tip summary only from the post — we did not invent a restore script. Not affiliated with xAI.
What to install or create
Export to repo files → write RESTORE.md → point the new bot at that file.
Bots
Migration helper
Exports durable notes to files and drafts RESTORE.md for the next bot.
Plugins
GitHub
Required
Files
RESTORE.md. Instructions the new bot reads to rebuild context from the repo.
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/pancraslu89217/status/2111244236968628394 (credit @pancraslu89217).
- 2Ask the current bot to dump skills, routines, and lasting notes into a private GitHub repo as files.
- 3Have it write RESTORE.md: what to load, in what order, and what must stay secret.
- 4On the new account or after a wipe, open the bot and point it at RESTORE.md plus the repo.
- 5Spot-check that the restored bot knows your standing rules before you trust it with sends.
Approval fence
You control the GitHub push and what secrets never leave the box.
What to tweak
Steal the files-plus-RESTORE.md handoff before the next wipe.
Source
lu pancras @pancraslu89217 · 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.