All plays › Other

86’d · What not to do
OtherGrok Bot

Never keep your bot team’s only copy on the bot’s computer

What happened

self-reported

A silent rollback of his shared Grok Bot computer wiped hours of files for 15+ bots in under a minute.

Eric Kang runs 15+ bots on one shared Grok Bot computer. When it was rolled back, their files went with it, and other users, including a plumbing-company owner, posted similar losses the same week. His fix: back up every bot’s role, prompts, routines and working files to a private GitHub repo every night.

Who did it

Eric Kang (@BeatAPIio)BeatAPIEric Kang on X · Oct 17, 2026

Try it now

The safe way to do this instead:

  1. Create a private GitHub repo for your bot system.
  2. Put every bot’s role, prompts, routines, skills and working files in it.
  3. Have one bot push the key folders every night, and tag a known-good restore point.
  4. Never commit passwords or tokens. If the box resets, connect GitHub and tell your bot to restore from the tag.
Copy-paste prompt
Every night at [time], copy these folders into my private GitHub repo [repo name] and push: [bot roles, prompts, routines, skills, working files]. Never include passwords, API keys, tokens or .env files; if you find one, skip it and tell me. Every Friday, tag the latest good version as restore-[date]. If you ever start up and these folders are missing or older than yesterday, stop and tell me before doing anything else.

Want this set up on your own site?

Build it with Page

What to watch out for

Back up anything you can’t afford to rebuild, and keep secrets out of the repo. This is a lesson from his own loss, not a vendor claim. Build it with Page: keep your important business files on hosting you own, not only on a bot’s computer.

Did it work?

PageMotor keeps this site free.