Grok Bot group chats: run several Bots that hand work to each other

Updated on 2026-10-26

A Grok Bot group chat puts several Bots in one conversation, two to six when you create it, so they can work toward one shared outcome with the handoffs in view. Bots can also message each other outside a group to pass work along. This guide covers when to use more than one Bot, how to start and direct a group chat, how Bot-to-Bot handoffs work, and what changes when you talk to Bots from Slack.

Status: Not tested yet. We have not run a logged test of group chats or handoffs, so everything below comes from the official Grok Bot docs, help pages and changelog. Sources checked on 2026-10-26.

When to use more than one Bot

The official Bots page treats each Bot as a teammate with one job. It says to create a separate Bot when the work has a distinct goal or area of ownership, a distinct set of tools and sources, a distinct working style, a distinct approval boundary, or a distinct recurring schedule. A job such as General Helper gives the Bot less guidance and makes its saved context harder to reuse.

The same page gives an order for building a team of Bots, starting with the smallest useful roster:

1. Give one Bot ownership of an end-to-end outcome.
2. Add another Bot only when the work has a stable specialist role.
3. Put Bots in a group chat when the handoff itself needs to be visible.
4. Keep external actions behind a clear approval boundary.

Its example is a Website Launch group with a launch coordinator, a content editor and an analytics reviewer. The coordinator can assign work, while the group keeps the handoffs in one conversation.

Your existing Bots can also suggest or create a focused Bot when a job should have a long-lived owner. The docs add: ask before creating several Bots if you want to keep the roster small. If you are starting from one Bot, see how to create a Grok Bot first.

How to start a Grok Bot group chat

The docs say to use a group when several Bots need one shared outcome and visible handoffs. On desktop the steps are:

Choose New chat

Choose New chat, the + button in the sidebar.

Select two to six Bots

In New chat, select two to six Bots.

Name the group

Open the group, then edit its generated name if needed.

Describe the shared outcome

Describe the shared outcome and who owns the next step.

On iPhone or Android, use + → New Group Chat. Group membership can be edited later. To rename a group on desktop, right-click it in the sidebar and choose Rename chat. On the phone, tap the group's name at the top of the chat, tap Edit, change the Name and tap Done. To change what the group is for, tell the Bots in the group.

The help page adds that you can put a teammate's published Team Bot in a group chat, but not alongside Bots that run on your own computer.

How to direct a message in a group

The docs list five ways to decide who answers:

• Write normally to let the Bots in the group decide who should respond.
• Type @ and select a Bot when one teammate owns the request.
• Choose Reply on a Bot's message to direct your answer to that Bot.
• Mention several Bots when the request really needs each of them.
• Use @everyone sparingly, for a group-wide update.

The docs give this kickoff as an example of a useful first message:

@Researcher gather the source material and link every claim. @Writer turn the findings into a launch draft. @Reviewer check the draft against the sources and list only blocking issues. Do not publish anything.

It names an owner for each step and ends with a limit. That matches the messaging page's advice to ask for a single owner at each stage.

What a group chat shows, and what it doesn't

Your messages in a group can include attachments. A Bot's replies there can include files, questions and forms, as in a one-to-one chat, and your answer to a question or form goes back to the Bot that asked.

Some things never appear in a group. The docs say approval requests, secret and login requests, and email or Slack drafts do not appear there. Bot-to-group handoff messages are currently text-only, so a Bot should send an image directly to another Bot when that teammate must inspect it.

A few other limits from the help page:

• Group chats don't have the per-Bot Notifications switch.
• Voice chat works with one Bot at a time, so you can't voice chat in a group.
• When you write in a group, the Bots answer there. To keep it that way, tell them, for example "Reply here in the group. Don't message me privately about this.", and ask each Bot to remember it.

How Bots hand work to each other

Bots don't need a group chat to work together. The docs say a Bot can send an asynchronous message to another Bot. The receiving Bot wakes, handles the request and can reply later, and you can see the handoff in the conversation. The help page adds that these messages show up in the Bots' own chats, not in the group.

The docs list four cases where a handoff helps:

• One Bot owns a source system and another owns the deliverable.
• A specialist should review a draft.
• A blocker belongs to another role.
• A long-running job should continue without you coordinating every step.

