Grok Bot Memory: Seed, Audit And Clean It In 5 Steps (2026)

Grok Bot memory is what turns a Bot from a chat window into a teammate that keeps your rules, your preferences and a dated log of the work it did with you.

This is the setup I'd run on a fresh Bot: seed it, import from your old assistant, audit it, clean it, and know exactly what each delete button wipes.

Every step below comes from the official What a Bot remembers docs and the Grok Bot changelog.

Want a second pair of eyes on your agent setup? Book a free SEO strategy session with my team.

What Grok Bot memory actually stores

The docs list four kinds of lasting things a Bot keeps.

How you like to work, and your preferences.
Rules you ask it to keep, such as "Always ask before you send an email."
Facts about you, like your name and time zone.
A dated record of the jobs it has handled with you.

That's it: stable preferences, important facts and summaries, not a replay of every message.

Logins, cards, addresses and phone numbers don't go in memory.

They go in Vault, which is built to fill them in at sign-in or checkout.

Personal Bots no longer have a description or a Bot settings page, so memory is now where a Bot's job lives.

To change what a personal Bot does, you tell it in chat and it stores the lasting rule.

Step 1: Seed the Bot's memory in the first message

The Create a Bot steps say to give the Bot its job, sources and approval boundaries in your first message, and ask it to remember them.

Do that before you send any real task.

Here's the shape I use.

Your job: own the weekly SEO report for my agency. Sources: Search Console and the shared reports folder. Boundary: never send anything to a client without my approval.

Remember all three of these as lasting rules.

Then send a real first task with a clear finish line.

Keep lasting rules apart from one-off tasks.

"From now on, never send external messages without approval" is a rule worth saving.

"Draft follow-ups for these twelve accounts" is a task, so don't ask it to remember that.

Step 2: Import Memory from your old assistant

If another AI assistant already knows you, don't retype it.

Grok Bot added Import Memory to Grok Bot in Settings with release 0.68.0, per the changelog.

Open Settings, then General.
Under Import, choose Start Import.
Copy the prompt it gives you into a chat with your other assistant.
Paste that assistant's answer into the second box.
Choose Add to Memory.

The import goes straight to your primary Bot, and that chat opens, as the Settings docs confirm.

So check which Bot is primary before you import.

A shared Bot can't be your primary Bot, so the import always lands on one of your own.

The phone apps list Import Memory in Settings too, per the mobile docs.

Read the pasted answer before you hit Add to Memory.

Strip any passwords, card numbers or addresses out of it, because those belong in Vault.

🔥 Want my exact Bot-seeding prompts and memory checklists?
Inside the AI Profit Boardroom you get step-by-step video trainings, the installable Agent OS, four coaching calls a week and 3,400+ members setting up agents like this one.
→ Join the AI Profit Boardroom

Pick your primary Bot before you import

The import always lands on your primary Bot, so choose that Bot on purpose.

Your primary Bot is your main point of contact, and it checks in with you and coordinates your other Bots, per the primary Bot section.

If you don't have one, Grok Bot shows Introducing your primary Bot.

Choose Create primary Bot, or pick an existing Bot and choose Confirm.

To switch later on desktop, right-click the current primary Bot in the sidebar and choose Replace with different Bot.

On iPhone and Android, the option is Replace Primary Bot… in the Bot's menu.

I make the coordinator Bot primary, then import, so the general context sits with the Bot that hands work to the others.

Step 3: Force a save when it matters

A Bot decides on its own when something is worth keeping, and it doesn't ask first.

You'll usually see it mention a save, though some saves never appear in the conversation.

So when a fact must stick, say it plainly: "Remember that I'm out every Friday."

That one word, remember, is the difference between hoping and knowing.

Since v0.78.1 on 27 October 2026, two saves to the same memory at the same moment no longer overwrite each other.

An earlier fix, in v0.59.0, made Bots with a lot of saved memory reply without a several-second pause and save and forget reliably.

Write rules the Bot will actually keep

Short, testable rules survive best.

"Be careful with clients" is vague, and the Bot has to guess what you meant.

"Always ask before you send an email" is the exact example the docs use, and you can check it.

I write each rule as one line with a verb, an object and a limit.

Remember these lasting rules: - Always ask before you send an email. - Never change a client account without approval. - Write reports in British English.

- My working hours are 9 to 5, Monday to Thursday.

Then I ask the Bot to read them back, so I know each one saved.

Step 4: Audit it with one question

There is no memory screen for a personal Bot.

You audit it in chat.

What do you remember about me?

Ask that after the import, and again once a week.

Read the answer line by line and flag anything stale, wrong or private.

Step 5: Correct and forget, and the shared-fact catch

Correcting is a normal message: "That's out of date. I moved to Denver."

Removing is a normal message too: "Forget that I'm on the launch team."

Here's the catch.

Each Bot has its own memory, but a few facts, such as your name and time zone, are shared by all your Bots.

A wrong shared fact can be fixed by telling any of your Bots.

Wiping one out for good takes a request to whichever Bot stored it first.

So if a fact keeps coming back, find the Bot that first learned it and ask that one to forget it.

