Ingeniería
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.
Qué dolía
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.
Qué instalar o crear
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
Obligatorio
Archivos
RESTORE.md. Instructions the new bot reads to rebuild context from the repo.
Rutinas
Ninguna en el primer uso. Mira primero una pasada manual.
El prompt
Esto es un consejo, no un prompt de sistema para pegar. El autor no publicó uno. Sigue los pasos del primer uso.
Primer uso
- 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.
Valla de aprobación
You control the GitHub push and what secrets never leave the box.
Qué ajustar
Steal the files-plus-RESTORE.md handoff before the next wipe.
Fuente
lu pancras @pancraslu89217 · Publicación original
Sin afiliación con xAI. No escribimos este prompt. Siguen aplicando las condiciones de las plantillas de terceros.
Paquete Pro
¿Quieres la configuración completa, no solo la idea?
Los paquetes Pro te dan el texto de la tarea, los prompts, los horarios y los tropiezos de los casos de uso más populares.