They also warn that too many parallel handoffs can create duplicate work and noisy updates, so ask for a single owner at each stage.

What several Bots share

The docs say Bots have separate roles and conversations, but they share one cloud computer. That computer belongs to your account, not to a single Bot:

• browser cookies and signed-in sessions are shared;
• files are visible to every Bot;
• command-line credentials are shared;
• a connected app is available to every Bot you run.

Each Bot gets its own screen, so several Bots can use browser and desktop tools at the same time. One Bot can run only one computer-use task on its screen at a time, and the docs say the screens are separate work surfaces, not separate security boundaries. Don't put a credential or file on the computer if another of your Bots should not be able to use it. The template safety checklist covers the same shared-computer risk from the template side.

Bots, group chats and Slack

Whether a Bot can hand work to other Bots from Slack depends on who it is acting for on that turn. The help page puts it in a table:

So to hand work between Bots from a Slack channel, the help page says to share a Team Bot and add it to Slack. A Team Bot has its own Slack app and handle, and anyone in the channel can give it work. The docs list the Slack setup steps: in the Bot's details choose Bring to your team's Slack, choose Connect Slack workspace and approve Cursor, pick the workspace, and then invite the Bot to channels, for example with /invite @BotName. The Bot must be published first, and each teammate links their Slack account once under Settings → General → Team Bots.

One date detail: the 2026-09-29 changelog said a Team Bot in Slack could message one of your own Bots and the reply would come to you privately in Grok Bot. The current help page says those replies are posted back into the same Slack thread. We follow the help page, which is newer.

Slack can also start a routine directly. A Slack trigger is part of a routine, not the Slack app, and the docs treat it as a separate path.

What we don't know yet

• Whether six Bots is a hard limit for a group after you edit its members. The docs only say to select two to six when you create it.
• How Bots in a group decide who answers when you write without an @ mention. The docs say they decide among themselves, but not how.
• How much usage a group of Bots spends compared with one Bot doing the same job. The help page says every reply counts and fewer Bots in a group means fewer replies, but gives no comparison with one Bot.
• How to set up a personal Bot in your own Slack DM. The help pages mention it, but the pages we read do not give the steps.

FAQ

Can Grok Bots talk to each other?

Yes. The docs say a Bot can send an asynchronous message to another Bot, and the receiving Bot wakes, handles the request and can reply later. Bots can also post into a group chat and pass work among themselves there.

How many Bots can be in a Grok Bot group chat?

When you create the group, the docs say to select two to six Bots in New chat. Membership can be edited later. The pages we read do not say whether six is a hard limit after editing.

How do I stop Bots from messaging each other?

The help page says there is no switch for this. Tell the Bots in the chat, for example "Don't message other Bots. Ask me first.", and ask each Bot to remember it. On a team, the changelog says admins can turn off Messaging between Bots under Bot capabilities on the dashboard.

Do messages between Bots use my usage?

Yes. The help page says every Bot reply counts toward your usage, including replies in a group and messages between Bots, so fewer Bots in a group means fewer replies.

Can a Bot hand off work from Slack?

It depends on where you ask. A personal Bot can hand off work from the app or your own Slack DM with it, but not from a Slack channel thread. A Team Bot can hand off work from a channel thread or a DM, to the personal Bots of the teammate who mentioned it.

Do my Bots share files and logins?

Yes. All of your Bots use the same cloud computer, so files, browser sessions, command-line credentials and app logins are shared. Each Bot gets its own screen, but the docs say the screens are separate work surfaces, not separate security boundaries.

Related on bests.one

• How to create a Grok Bot — start here if you have only one Bot so far.
• What is Grok Bot?
• How Grok Bot routines run — routines, including Slack triggers, are separate from group chats.
• Grok Bot template safety checklist — useful before several Bots share one computer and its logins.
• Templates from the Grok Bot Team

Sources: Message and collaborate (Grok Bot docs), Group chats and Bot-to-Bot messages (Grok Bot help), Create and manage Bots (Grok Bot docs), Use the computer and apps (Grok Bot docs), Grok Bot overview (docs), Team Bots (Grok Bot docs), Team Bots (Grok Bot help), Grok Bot changelog. Checked on 2026-10-26.