Grok Bot instructions don’t live on a settings page. You give a Bot its role and lasting rules in chat, ask it to remember them, and it keeps them in its memory for every future chat. This lesson shows how to write those instructions so they stick, how to check them, and how to fix them.
What you’ll build
By the end of this lesson you will have:
- A Bot with a one-sentence role.
- Five to eight lasting rules it has saved to memory.
- A memory check that shows the rules it kept.
- One Ask first rule in Auto-review, so your most important limit doesn’t rely on memory alone.
Before you start
- You finished lesson 1.6 and have a Bot with one job.
- You know the 3 to 5 things this Bot must always do, or never do.
- You use made-up names and data for any examples.
Role vs lasting rule vs task
These three are different. Mixing them up is the main reason a Bot “forgets”.
| What it is | Example | |
|---|---|---|
| Role | The Bot’s job, in one sentence | “You own my weekly invoice check.” |
| Lasting rule | Applies every time, until you change it | “From now on, never send external messages without approval.” |
| Task | One piece of work, right now | “Draft follow-ups for these twelve accounts.” |
Put the role and lasting rules in memory once. Put tasks in ordinary messages.
Step by step
Step 1: Write the role in one sentence
- Open the chat with your Bot.
- Fill in the template below and send it.
Paste this into: Grok Bot chat, message box.
Your role: you own [one job] for my [type of business]. You use [sources] and you produce [result]. You stop and ask me before [risky action]. Remember this as your role.
Write the role in working terms. “Own the weekly invoice check and give me a list of overdue invoices” is better than “help with money stuff”.
Step 2: Add lasting rules as a short list
- Write 5 to 8 short rules. Cover tone, sources, limits and approvals.
- Start with “From now on” or “Always” or “Never”, one rule per line.
- End with “Remember these rules.”
Paste this into: Grok Bot chat, message box.
From now on, keep these rules for every task: 1. Leave every email or message as a draft for me. Never send it yourself. 2. Use only the files and sheets I name. If something isn't there, say so. 3. Never promise a price, date or refund that isn't in my price sheet. 4. Write in plain, friendly English. Keep replies under 100 words. 5. My time zone is [your time zone]. Use it for every date and time. 6. If you're unsure, ask me. Don't guess. Remember these rules.
A Bot decides on its own when something is worth saving, and not every save shows in the chat. Asking it to remember makes sure.
Step 3: Check what it saved
There’s no memory screen for a personal Bot. Ask in chat:
Paste this into: Grok Bot chat, message box.
What do you remember about me and about your job? List your role and every lasting rule you're keeping, word for word if you can.
Read the list. If a rule is missing or reworded in a way you don’t like, go to Step 4.
Step 4: Correct or remove a rule
To fix a rule, say what’s wrong and what’s right:
Paste this into: Grok Bot chat, message box.
That rule is out of date. Replace rule 4 with: keep replies under 80 words and use first names. Remember the new version and forget the old one.
To remove a rule:
Paste this into: Grok Bot chat, message box.
Forget the rule about using only my price sheet.
Then ask the Step 3 question again to check.
Step 5: Back important limits with approvals
Memory isn’t a lock. It’s guidance the Bot follows. For anything that matters, like sending, paying or deleting, add an Auto-review rule as well:
- Open Settings → General, and under Bot find the Auto-review switch. Make sure it’s on.
- Under Custom Rules, in When Grok Bot wants to:, type one action in plain words, for example “send any email or message outside this chat”.
- Under It should:, choose Ask first.
- Press Add Rule.
An Ask first rule always stops matching actions for your OK. Lesson 2.6 covers this in full: set approvals.
Rules every business Bot should have
Copy what fits. Keep the list short.
- Drafts only: leave every outgoing message as a draft.
- Sources: use only the files, sheets or folders I name.
- No promises: never state prices, dates, availability or refunds that aren’t in my sheet.
- Time zone: use for every date and time.
- Who to ask: if unsure, ask me in this chat.
- No secrets: never ask me for passwords or codes in chat; use Vault or a secure form.
- Stale data: if a source is missing or out of date, report it instead of using old data.
Want ready-made sets? Download ready-made lasting rules.
Copy-paste prompts
Paste this into: Grok Bot chat, message box.
Your role: you own [one job] for my [type of business]. You use [sources] and you produce [result]. You stop and ask me before [risky action]. Remember this as your role.
Paste this into: Grok Bot chat, message box.
From now on, keep these rules for every task: 1. Leave every email or message as a draft for me. Never send it yourself. 2. Use only the files and sheets I name. If something isn't there, say so. 3. Never promise a price, date or refund that isn't in my price sheet. 4. Write in plain, friendly English. Keep replies under 100 words. 5. My time zone is [your time zone]. Use it for every date and time. 6. If you're unsure, ask me. Don't guess. Remember these rules.
Paste this into: Grok Bot chat, message box.
What do you remember about me and about your job? List your role and every lasting rule you're keeping.
Paste this into: Grok Bot chat, message box.
That rule is out of date. Replace it with: [new rule]. Remember the new version and forget the old one.
Expected result
- The memory check lists your role and every rule you gave.
- A test task follows the rules (for example, the reply is a draft and under the word limit).
- You have one Ask first rule in Auto-review for sending.
We haven’t run this lesson on our test account yet.
Common mistakes
- Rules buried in a long chat. A rule mentioned once in passing may not be saved. Send rules as their own short message and ask the Bot to remember them.
- Rules that contradict each other. “Keep it short” and “explain everything” can’t both win. Read your list after the memory check and remove one.
- Secrets in rules. Don’t put passwords, card numbers or addresses in memory. Logins, cards and contact info belong in Vault.
- Expecting a rule to stop an action. Memory guides the Bot. To make sure a send or payment waits for you, add an Ask first rule.
- Old facts in memory. Prices and stock change. Keep changing facts in a sheet and tell the Bot to check it, rather than storing them as rules.
- Putting the rules in the wrong Bot. Each Bot has its own memory. Rules you give one Bot don’t apply to your other Bots.
Stuck? If a Bot stops replying or acts oddly, see the help hub.
Safety and usage
- Memory isn’t the source of truth. For big decisions, ask the Bot to reopen the current sheet or file.
- Your name and time zone are shared by all your Bots. Job rules aren’t.
- Every Bot reply uses some of your plan’s usage. Clear rules mean fewer corrections later.
Saved in this browser only; no account needed.
Then: 2.1 write clear prompts with the five-part formula
Level progress: Foundations, lesson 1.8.
Related builds: the Lead Responder build uses these rules.
FAQ
Where are a Bot's instructions stored?
In the Bot’s memory. You set and change them in chat. Personal Bots don’t have a description or a Bot settings page.
Do all my Bots share rules?
No. Each Bot has its own memory. A few facts about you, such as your name and time zone, are shared by all your Bots.
Can a rule stop a Bot from sending email?
A rule tells the Bot what to do, but memory alone isn’t a lock. Keep drafts on and add an Ask first rule for sending in Auto-review.
How many rules is too many?
There’s no number in the docs. Keep each rule to one line and the list short enough that you can read it back in a minute.
Can I copy rules to another Bot?
Yes. Paste the same rules into the other Bot’s chat and ask it to remember them, or start from a ready-made template.
What about shared Bots on a team?
A shared Bot has a description that its owner or a Manager edits under About in the Bot’s details. It can also save things it learns for the whole team.
Written with Grok, checked against the docs on Nov 4, 2026. Nothing in this lesson has been run on our test account yet. – Role in operational terms, lasting rule vs task examples, no description or Bot settings page for personal Bots, shared Bot “About”: https://docs.x.ai/grok-bot/bots – What a Bot remembers, Bot decides when to save, “Remember that…”, no memory screen, “What do you remember about me?”, “Forget that…”, name and time zone shared, Vault for logins, memory is not a source of truth: https://docs.x.ai/grok-bot/bots – Auto-review switch, Custom Rules, “When Grok Bot wants to:”, “It should:”, Ask first wins: https://docs.x.ai/grok-bot/approvals-security-and-privacy – Correct lasting preferences explicitly; “Remember: in group chats, reply in the group” pattern: https://docs.x.ai/grok-bot/chat-and-collaboration – Every Bot reply counts toward usage: https://docs.x.ai/grok-bot/chat-and-collaboration – Plan line: https://docs.x.ai/x-subscription/grok-bot and https://cursor.com/help/grok-bot/plans The role-and-rules template and the “rules every business Bot should have” list are Bot Agents 24’s own suggestions, built on the docs above.