How memory moves across chats, calls and group chats

Since v0.75.2 on 22 October 2026, what a personal Bot saves in one chat it remembers in all your chats with it.

Voice calls pick up your earlier calls and your latest chat, and once you hang up you can quiz the Bot about the call in text.

Group chats need more care.

Your Bot can use what you told it in your private chat.

Each Bot in the group keeps its own memory, and your Bot's memory isn't shared with the other Bots there.

But everyone in the group can read what your Bot says.

If something should stay out of a group chat, tell your Bot before you add it.

Reset, hide, delete: what each one does to memory

This table is the one I check before touching any button.

Action	What happens to memory
Reset a conversation	Kept, along with files, routines and settings
Hide from sidebar	Kept; the Bot stays active
Duplicate on iPhone	The copy gets no learned memory or history
Delete a Bot	That Bot's memory is erased, including shared facts it saved
Delete your account	Every Bot's memory goes

Deleting a Bot can't be undone, per the Bots docs.

Since v0.75.2 it also removes the Bot's Slack app.

Files and sign-ins on the shared computer aren't isolated per Bot, so they can stay behind after a delete.

If you might want the work or the memory later, choose Hide from sidebar instead.

Team Bots: who remembers what

On a shared Bot, each person's chat is private.

The Bot can save things it learns for the whole team, and it tells you when it does.

It doesn't save anything about you personally for the team.

Anything it learns about how you work with it stays private to the two of you.

A teammate's shared Bot doesn't get the facts your own Bots share about you.

Per the changelog, a teammate who has linked their account brings their own connectors and their own memory to a Team Bot.

Managers can change a shared Bot's instructions, skills, memory and apps, while Collaborators only chat with it.

So keep the Manager list short.

I covered the full sharing setup in my Grok Bot teams walkthrough.

📞 Rolling Bots out to staff and worried about what they'll remember? Book a free SEO strategy session and we'll map which rules, roles and data belong where. → Book my free strategy session

Privacy controls I'd check on day one

Grok Bot runs on your Cursor account and its data settings, per the approvals, security and privacy page.

It needs data storage, so Legacy Privacy Mode isn't supported.

Training opt-out follows your Cursor account and privacy settings, so set that there.

On teams, the teams docs say that with Privacy Mode enabled, customer data isn't used for training.

Admins also get Delete All Grok Bot Data, which wipes a member's Bots, conversations, memory, routines and computer across every team, for up to 100 members per run, per the computers docs.

It can't be undone, and each run lands in the audit log.

Gotchas, with the fix for each

A rule lives only in memory. Auto-review doesn't review memory writes, per the security docs. Back real boundaries with approvals and Ask first rules.
The Bot trusts an old fact. Memory isn't a source of truth. Ask it to reopen the current source before any big decision.
A blocked message keeps coming back after Reset. The blocked content may sit in the Bot's memory or files, so remove it there.
The import landed on the wrong Bot. It always goes to your primary Bot, so swap the primary first with Replace with different Bot.

Don't mix up Bot memory and computer RAM

The changelog also says the Bot's computer stays up when memory runs low.

That line is about the computer's RAM, not what your Bot remembers about you.

If a search lands you on that note, it has nothing to do with saved facts or rules.

My weekly memory routine

Ask each active Bot "What do you remember about me?"
Correct anything stale in one message.
Ask the right Bot to forget anything private or wrong.
Move any login or card it mentions into Vault.
Hide, don't delete, any Bot you've stopped using.

Ten minutes a week keeps every Bot working from the right facts.

If you want the trainings and templates behind this, join the AI Profit Boardroom.

Also On Our Network

FAQ: Grok Bot Memory

How do I see what my Grok Bot remembers?

Ask it in chat: "What do you remember about me?" Personal Bots have no memory screen, so the chat answer is your audit.

Where is Import Memory in Grok Bot?

Open Settings, then General, and choose Start Import under Import. The imported answer goes to your primary Bot.

Does resetting a conversation clear memory?

No. Reset starts the conversation history over and keeps the Bot's memory, files, routines and settings.

Why does a fact my Bot forgot keep coming back?

Name and time zone style facts are shared across all your Bots. Ask the Bot that first saved the fact to forget it.

Should I save passwords in Bot memory?

No. The docs say logins, cards and contact info belong in Vault, not in memory.

📺 Video notes + links to the tools 👉

🎥 Learn how I make these videos 👉

🆓 Get a FREE AI Course + Community + 1,000 AI Agents 👉

About Julian

I'm Julian Goldie, an SEO entrepreneur, author and founder of the AI Profit Boardroom, which has 3,400+ members.

I help business owners scale with AI agents, automation and SEO.

I've built a 7-figure SEO and link building agency, Goldie Agency, with a team of 70+ SEO experts.
I've grown a YouTube channel to 400,000+ subscribers.
I wrote "Link Building Mastery".
My Udemy courses have taught over 29,000 students.

→ Get my best AI training inside the AI Profit Boardroom

Seed your Bot today, run the audit question on Friday, and book a free strategy session if you want help rolling out Grok Bot memory across your team.