Best practices · 10 principles
From official docs and what builders on X repeat. Most of it is about writing down the boundaries.
The persona should be specific enough that the bot knows exactly what to do, and what itmust not do.
"You are a helpful assistant that helps me with everything I need."
Too broad. The bot does not know what it is good at.
"You handle my inbox and do prioritization. Every morning you read the latest 20 emails, categorize them by priority (Urgent/Normal/Can wait), and list them in a markdown document. You NEVER reply to email for me."
Clear scope. The bot knows its job and its limits.
Don'ts are as important as jobs. They protect you from unexpected "helpful" actions, the bot that sends the email it was only supposed to draft.
Role
Follows up leads and keeps the CRM updated.
Choose the trigger method based on the task:
On-demand
Manual trigger. Use for:
Routine
Scheduled. Use for:
A common mistake: ask the bot for confirmation constantly. That kills the point of automation.
"Run prioritization on the mail in my inbox. Ask me before you categorize each email. Also ask whether to include mail from the spam folder."
The bot cannot work independently. You end up answering a pile of questions.
"Run prioritization on the mail in my inbox. Ignore the spam folder. Rules: mail from customers = Urgent, newsletters = Can wait, everything else = Normal."
The bot knows the rules and works without asking.
Don'ts in the description are layer one. Layer two is the product's own rules underSettings → General → Auto-review. Set Require Approval for:
Require Approval wins over Always Allow.
Grok Bot can shop online via @link: you approve each purchase; the Bot gets a one-time card. At time of writing: USA, rolling out to mobile.
Resist the urge to build a superbot that does everything. It gets messy fast.
Tell CoS before you create several. Use group chat when the handoff itself should be visible. Duplicate a Bot when the same role needs a new scope (the copy gets profile, skills, and routines, but not history or memory).
Docs: /workspace on the cloud computer survives computer updates. Builders on X:"Chat is history. That file is memory."
The most documented complaint: the weekly quota runs out faster than people expect. @bot reset quotas for everyone on 5 Sep 2026, and did the same on 26 Aug when access widened. Do not count on that every week.
What burns
What holds
The cloud computer is one per account, not per Bot. Logins, cookies, and files are shared. Each Bot gets its own screen so they can work in parallel, but screens are not a security boundary.
Multiple Bots ≠ isolation
One computer, all logins. Do not put a password on the computer that another Bot should not be able to use.
X credits run out quietly
A Bot watching X may report "nothing new" instead of an error.
Site layout changes
A scraper can report an empty scan for weeks and sound calm. Ask it to report its inputs, not only findings.
Hiding a Bot does not pause routines
Hide only removes it from the sidebar. Pause routines separately.
Delete leaves traces
Delete removes profile, conversation, and routines, but files and logins on the shared computer may remain.
Older blogs lie about platforms
Linux and Android exist now. iPad still does not.
Crypto-desk posts
Threads promising thousands a week lack verifiable receipts. Treat as ads.
Build the team week by week:
Summary
Roore AB · Stockholm · we build it for you
Deterministic where the answer should be the same every time. Prepared material and your yes where it must not proceed automatically. If you have an invoice, order, or email flow done by hand every week, we can build that first.