Export a Grok Bot memory backup

There is still no one-click export in Settings. Staff (mohitjain, Sep 7, 2026) documented a chat-driven zip backup on forum 170714: each Bot’s durable state lives as plain text on the shared cloud computer, and the Bot can zip it and attach the archive.

Inspect or delete without a zip: Inspect and delete what a Grok Bot remembers.

Back up one Bot

1. Open a one-to-one chat with that Bot.
2. Paste: Please make a full backup of your durable state. Make a folder backup/, copy your complete memory (profile + every memory-log entry, including older months) into memory.md, list your routines (schedule + prompt) in routines.md and your connectors in connectors.md, then zip the folder and send it here as an attachment.
3. Download the zip when it appears.
4. Repeat for every Bot you care about.

Optional add-on in the same prompt: also write a SKILL.md for each distinct topic in your memory and include it in the zip. Promote only reviewed procedures into skills later — raw memory and skills stay separate (forum follow-up on 170714).

Shared memory and skills

Ask your Chief of Staff (or whichever Bot owns shared facts):

Copy the shared memory all bots can see into shared-memory.md, zip the skills library folder, and send both here as attachments.

Other files on the computer

Name the folders that matter and ask any Bot to zip and send them. Attachments cap at 25 MB — ask the Bot to split larger archives.

What will not export

Connector logins cannot be exported. The connectors list is a record of names, not credentials. You reconnect plugins on a fresh account or after a wipe.

Pitfalls

• Converting every memory line into a skill wholesale — that freezes stale facts into instructions.
• Expecting a Settings → Export button that docs and staff have not shipped.
• Skipping per-Bot repeats and assuming one zip covers every roster member.