agentos.guide › blog

Grok Bot Memory: Write The Import, Check The Audit And Tidy Every Bot's Memory From Your Agent OS

By Julian Goldie · 2 November 2026 · agentos.guide

Grok Bot memory stays tidy when your Agent OS writes the import, drafts the lasting rules and checks the audit, so the Bot only stores what it should.

Grok Bot holds the memory.

Your Agent OS keeps the master copy of your rules in your own files and runs the checks every month.

Below is a quick start, five copy-paste prompts and a monthly loop, all built on the official What a Bot remembers docs.

Want help wiring this into your business? Book a free SEO strategy session with my team.

Quick start: the 10-minute version

1. Check you're on a plan with Grok Bot: Premium, Super and Ultra include it; Plus doesn't.
2. Confirm which Bot is your primary Bot, because imports land there.
3. Run Prompt 1 in your Agent OS to write the import answer.
4. In Grok Bot, open Settings, General, choose Start Import, paste the answer and choose Add to Memory.
5. Run Prompt 2 and send the rules message to the Bot.

That gets a Bot working from your real preferences on day one.

The five prompts below then keep the Bot's memory in line with the rules file your Agent OS already owns.

Run them in order the first time, then use Prompt 5 as your monthly habit.

What lives in Grok Bot and what stays in your Agent OS

The docs say memory isn't a substitute for an authoritative source, so changing facts never live only in the Bot.

Prompt 1: write the import answer from your own files

Grok Bot's import gives you a prompt meant for your old assistant, per the Settings docs.

Your Agent OS can answer it from your notes instead.

Here is the prompt Grok Bot's Import Memory gave me:
[paste the import prompt]
Answer it using only my profile, SOPs and preference files.
Include: how I like to work, my standing rules, my time zone.
Leave out every password, card number, address and phone number.
Flag anything you're unsure about instead of guessing.

Read the answer, then paste it into the second box and choose Add to Memory.

Grok Bot sends it to your primary Bot and opens that chat.

Prompt 2: turn your house rules into one lasting-rules message

The docs separate lasting rules from one-off tasks, and say to ask the Bot to remember the lasting ones.

From my rules file, write one message for my Grok Bot.
List only lasting rules, one per line, in plain words.
Start with: "Remember these as lasting rules."
Drop anything that is a one-off task.
Mark any rule about sending, buying or deleting with [APPROVAL].

Every [APPROVAL] line also becomes an Ask first rule in Grok Bot, because Auto-review doesn't review memory writes, per the security docs.

🔥 Get the full Agent OS that runs these prompts

AI Profit Boardroom members get step-by-step video trainings, the installable Agent OS, four coaching calls a week and 3,400+ members swapping memory setups.

→ Join the AI Profit Boardroom

Prompt 3: check the Bot's own account of its memory

There's no memory screen for a personal Bot.

Ask the Bot "What do you remember about me?", copy the reply, then hand it to your Agent OS.

