Memory mechanism: how the Bot remembers you and how to correct it
In the previous lesson it learned to "create something from nothing"; in this lesson, let's see how it "remembers you." Grok Bot memory (called memory in the official docs) is the underlying mechanism that makes it better to use over time: the Bot retains stable preferences, important facts, and work summaries, so it can maintain its role long-term without replaying all your historical messages every time.
The whole thing takes about 8 minutes, with no commands to run—viewing, correcting, and deleting memories all happen by "talking to it."
What you'll be able to do after this lesson
- Use a single "Remember that…" to make the Bot reliably remember your preferences or rules, effective long-term across chats
- Understand the sharing scope of memories: each Bot has its own, while a few facts about you (name, time zone) are shared across all Bots—once one learns it, all of them know
- View, correct, and remove what the Bot remembers right in the chat (the personal Bot has no memory settings page)
- Tell apart what Reset, deleting a Bot, and deleting your account each do to memory, so you no longer delete things by mistake
- Import memories from another AI assistant (Settings → General → Start Import), landing them in your primary Bot
Your current predicament
- Every new conversation means introducing yourself all over again: "who I am, which time zone, ask me before sending emails"—it does it once when told, and forgets if you don't
- It got your information wrong (you've moved, but it still schedules around the old city), and you want to fix it in settings, but there's no "memory" page anywhere
- You want to clear the context and start fresh, but you're afraid of losing preferences you've built up over weeks; you also worry that things you told it privately might get brought up in group chats
When to use this technique
When you need to:
- Have the Bot remember your working style, rules, name, and time zone long-term, without repeating yourself every time
- Have multiple Bots all know the basic facts about you—tell one, and the rest all know too
- After moving, changing roles, or updating workflows, correct outdated memories or delete what shouldn't have been remembered
And you don't want to:
- Dig through the settings interface for a memory management page—the personal Bot doesn't have one at all
- Lose the preferences you painstakingly built up just because you reset one conversation
- Have sensitive information like passwords, bank cards, addresses, and phone numbers end up in memory—those belong in the Vault
🎒 Before you start
- Completed 2.1 Messages and conversations: you can send messages and start chats—memory management is all done by "talking to it"
- Have at least one Bot of your own that you've given a task once (see 1.5 Your first Bot)
- If you want to import memories from an old assistant, be able to open that assistant's chat window
- A cup of water ☕—no commands to run in this lesson
Core idea
Grok Bot memory and chat history are two different things: conversation history is a message-by-message log, while memory is the stable preferences, important facts, and work summaries the Bot distills on its own. Precisely because it stores the stable stuff in memory, it can maintain its role across sessions without replaying historical messages every time.
It keeps things that are useful long-term; the official docs list four categories:
- The working style and preferences you like
- Rules you ask it to keep, such as "Always ask before you send an email."
- Facts about you, such as your name and time zone
- A dated work log of what you've done together
Three key mechanisms:
- The Bot decides what to save: it judges on its own what's worth remembering and won't ask you first; it often mentions in its replies what it saved, but not every save is shown in the chat
- Works across chats: what's remembered in one chat is remembered in all your chats with it
- Each Bot is independent, with a few shared facts: each Bot has its own memory; but a few facts about you (like name and time zone) are shared across all your Bots—once one Bot learns them, the other Bots know too
The division of labor between memory and conversation history, just to get familiar:
| Memory | Conversation history | |
|---|---|---|
| What's stored | Preferences, rules, facts about you, dated work logs | A message-by-message log |
| How it gets in | The Bot decides what to save; you can explicitly ask it to remember / forget | Every message you and the Bot send |
| After resetting a conversation | Kept | Starts over |
| After deleting a Bot | That Bot's memory is deleted | Deleted along with it |
Information like logins, bank cards, addresses, and phone numbers belongs in the Vault, not in memory—see 5.2 Vault and secure logins.
⚠️ Memory is not an authoritative source
The official docs are clear: facts that change should live in the source system; for important decisions, have the Bot cite or reopen current data rather than rely on memory; correct outdated assumptions as soon as you spot them; safety boundaries are backed by approvals and Auto-review rules, not by memory alone.
Follow along
Step 1: make the Bot remember a preference: say it explicitly with "Remember that…"
Why: the Bot decides on its own what's worth remembering without asking you first; it often mentions saves in its replies, but not every save is shown in the chat. To make sure it remembers, you must say so explicitly.
Official example (swap in your own content and send it directly):
Remember that I'm out every Friday.
It works the same in Chinese—just put "remember" at the very front:
Remember: I'm away every Friday, don't schedule meetings on Fridays.
You should see: The Bot confirms in its reply that it has noted this. Note: Not seeing the words "saved" doesn't mean it wasn't recorded — not every save is displayed in the chat.
- Had the Bot remember one of your real preferences (e.g., you're unavailable on Fridays, or ask before sending emails)
Step 2: View Grok Bot memory: ask in chat, there is no memory settings page
Why: A personal Bot has no memory interface — you won't find a "memory management" page in Settings; the officially recommended way is simply to go back to the chat and ask.
Official example:
What do you remember about me?
You should see: The Bot lists what it remembers — typically your preferences, rules you've set, facts about you, and a summary of recent work with you.
- Asked "What do you remember about me?" once and saw the list it produced
Step 3: Correct outdated memories: just tell it the correct version
Why: Memories go stale — after moving, changing roles, or changing workflows, old memories cause trouble instead. One of the official tips for efficient conversations: explicitly correct persistent preferences — say it directly; don't count on it noticing on its own.
Official example:
That's out of date. I moved to Denver.
You should see: The Bot updates the memory with the new version you gave, and subsequent arrangements follow the new information.
Shortcut for correcting shared facts: For facts like your name or time zone that are shared across all Bots, just tell any one Bot the correct version — no need to fix them one by one.
Step 4: Remove a memory: have the Bot that saved it forget it
Why: If you don't want it to keep remembering something (e.g., you left that project team long ago), say "forget it" explicitly.
Official example:
Forget that I'm on the launch team.
You should see: The Bot confirms it has forgotten this and no longer references it afterward.
The rule for removing shared facts differs from correcting them: to correct content, telling any Bot works; to completely remove a fact shared across all Bots, the official requirement is to tell the Bot that saved it.
- Removed a memory, or can state "for corrections, go to any Bot; for complete removal, go to the Bot that saved it"
Step 5: Distinguish Reset from deletion: which operations affect memory
Why: This is the easiest trap to fall into — deleting the Bot to "start over," losing weeks of accumulated preferences; or assuming Reset clears memory, when it in fact preserves it.
Official comparison table:
| Your action | What happens to memory |
|---|---|
| Reset a conversation(reset the conversation) | Preserved |
| Delete a Bot(delete the Bot) | That Bot's memory is deleted |
| Delete your account(delete your account) | The memory of all your Bots is deleted |
You should see: Nothing to do — check against the table above; all three rows' consequences match. When you want to "start over," first distinguish whether you want to restart the conversation or delete the Bot along with its memory.
Three additional notes, all common points of confusion:
When a message is blocked, the prompt may show Reset; selecting it displays Reset this conversation? — the conversation history starts over, but the Bot's memory, files, routines, and settings are all preserved
Deleting a Bot erases its profile, conversations, memory, routines, and attachments, including shared facts it saved for other Bots, irreversibly. If you may still need that work later, or want to keep the Bot's memory, use Hide from sidebar instead of deleting
Duplicate(duplicate a Bot) carries over the profile, settings, enabled skills, routines, and avatar, but does not carry over conversation history, learned memory, or attachments — the new copy needs your preferences explained again
Can recite: Resetting a conversation keeps memory; only deleting a Bot deletes its memory (along with shared facts)
Step 6: Import memory from another AI assistant: Settings → General → Start Import
Why: Switching from another assistant, you don't have to teach from scratch — the official import channel brings over "what the other assistant knows about you" in one go.
Four steps (official process):
- Open Settings → General, and under Import select Start Import
- Copy the prompt given by the Grok Bot and send it in a chat with another assistant
- Paste that assistant's reply back into the Grok Bot's second input box
- Select Add to Memory
You should see: The Grok Bot sends the imported content to your primary Bot (the main point of contact Bot, which proactively checks in and coordinates other Bots; see 1.5 Your first Bot) and opens that chat — the imported memory takes effect from there.
- Found the Import entry under Settings → General (you don't have to import; just knowing where it is counts)
Checkpoint ✅
- Used "Remember that…" to have the Bot remember a real preference
- Asked "What do you remember about me?" and saw the list of what it remembers
- Corrected or removed a memory, or can state the official wording for both
- Can recite: Resetting a conversation keeps memory; deleting a Bot deletes its memory (including shared facts, irreversibly)
- Know that sensitive information (logins, cards, addresses and phone numbers) goes in the Vault, not in memory
Pitfall reminders
❌ Searching Settings for a "memory management" page
Symptom: Wanting to view or edit what the Bot remembers, you searched all through Settings and found no memory page.
Cause: A personal Bot has no memory interface — official wording: "There is no memory screen for a personal Bot. Ask in chat instead."
Correct approach: Go back to the chat and just say it — to view: "What do you remember about me?"; to correct: "That's out of date. …"; to remove: "Forget that …".
❌ Wanting to start over and just deleting the Bot
Symptom: Wanting to clear the context and "start over," you right-clicked and deleted the Bot — preferences, rules, and work logs all gone, irreversibly.
Cause: Deleting a Bot erases its profile, conversations, memory, routines, and attachments, including shared facts it saved for other Bots.
The right way: If you only want to restart the conversation, use Reset in the interception prompt (conversation history restarts, memory is kept); if you want to remove it from the list but keep the Bot and its memory, use Hide from sidebar.
❌ Having the Bot "remember" passwords, bank cards, addresses, and phone numbers
Symptom: You have the Bot remember login passwords or card numbers, thinking it saves effort next time.
Why: The official stance is clear—Logins, cards, and contact info (addresses, phone numbers) belong in the Vault, not in memory.
The right way: Put sensitive credentials in the Vault (the Bot never sees the values); see 5.2 Vault and secure logins. Memory is only for preferences, rules, and non-sensitive facts.
❌ In a group chat it goes back to private chat to reply, or brings private matters into the group
Symptom: You assign work in a group chat, but the Bot replies to you in private chat; or things you told it privately show up in the group chat—everyone in the group can read what it says.
Why: In group chats, your Bot can use what you told it privately; "where to reply" is not a default rule either.
The right way: In the group, say explicitly "Reply here in the group. Don't message me privately about this."; to make it a long-term rule, have each Bot remember: "Remember: in group chats, reply in the group."; for things that shouldn't go into the group, tell it in advance not to bring them in.
Advanced tips (optional)
Voice chats also use memory. During a voice chat, the Bot can draw on your previous calls and recent chats; after hanging up, you can ask it in the chat what was said in that call.
Memory boundaries of Team Bots. A team-shared Bot can save what it learns for the whole team and will tell you; team rules taught to it by a Collaborator only take effect after being approved by an Owner or Manager in Review learnings (see Team Bot: One Bot for the Whole Team); it will not save anything about you personally to the team—the details of its collaboration with you that it remembers remain between you and it. A teammate's Team Bot also cannot access facts about you shared by your own Bot.
Don't use memory as a database. Memory handles "preferences," not "truth": for important decisions, have the Bot cite current data and go through approvals; safety boundaries rely on approvals and Auto-review rules—not on "it remembers you said it was okay."
Lesson summary
✅ The main thread of Grok Bot memory: the Bot decides on its own to save stable preferences, important facts, and work summaries; to make sure something is remembered, say explicitly "Remember that…".
✅ Sharing scope: memory works across chats; each Bot has its own; a few facts about you (name, time zone) are shared across all Bots—to correct one, ask any Bot; to fully remove one, ask the Bot that saved it.
✅ All management happens in chat: view with "What do you remember about me?" / correct with "That's out of date. …" / remove with "Forget that …"—personal Bots have no memory settings page.
✅ Consequences of actions: Reset keeps memory while resetting the conversation; deleting a Bot deletes its memory (including shared facts, irreversible); deleting your account deletes all memory; Duplicate doesn't carry memory.
✅ Sensitive information (logins, cards, addresses, phone numbers) belongs in the Vault; memory is not an authoritative source—for important decisions, have the Bot check current data.
✅ Switching assistants: Settings → General → Import → Start Import → paste the answers → Add to Memory, which lands on your primary Bot.
Key actions recap:
| Action | What to say / where to find it | Effect on memory |
|---|---|---|
| Have it remember | "Remember that I'm out every Friday." | Saved, works across chats |
| View | "What do you remember about me?" | Read-only |
| Correct | "That's out of date. I moved to Denver." | Updated; for shared facts, tell any Bot |
| Remove | "Forget that I'm on the launch team." | Deletes one entry; for shared facts, ask the Bot that saved it |
| Reset conversation | Reset in the interception prompt (Reset this conversation?) | Keeps memory, files, routines, and settings |
| Delete Bot | Right-click in the sidebar Delete | Deletes that Bot's memory + the shared facts it saved, irreversible |
| Import memory | Settings → General → Import → Start Import | Added to memory, lands on the primary Bot |
Next lesson preview
It remembers you now; in the next lesson, we'll connect it to your tools. Next lesson: 2.5 Connect apps (plugins).
You will learn:
- 5 steps to connect Gmail, Slack, Calendar, and other apps (about 10 minutes)
- Added ≠ logged in: how to handle the Needs auth / Disconnected states
- Each plugin's capability limits: Calendar can't add Zoom links, Slack posts as you
- How to get past Google admin review (Your admin needs to review Grok)