Grok Bot group chats and handoffs

Several Bots can work in parallel on the shared computer, message each other, and pass ownership so you are not the person in the middle. That is useful only after each Bot has a job of its own. A group of vague helpers is harder to review than one focused Bot.

Start with one owner

Create a second Bot when the work has a different goal, tool set, working style, approval boundary, or schedule. Until then, extra Bots add sessions and shared-computer risk without adding clarity.

A workable split looks like: Bug Reproduction returns a pack, Product Performance writes the investigation, you decide whether anything ships. The handoff is a file and a message, not a standing committee.

See how Bots work for profile, memory, share, and delete rules. Official documentation currently allows up to 50 Bots and group chats combined.

Direct messages, groups, and @mentions

In a conversation you can:

• Mention a Bot, group, routine, or connector with @
• Reference a saved skill with /
• Reply to a specific message
• Send “Stop now” to end the current turn (this does not undo completed actions)

A direct message from you takes priority over background work. Use it to redirect, not to run a second conflicting job in the same thread.

When a group is justified

Use a group when several Bots need one shared outcome and the handoff itself should be visible.

Official documentation currently describes groups of two to six Bots:

1. Choose New in the sidebar (on iPhone, + → New Group Chat).
2. Select the Bots.
3. Name the shared outcome and who owns the next step.
4. Edit membership later if the roster changes.

Put the decision rule in the first group message:

Reproduction owns the pack. Performance writes the one-page investigation. I approve before any ticket is closed or any production setting is touched. If staging is down, stop and say so.

Handoff limits you should plan around

xAI currently documents that your group messages can include attachments, but Bot-to-group handoff messages are text-only. If another Bot must inspect an image or file, send it in a direct message to that Bot, or leave it in /workspace with a path the next Bot can open.

Bots share files on the computer even when they are not in a group. A group is for visible coordination, not for isolating data. See Agent Computer.

Do not use extra Bots as a security boundary

All Bots on the account share browser sessions, files, and command-line credentials. A “personal” Bot and a “work” Bot on the same account can reach the same logins. If a credential must not be available to the rest of the roster, it does not belong on this computer.

A small roster beats a company of agents

Official product pages show many named jobs. That is a menu, not a staffing target. Three Bots with sharp edges outperform eight that all “help with ops.” Hide Bots you are not using; hiding does not pause their routines, so pause those separately.

When you do need parallelism, give each Bot a screen-sized job and a written next owner. You watch the handoff. You do not retype it.

Sources and verification

Last verified: August 27, 2026.

• Message and collaborate (xAI)
• Create and manage Bots (xAI)
• Use the computer and apps (xAI)
• Grok Bot overview (xAI)