Below is what my Grok Bot says it remembers about me.
Compare it with my rules file and profile.
Return three lists:
1. Stale or wrong: with the correction to send.
2. Private: items that belong in Vault or nowhere.
3. Missing: rules from my file the Bot doesn't mention.
Then write the exact correction and "Forget that..." messages.
[paste the Bot's reply]

Send the corrections as plain chat messages.

If a fact shared across all your Bots is wrong, telling any Bot fixes it, but only the Bot that saved it can remove it completely.

Prompt 4: the pre-delete checklist

Deleting a Bot erases its profile, conversations, memory, routines and attachments, including shared facts it saved for your other Bots, and it can't be undone.

I'm about to delete my Grok Bot called [name].
Write a checklist I run first:
- Export any rule I want to keep into my rules file.
- List shared facts it may have saved for my other Bots.
- List routines to pause and websites to sign out of.
- Remind me that files on the shared computer stay behind.
End with: hide it instead if I may need it later.

The FAQ confirms files and logins on the shared computer can remain after a delete.

Hide from sidebar keeps the Bot's memory and work.

Prompt 5: the monthly memory review

Run my monthly Grok Bot memory review.
For each Bot in my roster file: remind me to ask it what it remembers,
take the reply I paste, and run the Prompt 3 checks on it.
Log the date, the fixes sent and anything moved to Vault
in memory-review.md.

That log lives in your Agent OS, so you keep a dated record outside the Bot.

Over a few months it shows which Bots drift most, and which rules need rewriting in plainer words.

If one Bot keeps getting the same rule wrong, rewrite that rule shorter and send it again.

Where memory travels, and where it doesn't

• Across chats: since v0.75.2, a personal Bot remembers in every chat what it saved in one.
• Across Bots: only a few facts, such as your name and time zone, are shared.
• Into calls: voice chats can use earlier calls and your recent chat.
• Into group chats: your Bot can use private context, and everyone reads its replies, so tell it what to keep out.
• Into copies: a Bot duplicated on iPhone gets no learned memory.

Give this list to your agent as context, so its audit knows where to look for leaks.

Shared Bots: how memory works for your teammates

On a shared Bot, every chat is private, and the Bot never saves anything personal about a teammate for the team.

It can save team-wide learnings, and it tells people when it does.

The changelog notes that every linked teammate keeps separate memory and connectors there.

Give the Manager role sparingly, since Managers can edit what a shared Bot remembers.

The rollout prompts are in my Grok Bot teams guide.

📞 Want us to plan your Bots' memory with you?

Book a free SEO strategy session and my team will map your rules, roles and data for each Bot.

→ Book my free strategy session

What your Agent OS should never send to Bot memory

Keep a short deny list in your Agent OS and make every prompt above respect it.

• Passwords, API keys and one-time codes.
• Card numbers and bank details.
• Customer addresses and phone numbers.
• Live prices, stock levels and deadlines that change weekly.

The first three belong in Vault or nowhere; the last belongs in its source system.

Add this line to the top of your rules file: "Never include deny-list items in anything meant for Grok Bot memory."

Before you merge two Cursor accounts

If you combine Cursor accounts, Grok Bot chats, tasks, memory, routines and rooms move to the primary account, per the multiple accounts page.

Bots keep the same IDs and sit next to the primary account's Bots.

Have your agent list every Bot on both accounts first, so you know which memories you're bringing together.

List every Grok Bot I run on both Cursor accounts from my roster file.
For each, note its job and whether it should keep its memory after the merge.
Flag any two Bots doing the same job, so I can hide one afterwards.

Snags, and what to tell your agent

• The import went to the wrong Bot. Make the right Bot primary with Replace with different Bot, then import again.
• A fact won't go away. Ask your agent which Bot learned it first, then ask that Bot to forget it.
• Reset didn't help with a blocked message. Reset keeps memory, so the blocked text may be in memory or files.
• A "memory runs low" note in the changelog. That's the computer's RAM, not your Bot's memory.

The monthly workflow, end to end

1. Update the rules file in your Agent OS.
2. Run Prompt 2 and send any new lasting rules.
3. Ask each Bot what it remembers and run Prompt 3.
4. Move anything sensitive to Vault and send the forget messages.
5. Log it all with Prompt 5.

Since v0.78.1, two saves to the same memory at once no longer overwrite each other, so batch corrections are safe to send.

Join the AI Profit Boardroom for the full Agent OS and the trainings behind these prompts.

FAQ

Can my Agent OS write the Grok Bot Import Memory answer?

Yes. Paste the import prompt into your Agent OS, have it answer from your own files, then paste that answer into the second box and choose Add to Memory.

Where do imported memories go?

Grok Bot sends the import to your primary Bot and opens that chat.

How often should I audit Grok Bot memory?

Monthly is a good rhythm. Ask each Bot what it remembers and check the reply against your rules file.

Is a rule in memory enough to stop a Bot sending email?

No. Auto-review doesn't review memory writes, so add an approval or Ask first rule for anything that sends, buys or deletes.

Final word on Grok Bot Memory

Paste Prompt 1 into your Agent OS now, then book a free strategy session if you want help setting up Grok Bot memory across your business.

Related guides on agentos.guide

→ Grok Bot Teams: Plan, Audit And Roll Out A Shared Bot With 5 Prompts In Your Agent OS

→ Grok Bot Routines: How To Plan, Test And Review Every Routine In Your Agent OS, With Five Copy-Paste Prompts

→ Grok Bot Connectors: Manage Apps In Your Agent OS

→ Grok Bot Android: Approve And Steer It In Your Agent OS

📺 Video notes + links to the tools 👉

🎥 Learn how I make these videos 👉

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

← all guides on agentos.guide