Grok Bot Memory: What a Bot Remembers and How to Change It

A Bot saves the lasting things that let it keep a role over time without replaying every earlier message. Cursor Help lists four kinds.

• 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 log of what it has worked on with you.

What it does not hold is just as useful to know. Logins, cards and contact details such as addresses and phone numbers go in Vault, not in memory, and the Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. Vault guide covers that side. The docs also draw a firm line about authority: memory is not a substitute for the source system. Keep changing facts where they live, ask the Bot to cite or reopen current data before a consequential decision, and back safety boundaries with approvals and Auto-review rules instead of memory alone.

That last point is easy to read past. A rule like "never send external messages without approval" sits comfortably in memory, but the docs treat it as guidance, and the thing that actually stops the send is an approval rule. If a boundary matters, it probably belongs in both places, and the approvals guide is where the enforced half lives.

The Bot decides on its own when something is worth keeping, and it does not ask first. It often mentions a save in its reply, though not every save shows up in the chat, so you cannot rely on the transcript as a complete record of what it kept.

To be sure, ask. "Remember that I'm out every Friday" is the pattern Cursor uses, and the same move applies to rules: when you discover a lasting preference, boundary or responsibility, tell the Bot and ask it to remember. One-off task instructions belong in ordinary messages. The split keeps memory small and predictable, which matters more as the Bot's log grows.

The best moment to do this is the first message to a new Bot. Cursor's setup guidance is to give the Bot its job, sources and approval boundaries there and ask it to remember them.

Mostly yes, with one boundary per Bot. The table below sets out where memory travels, because the answer differs depending on whether the context is your own chats, your other Bots or a shared space.

The group chat row is the one to think about before you add a Bot to a shared conversation. Your Bot will not hand its memory to the other Bots, yet it can repeat something from your private chat in its reply, and that reply is visible to the whole group. If something should stay out, tell your Bot so. The group chats and voice guide covers how those conversations work.

Separate memory does not mean separate everything. Conversations and learned context stay per Bot, but shared files, browser sessions and direct handoffs still move context between your Bots, since they all work on one cloud computer.

Copies are the other edge case. On iPhone you can Duplicate a Bot to reuse a role at a different scope, and the copy carries its profile, settings, enabled skills, routines and avatar, but no conversation history, learned memory or attachments. A duplicate starts out knowing its job description and nothing it learned doing the job, so treat its first few tasks the way you treated the original's, and restate any lasting rules you want it to keep.

Personal Bots have no screen that lists their memory. You manage it by asking in chat, which feels informal for something this important, but it is the only route the help page gives.

Correcting stale assumptions directly is also what the docs recommend in general. A Bot working from an old fact will keep applying it until someone tells it otherwise, and because saves are not always announced, a periodic "what do you remember about me?" is the only way to catch one you never saw it make.

Very little resets memory by accident. Only deleting the Bot or your account removes it, and the conversation-level reset you might hit after a blocked message leaves it untouched.

The conversation reset appears when a message is blocked and the notice offers Reset, followed by Reset this conversation? Deleting a Bot is a right-click and Delete in the sidebar, and the managing Bots guide covers what else goes with it. The shared-facts detail is the one that can catch you out, since deleting one Bot can quietly remove your name or time zone from the others if that Bot was the one that saved them.

A personal Bot's memory is yours, and only you can change it. Team Bots are where this gets more involved.

A Team Bot can save what it learns for the whole team, and it tells you when it does. It does not save anything about you personally for the team; what it remembers about working with you stays between you and the Bot. A teammate's Team Bot also does not receive the facts your own Bots share about you. When you turn one of your Bots into a Team Bot, you choose which memories the team copy gets, using Share with team or Keep private, and Team Bots walks through that conversion.