How to Back Up Your Grok Bots

If your Grok Bots are running your shop, “it’s on the computer” isn’t a backup.

Here’s what we actually set up — and a copy-paste prompt you can hand one of your bots so it builds the same thing.

What goes in git

• SOPs / ops playbooks (how the company runs)
• Custom skills and workflows
• Shared facts across bots
• Each bot’s profile, routines, and memory (no secrets)
• Non-secret tooling scripts
• A RESTORE.md plus a checklist of where secrets live (paths only)

One important detail: a Grok Bot project is a shared folder your bots join — not a single file. We put shared SOPs in one project (Ops Playbooks) so every bot loads the same operating brain.

What stays out

• Tokens, OAuth, API keys, Page tokens, .env
• Chrome cookies and saved passwords
• Full chat transcripts
• Plugin caches (reinstallable)

How we did it

1. Put shared SOPs in one project every bot joins
2. Created a private GitHub repo
3. Pushed a structured tree from the bot computer (working copy stays source of truth; git is the backup)
4. Scheduled a twice-daily sync (morning + evening) that only pushes when something changed — quiet otherwise
5. Real secrets live in a password manager; git only knows the file paths for restore

Honest caveat

Git restores knowledge, skills, and routines. It does not magically recreate live bots, channels, or connectors. After a wipe you: recreate agents from profiles, rejoin projects, re-auth connectors, then drop secrets from your password manager into the listed paths.

Paste this to one of your Grok Bots

Select all of the text in the box below (tap and hold on mobile), copy it, and paste it to a Grok Bot:

Create a private GitHub backup of this Grok Bot computer for disaster recovery.

Include: ops/SOP markdown projects, custom skills/workflows, shared user memory, each agent’s profile + routines + memory (no secrets), and non-secret tooling scripts. Add RESTORE.md explaining how to restore.

Exclude: all tokens/OAuth/connector secrets, Chrome cookies, chat transcripts, plugin caches.

Use a private repo I create (or create one if you can). Working copy on the bot computer stays source of truth. Set a twice-daily sync (morning + evening in my timezone) that pushes only when files changed; stay quiet when unchanged.

Also give me a checklist of secret file paths to store in my password manager (values never in git or chat).

Building in public with the same stack I use for local service owners — if you want an AI-built site without the agency bill, start at https://augenix.ai/build.