Why doesn't Grok Bot remember my rules or preferences? Fixes to try before you cancel

Why don't my bots remember the full context of my company?

• What a Bot remembers

  xAI's FAQ says: "A Bot can retain stable preferences, role context, and summaries of prior work." It also says that for important decisions, you should ask the Bot to check the current source rather than relying on memory (xAI's Grok Bot FAQ). xAI's Bots docs put it plainly: memory is not a substitute for an authoritative source (xAI's Bots docs). So treat a Bot's memory as a helpful summary, not a record you can count on for every detail.

• Give each Bot one clear job

  xAI's docs say: "A job such as General Helper gives the Bot less guidance and makes its saved context harder to reuse." They suggest a separate Bot when the work has a distinct goal, set of tools and sources, working style, approval boundary or recurring schedule, and describing the role in operational terms (xAI's Bots docs). If one Bot is doing everything for your business, split out the jobs it does every week, like invoices or bookings, into Bots of their own.

• Ask it to remember lasting rules

  Cursor's help says: "For a lasting rule, ask it to remember." Its example is "From now on, ask before sending any email.", and it adds: "The Bot keeps lasting rules in its memory." The same page says "personal Bots no longer have a description". A Team Bot you own or manage still has one, under About in the Bot's details (Grok Bot help: Edit a Bot). xAI's Bots docs still say to use the description for rules that should remain true (xAI's Bots docs), so the two differ, and we follow Cursor's current help on this point. Because xAI says memory isn't an authoritative source, back the rules that must always hold with an Ask first rule, and turn repeat work into a skill, both covered below.

• Keep changing facts in the source

  xAI's docs list what to do instead of relying on memory: keep changing facts in the source system, ask the Bot to cite or reopen current data for consequential decisions, and correct stale assumptions directly (xAI's Bots docs). For a business, that means prices, opening hours and client details live in your sheet, calendar or docs, and the Bot reads them each time instead of remembering them. When it gets something wrong, correct it in the chat straight away.

• Turn repeat work into a skill

  xAI's docs say: "Start with a one-time task. Make it reliable, save the method as a skill, and only then automate it." A skill captures steps, decision rules, expected output and safety boundaries, and skills are available across your Bots (xAI's Skills and routines docs). Once a job comes out right, ask the Bot to save the process as a skill, so the next run follows the same steps instead of relying on what it remembers. If a skill doesn't show, check Connect apps, Your plugins, Manage plugins and skills, under Private skills (xAI's Skills and routines docs).

• Keep your roster small

  xAI's docs say to start with the smallest useful roster: give one Bot ownership of an end-to-end outcome, and add another Bot only when the work has a stable specialist role (xAI's Bots docs). If you have many Bots handing work to each other, fewer Bots with clearer jobs leave less to keep track of. Our multiple Bots guide covers how many to run and how to split the work.

• Report it so support can look

  If a Bot keeps getting something wrong after these fixes, contact Grok Bot support at hi@cursor.com. Include the email on your Grok Bot account, your Grok Bot version and platform, what you were trying to do, a screenshot, the steps you've tried, and the request ID if the menu offers Copy request ID (Grok Bot help: Get help). Describe one specific example, such as the rule you set and the reply that broke it. If you're rebuilding your Bots from scratch, our free What should my bot do? planner picks three first jobs in 5 quick questions.

Ready-made use cases

1. 01CEO morning brief in 5 minutes
   One message each morning: calendar, urgent emails, money in/out, and the 3 things that move the business today.
   ~3h/week · estimate
2. 02Weekly CEO review & plan
   Every Friday the agent compiles wins, numbers, stuck items and proposes next week's priorities.
   ~2h/week · estimate
3. 03One daily list of drafts to approve
   Your bots hold every email, message and post they write as a draft. Once a day (or once a week) you get one numbered list and answer approve, edit or reject for each. Nothing goes out unapproved.
   ~1h/week · estimate

Grok Bot routine: CEO morning brief in 5 minutes
Schedule: Daily 7:30

Every morning, read my calendar for today, my unread emails from the last 24h and yesterday's revenue. Send me a brief: (1) meetings with one prep note each, (2) emails that need my reply with a suggested one-line answer, (3) money in/out, (4) the 3 highest-leverage tasks for today. Keep it under 200 words.

Rules: draft first, never send or post anything external without my approval. Keep summaries short.

Grok Bot, ChatGPT, Claude and n8n versions: all templates

Email me this template + the Starter Kit

Keep these human

• Don't rely on memory for facts that change, like prices or client details. Keep them in the source and ask the Bot to reopen it (xAI's Bots docs).
• Rules that must always hold, like asking before sending, are lasting rules: ask the Bot to remember them, and on a Team Bot also put them in the description (Grok Bot help: Edit a Bot). Back them with Ask first rules under Settings → General → Auto-review (xAI's Approvals docs).
• For important decisions, ask the Bot to check the current source rather than relying on memory (xAI's Grok Bot FAQ).
• We can't tell you why a particular Bot forgot something. When you report it, give support one specific example (Grok Bot help: Get help).
• Start in draft mode: the agent prepares, you approve, then you loosen the leash routine by routine.

FAQ

Related guides

• Tired of re-explaining your business to every AI tool? Brief it once
• How many Grok Bots does a small business need? One main Bot, specialists and group chats
• Grok Bot skills vs routines: how a job is done, and when it runs
• Grok Bot approvals: set it up so nothing goes out without your OK
• Turn your SOPs and docs into instructions your AI agent follows
• Grok Bot first-day fixes: locked out, usage gone, starting from X and bots that never ship