How Grok Bot Bots work: roles, memory, sharing, and limits

A Bot is a durable AI teammate with a name, job, conversation, and working context that develops over time. The best Bot is not a universal helper. It owns one clear outcome and has explicit sources, tools, style, and approval boundaries.

Give one Bot one durable job

Create a separate Bot when the work has a genuinely different goal, tool set, working style, recurring schedule, or approval boundary. A useful profile answers:

• What outcome does this Bot own?
• Which sources and tools should it use?
• Which rules remain true across tasks?
• What must always stop for approval?
• Where should it report results?

Use the Bot description for durable rules, such as “Never send an external message without approval.” Put temporary instructions, such as this week’s account list, in the conversation.

Start with the smallest roster

One focused Bot with a clear end-to-end job is easier to review than a crowd of vaguely specialized agents. Add another only when a stable specialist role exists. Official documentation currently allows up to 50 Bots and group chats combined, but the limit is not a target.

Bots can communicate through direct messages, groups, and shared files. Use a group only when the handoff itself needs to be visible. Otherwise, one owner and a clear artifact may be simpler.

Memory is context, not a source of truth

A Bot can retain stable preferences, important facts, and summaries. Correct stale assumptions directly and keep changing facts in the authoritative system. For consequential decisions, ask the Bot to reopen or cite the current source rather than relying on memory.

Bots share one computer

Bots have separate roles, conversations, and screens, but all Bots on an account share the same cloud computer. Files, browser sessions, and command-line credentials are account-wide. Separate Bots are not separate security boundaries.

Do not sign in to a service or place a credential on the shared computer if another Bot on the account should not be able to use it. See approvals and security before enabling local-computer access or consequential actions.

Duplicate, hide, share, or delete

• Duplicate when the same role needs a new scope. The copy carries profile settings, enabled skills, routines, and avatar, but not conversation history, learned memory, or attachments.
• Hide when you may need the Bot later. Hiding does not pause its routines.
• Share only after removing internal URLs, customer data, secrets, and other private configuration. A share link is public to anyone who has it.
• Delete only after checking the effect. Deleting a Bot removes its active profile, conversation, and owned routines; shared-computer files and sign-ins may remain.

A safe Bot profile template

Name: [short role name]
Job: [one durable outcome]
Sources: [authoritative systems]
Working style: [format and evidence rules]
Approval boundary: [send, publish, purchase, delete, permissions, production]
Failure rule: stop and report missing or stale inputs

After the first successful task, save the stable method as a skill. Add a routine only when timing deserves automation. The workflow builder can create a task brief before you make the role permanent.

Sources and verification

Last verified: August 27, 2026.

• Create and manage Bots (xAI)
• Use the computer and apps (xAI)
• Approvals, security, and privacy (xAI)