How this helps you
Rules kept in the description survive when you copy a Bot, so a duplicate starts with the right behaviour.
Read your current description and the things you've learned from our chats. Draft a new description with: your one job, the sources you treat as the truth, what you never do, and what needs my approval first. Write rules as principles, not stories about past mistakes. Show me the draft and don't save it until I say yes.
What they did
@unicodef1wn's X article (notes from 72 hours of the Grok Bot team's livestreams) says the Bot's description works as its system prompt. When you duplicate a Bot, the description is copied but memory starts empty. So anything you rely on belongs in the description. The article's other rules: name the source of truth for each Bot, set how much it can do on its own by the damage a mistake could cause, and remember that frequent routines and group chats are where usage goes.
Who it's for: Anyone who plans to copy, share or rebuild a Bot.
How to try it
- Open the Bot's details by clicking its name at the top of the chat.
- Move the rules you rely on into the description: its job, what it never does, and what needs your approval.
- Write principles, not one-off incidents. A rule should make sense to someone who wasn't there when it happened.
- Ask the Bot to read its description back and point out anything vague or contradictory.
What to expect
A short description you can review line by line before the Bot saves it.
Common mistakes
- Leaving important rules only in memory. A duplicated Bot won't have them.
- Writing rules about one past incident, such as 'don't email Sam again', that confuse the Bot later.
Related tips
- One job per Bot: Give each Bot one job and a list of things it never does.
- Back up your whole Bot setup: Have each Bot document its job, rules, skills and routines into a recovery doc, kept current monthly.
- Start with a chief of staff Bot: Talk to one coordinator Bot and let it hand work to your specialist Bots.
- Turn a Bot into a team Bot your colleagues can use: Share a working Bot with your team as an internal tool, with owners who edit and users who just use it.
- Move an old AI agent folder into Grok Bot: Tom moved 59 local agents into about two dozen Bots by going through them one role at a time: keep, merge, instructions or shared skill.
- Import what another AI assistant knows about you in four steps: Settings, Import Memory gives you a prompt to run in your old assistant. Paste its answer back and choose Add to Memory, so your Bots start with your preferences and context.
Worth knowingHis other rules: name the source of truth, set autonomy by blast radius, and remember that frequency and group chats are where tokens go.Next in your path →Turn a Bot into a team Bot your colleagues can use
Learn more: How to Use Grok Bot: A Beginner's Guide (2026) · All Grok Bot skills tips