Grok Bot Memory: What Your Bot Remembers and How to Control It
Grok Bot memory is why a Bot gets better the longer you use it. A named Bot keeps your preferences, rules, key facts and a dated log of its work across every chat, so you don’t repeat yourself. There’s no memory screen, though. You see, fix and delete memories by asking the Bot in plain English. In the video below I show the newest Grok Bot update. Here’s exactly what a Bot remembers, what all your Bots share, and how to keep its memory accurate, from xAI’s official docs.
Key takeaways
A Bot saves preferences, rules, facts and a dated work log.
Each Bot has its own memory; your name and time zone are shared by all.
No memory screen: ask “What do you remember about me?”
Import memory from another AI assistant in Settings.
According to the Bots guide, a Bot keeps stable preferences, important facts and summaries from its work, so it can hold a role over time without replaying every old message. It saves lasting things such as:
How you like to work, and your preferences
Rules you ask it to keep, like “Always ask before you send an email.”
Facts about you, like your name and time zone
A dated log of what it has worked on with you
What it doesn’t keep in memory: logins, cards and contact details such as addresses and phone numbers. Those belong in Vault.
Personal Bots no longer have a description or a Bot settings page. To change what a Bot does, you tell it in chat, and it keeps the lasting rules in memory.
When a Bot saves something
A Bot decides on its own when something is worth keeping, and it doesn’t ask first. It often mentions a save in its reply, but not every save shows up in the chat.
To make sure it keeps something, say so: “Remember that I’m out every Friday.” A save made in one chat is remembered in all your chats with that Bot.
One fix from the 0.78.1 changelog (27 October 2026): two saves to the same memory at once no longer overwrite each other.
Want AI agents that remember how your business runs? Inside the AI Profit Boardroom you get step-by-step AI agent training, the Agent OS, ready-made automations for your business and four live coaching calls a week.
A few facts about you, like your name and time zone
All your Bots
Your Bot in a group chat
Its own memory, not shared with the other Bots, but everyone can read what it says
A voice chat
The Bot can draw on earlier calls and your recent chat with it
In a group chat your Bot can use what you told it privately. If something should stay out of a group chat, tell your Bot. Bots can also pass context through shared files, direct messages and handoffs, because they share one computer.
See, correct or remove a memory
There’s no memory screen for a personal Bot. Ask in chat instead:
To see it: “What do you remember about me?”
To correct it: “That’s out of date. I moved to Denver.”
To remove it: “Forget that I’m on the launch team.”
If a fact all your Bots share is wrong, tell any Bot the right version. To remove a shared fact completely, ask the Bot that saved it.
What resets or deletes memory
What you do
What happens to memory
Reset a conversation
Memory is kept
Delete a Bot
That Bot’s memory is deleted, including shared facts it saved
Delete your account
All your Bots’ memory is deleted
Duplicate a Bot (iPhone)
The copy gets skills and routines, but not learned memory
Want to keep a Bot’s memory but tidy your sidebar? Choose Hide from sidebar instead of Delete. Deleting can’t be undone.
Moving from another AI assistant? Open Settings → General and choose Start Import under Import. Copy the prompt into a chat with your old assistant, paste its answer into the second box, and choose Add to Memory. Grok Bot sends it to your primary Bot and opens that chat (settings guide). The phone app has the same option as Import Memory.
Shared Bots and team memory
A personal Bot’s memory is yours, and only you can change it. A shared Bot can save what it learns for the whole team and tells you when it does. It doesn’t save anything about you personally for the team, and a teammate’s shared Bot doesn’t get the facts your own Bots share about you. Managers on a shared Bot can change its memory, instructions, skills and apps.
Memory is not a source of truth
The docs are direct: memory is not a substitute for an authoritative source.
Keep changing facts, like prices or stock levels, in the source system.
Ask the Bot to reopen current data before an important decision.
Correct stale assumptions as soon as you spot them.
Back safety rules with approvals and Auto-review rules, not memory alone. The security guide notes Auto-review doesn’t review memory writes.
My verdict
Treat a Bot like a new hire: tell it your rules once, check what it knows with one question, and correct it when it’s wrong. Keep facts that change in your real systems and keep logins in Vault. Do that and Grok Bot memory turns each Bot into a teammate that knows how you work.
