How to Stop a Grok Bot From Forgetting Your Instructions
- Tell the Bot each lasting rule and ask it to remember. Save methods you repeat as skills. Keep facts that change in a document or app the Bot can reopen.
- Check what it remembers by asking, and correct or remove anything that's out of date.
- Memory isn't a source of truth. Back anything important, like sending or deleting, with an approval setting too.
If your Grok Bot forgets instructions, the fix often comes down to where the instruction lives, not how loudly you say it. There are four places an instruction can go: the Bot's memory, a skill, a source it can reopen, or the message itself. This page shows which instruction belongs where, and how to check it stuck.
How do you stop a Grok Bot from forgetting your instructions?
Tell it each lasting rule and ask it to remember, save methods you repeat as skills, and keep facts that change in a source the Bot can reopen. Then check what it remembers by asking, and back important limits with approval settings rather than memory alone.
Where does this instruction go?
| Kind of instruction | Where it goes | Words to say |
|---|---|---|
| A lasting rule ("ask before you email anyone") | The Bot's memory | "Remember this rule: ask me before you send any email." |
| A method you repeat (how to build the Monday report) | A skill | "Save how you just did this as a skill called Monday report." |
| Facts that change (prices, client lists, policies) | The source system, such as a doc or an app | "Reopen the price sheet and use today's numbers." |
| A one-off task | The message itself | "Just for today, skip the weekend summary." |
| A login, card or contact detail | Vault, not memory | Add it to Vault rather than telling the Bot in chat, according to the official Vault and secure sign-in docs. |
The wordings in the right-hand column are examples you can adapt. The official docs don't give a fixed phrase for each, beyond asking the Bot to remember.
What does a Bot remember?
A Bot keeps stable preferences, important facts and summaries of its work: how you like to work, rules you ask it to keep, facts about you such as your name and time zone, and a dated log of what it worked on with you. It decides on its own what's worth keeping.
According to the official Bots page, each Bot has its own memory. A few facts about you, such as your name and time zone, are shared by all your Bots. Everything else stays with the Bot that learned it.
Memory isn't the only thing a Bot carries. Skills are separate: a skill is a reusable set of instructions for how to do a task, and your skills live in one library across your Bots.
How do you make it remember something?
Ask it to remember: a Bot decides on its own what's worth keeping and doesn't ask you first, so if a rule matters, tell it the rule directly and ask it to remember. That's the surest way to make sure it lands in memory.
Some examples, in your own words:
- "Remember that I'm on Eastern Time and don't want messages before 8 a.m."
- "Remember: always ask before you send an email to a client."
- "Remember that reports go to me first, never straight to the client."
The official advice for long conversations helps here too. Lead with the result you want, link the source of truth, say what the Bot may change, and correct lasting preferences out loud rather than hoping it notices.
How do you check, fix or remove a memory?
Ask the Bot in a chat: to see what it has kept, ask "What do you remember about me?"; to fix something, tell it what's out of date; and to remove something, tell it to forget that specific thing. There's no memory screen for a personal Bot, so the chat is where you check.
Check what it remembers (four lines)
- Ask: what do you remember about me?
- Read the list and spot anything wrong or missing.
- Correct it: tell the Bot what's out of date and the right version.
- Remove what shouldn't be there: tell it to forget that item.
If a fact shared across your Bots is wrong, such as your name or time zone, tell any one of your Bots the correct version.
When should an instruction be a skill instead?
When it's a method rather than a rule: the steps for a task you'll repeat, like how to build a weekly report. A skill is a reusable set of instructions for how to do a task, and skills sit in one library across your Bots, so any Bot can follow the same method.
A simple test: if the instruction starts with "always" or "never," it's probably a rule for memory. If it starts with "here's how to," it's probably a skill.
The official order for a repeating job is to do it once as a one-time task, make it reliable, save the method as a skill, and only then put it on a routine, which tells one Bot when to run it. For the full walkthrough, see Grok Bot Skills vs Routines: How to Automate a Recurring Task.
What about a central knowledge base?
Keep facts that change, like prices, policies or client details, in the source system, such as a document or an app, and ask the Bot to reopen it. The official docs say memory is not a source of truth, so for numbers that change, ask the Bot to look them up again.
What the official docs advise:
- Keep changing facts in the source system, not in the Bot's memory.
- Ask the Bot to cite or reopen current data before any decision that matters.
- Correct stale assumptions directly when you see them.
- Back safety limits with approvals and Auto Review rules, not memory alone.
I keep a shared knowledge base for my bots in Obsidian: standing facts, how the team is organized, and lasting decisions. I do not need the vault's internal name on this page. It has been in place since at least October 2026.
I run my business with a team of Grok Bots: one front-door "chief of staff" bot that hands work to specialist bots, following handoff and usage rules I wrote. When several Bots need the same facts, a single source they can each reopen can help keep them from drifting apart. For how that front-door setup works, see How to Set Up an AI Chief of Staff With Grok Bots.
How do you reset a conversation without deleting the Bot?
Use Reset: when a message is blocked, the notice can offer Reset, which starts the conversation history over while keeping the Bot's memory, files, routines and settings. Don't delete the Bot to get a fresh start, because deleting it erases its memory and can't be undone.
What resets or deletes memory, per the official Bots page:
| What you do | What happens to memory |
|---|---|
| Reset a conversation | Memory is kept |
| Delete a Bot | That Bot's memory is deleted |
| Delete your account | Every Bot's memory is deleted |
Deleting a Bot also erases its profile, conversations, routines and attachments, and it can't be undone. If you just want a Bot out of the way, hide it from the sidebar instead, which keeps its work and memory.
When a conversation turns into a different long-lived job, the official advice is to start a thread or a new Bot for it. For how to split work across Bots, see How to Build a Team of AI Agents in Grok Bot.
FAQ: Grok Bot forgets instructions
Do my Bots share memory?
Mostly no. Each Bot has its own memory, but a few facts about you, such as your name and time zone, are shared by all your Bots.
Does a new conversation lose my rules?
Resetting a conversation keeps the Bot's memory, files, routines and settings, so rules it has remembered stay. To be sure a rule was kept, ask the Bot what it remembers about you.
Where do passwords go?
In Vault, not in memory. The official Vault and secure sign-in docs say to save logins, cards and contact info in Vault so your Bots can sign in and check out without seeing your passwords.
Can I bring memory from another assistant?
Yes. Import Memory, under Settings > General > Import, brings preferences and context from another assistant into your primary Bot.
What if the Bot remembered something wrong?
Tell it what's out of date and what's true now, or tell it to forget that item. If it's a shared fact like your time zone, telling any Bot the correct version is enough.
If you want a set of ready-to-install bots, in order, that look for money before they ask you to spend more of it, see The Payback Roadmap. If a rule keeps slipping because of approvals or routines, Grok Bot Not Working? Fixes for Routines and Permission Prompts covers those, and Is Grok Bot Safe? Approvals, Vault and Access to Your Computer explains approvals and Vault.
This bot is one piece of a full AI team. See how I run my business with a team of Grok bots. The AI Chief of Staff: How I Run My Business With a Team of Grok Bots