Back up Grok Bot memory when there is no export feature

Use this when you want a copy of what a Bot remembers before you reset, delete, or restructure it. No official memory export exists. xAI's docs say a Bot "can retain stable working preferences, important facts, and summaries from its work" and document no memory viewer, editor, or export (docs.x.ai/grok-bot/bots, checked 2026-09-25). Cursor's Grok Bot docs describe memory the same way and also document no export (cursor.com/docs/grok-bot/work, checked 2026-09-25). docs.x.ai has no separate Grok Bot memory page.

What the docs do say is to "Correct stale assumptions directly" in the conversation and to keep changing facts in the source system (docs.x.ai/grok-bot/bots, checked 2026-09-25).

Workaround 1: ask the Bot what it is working from (unconfirmed)

1. Open a one-to-one chat with that Bot.
2. Ask: List the preferences, facts, and summaries you are keeping for this role, as plain text.
3. Copy the reply into a file you control.
4. Correct anything stale in the same conversation, as the docs suggest.

This is ordinary chat. Neither Cursor nor xAI documents it as a backup method, and nothing confirms the reply covers everything the Bot has retained.

Workaround 2: staff-suggested zip backup

A Cursor staff reply (mohitjain, Sep 7, 2026, forum 170714) says a Bot's memory lives as plain text files on its computer, and the Bot can zip them and send them back. Another staff reply names memory/profile.md and memory/log/YYYY-MM.md as memory files (deanrie, Sep 16, 2026, forum 171895). This is a staff workaround and isn't in the docs, so file names and behavior can change without notice.

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, and open it to check that it holds what you expect.
4. Repeat for every Bot you care about. Memory belongs to each Bot, and a duplicate "does not copy conversation history, learned memory, or chat attachments" (docs.x.ai/grok-bot/bots, checked 2026-09-25).

The same staff thread suggests also asking for a SKILL.md per topic. No official SKILL.md format is documented, so review anything you promote into a skill.

Skills and shared files

Private skills are "one library shared by all your Bots" and can be listed under Settings → Plugins → Yours (xAI's docs call this Marketplace → Your plugins → Manage plugins and skills → Private skills; cursor.com/docs/grok-bot/work, checked 2026-09-25; docs.x.ai/grok-bot/skills-routines-and-automations, checked 2026-09-25). No skill download or export is documented. Asking a Bot to zip skill folders or other files on the shared computer is unconfirmed by Cursor or xAI. If an archive is large, ask the Bot to split it. The docs list a 25 MB limit per document attachment (docs.x.ai/grok-bot/files-and-results, checked 2026-09-25) and don't say whether files a Bot sends follow the same limit.

What no workaround covers

No export of connector logins is documented. A connectors list is a record of names only, so plan to reconnect plugins on a fresh account or after a wipe.

Related

• All how-tos: How-to index.
• Inspect or delete memory: Inspect and delete what a Grok Bot remembers.
• What a Bot keeps: What a Grok Bot remembers.
• When memory writes fail: When update_state memory fails with brain docs snapshot cut short.

Pitfalls

• Expecting a Settings → Export button. Neither doc set documents one.
• Treating the Bot's own summary as a complete copy of its memory.
• Converting every memory line into a skill wholesale, which freezes stale facts into instructions.
• Skipping per-Bot repeats and assuming one zip covers every roster member.