What a Grok Bot remembers

A Bot retains stable preferences, important facts, and summaries from its work so it can keep a role over time without replaying every prior message. Conversations and learned context stay separate per Bot. Shared files, browser sessions, and direct handoffs move context between Bots on your account. Official guide: Work with Grok Bot → What a Bot remembers.

What memory is for

Use memory for durable preferences, role context, and short summaries of prior work. Put safety boundaries and standing rules in the Bot's description, not only in memory, so they stay visible when you open Bot settings. Keep changing facts in the source system (CRM, sheet, ticket queue) and ask the Bot to cite or reopen current data before consequential decisions.

How to keep memory useful

1. Correct a stale assumption in the conversation as soon as you see it. Tell the Bot the corrected fact and that it should use the new version going forward.
2. Move standing rules into the description when they should shape every future task ("Never send external messages without approval").
3. For numbers, statuses, and lists that change, point the Bot at the live source instead of asking it to recall last week's snapshot.
4. After a long break, ask the Bot to restate what it believes about the role, then correct anything that drifted.

What memory does not replace

Memory is not an authoritative source. Do not rely on it for billing totals, live inventory, customer status, or anything you would verify before acting. Ask for source links, screenshots of current state, or a fresh pull from the connected system. Shared computer files and plugin data are also separate from learned memory; another Bot can open the same /workspace folder even when it does not share this Bot's conversation.

Pitfalls

• Storing approval boundaries only in memory — put them in the description so they stay in Bot settings.
• Treating last week's summary as today's truth — re-read the source for consequential work.
• Expecting memory to transfer when you Duplicate a Bot — the copy keeps profile and routines, not learned memory or conversation history.
• Assuming another Bot cannot see files this Bot wrote — the cloud computer is shared across your Bots.