Multi-Bot collaboration: group chats, handoffs, and Team Bots
The Bot template from the previous lesson gives each colleague a copy; this lesson covers two other things: getting multiple Bots to collaborate in the same chat—Grok Bot group chats plus handoffs between Bots, and getting the whole team to chat with the same Bot—the Team Bot. The whole thing takes about 12 minutes.
Get familiar with the three approaches first—each step later uses them:
| Collaboration approach | In one sentence | Best for |
|---|---|---|
| Group chat | You and 2–6 Bots in the same chat | One shared result, with the handoff process visible to everyone |
| Handoff | Bot A sends an asynchronous message to Bot B | Long tasks flow between Bots without you watching every step |
| Team Bot (a Bot shared by the team) | The whole team chats with the same Bot | Unified configuration, each person's chats stay private |
What you'll be able to do after this lesson
- Use
Cmd/Ctrl+Shift+Nto start a Grok Bot group chat, add 2–6 Bots in To:, rename the group, and adjust members anytime - Use
@-mentions, Reply targeting, and@everyoneannouncements to set a single owner for each stage - Have Bots hand off work to each other (handoff), and explain why personal Bots can't hand off within Slack channel threads
- Share a Bot with the whole team or specific people, and distinguish Collaborator (chat) from Manager (edit configuration)
- Get colleagues using the Team Bot via Browse Team Bots, the share link, or Slack, and know whose usage it counts against
Your current pain points
- "Three Bots—research, drafting, and review—each work on their own, and I'm a human relay between three windows, with no idea who lost whose output"
- "I want the whole team to use the same knowledge-base Bot, but all I know is sending templates—everyone gets a copy, and the configurations drift apart as they chat"
- "A colleague @-mentions my Bot in a Slack channel, and it either does nothing or sends the result back to the app where nobody in the channel can see it"
When to use this technique
When you need:
- Several Bots to jointly produce one shared result, with the handoff process visible to everyone
- Long tasks to flow asynchronously between Bots, with you only watching key checkpoints
- The whole team to chat with the same Bot: unified configuration, private chats per person
And you don't want:
- To copy-paste between multiple one-on-one chats as a relay
- To send everyone a Bot copy with configurations drifting apart (that's the templates scenario)
- To hand over sensitive apps, secrets, and files along with the Bot
🎒 Prerequisites
- Completed Your first Bot: create it, assign work, and watch it work on a cloud computer, with at least one working Bot on hand
- Want to follow along with Team Bot: you are in a Cursor team and every member has a Grok Bot——you can see Browse Team Bots under + in the sidebar (if you can't see it, you're not in a team, or the app needs updating)
- To follow along with the Slack part: you have permissions for your team's Slack workspace and colleagues are willing to link their own accounts
- Read Approvals and Auto Review: there are no approval cards in group chats, and this comes up repeatedly in this lesson
Core ideas
The three approaches are distinguished by "who shares context with whom"—the table above is a quick reference. What really determines success or failure are three boundaries:
- No approvals in group chats. Approval requests, key/login requests, email and Slack drafts never appear in the group; for actions that need approval, go back to a one-on-one chat.
- Sharing doesn't copy. A Team Bot is the same Bot: each person's chat is private (even the owner and Managers can't see yours), but the apps, secrets, skills, and files configured by the owner take effect in every teammate's chat. If you want a separate copy for each person, use templates.
- Local Bots can't be shared or mixed into groups. A Bot running on your own computer can't be shared; you can add a Bot a colleague shared with you to a group chat, but it can't be in the same group as a Bot running on your own computer.
Follow along
Step 1: Start a Grok Bot group chat (add 2–6 Bots in To:)
Why: When several Bots need one shared outcome, a group chat lets everyone see the same context and handoff process, so you don't have to relay messages.
On desktop, pick one of three options: New chat, the shortcut Cmd/Ctrl+Shift+N, or Cmd/Ctrl+K to open the command palette and choose New group chat. On the mobile app 1.19.0 and later, + only offers New Bot and no longer provides New Group Chat, so start group chats on desktop; existing group chats on mobile can still be opened, posted in, and renamed.
Add 2–6 Bots in To:, open the group, and rename the auto-generated group name to something readable—on desktop, right-click the group in the sidebar and choose Rename chat, or click the group name at the top and edit the name in the details; on mobile, tap the group name → Edit → change Name → Done. Group members can also rename it later.
In the first message, state clearly what the shared outcome is and who is responsible for each step. The group's purpose is defined by the conversation; if you want to change it, just say so.
You should see: a group chat with you and these Bots, with the Bots starting to claim tasks based on the opening message.
- The group chat is created, To: contains 2–6 Bots, and the group name is readable
Step 2: Assign work by @ mention, one owner per stage
Why: Without a named assignee, Bots will negotiate among themselves who answers; naming one avoids squabbling over tasks and duplicated work.
Ways to assign work: write a normal message and let the Bots decide who responds; type @ to direct a task to a specific Bot; click Reply on a message to respond to a particular Bot; type @everyone for an all-hands announcement—use with care.
Assign a single owner for each stage right at the start (replace @Researcher and the like with your own Bot names):
@Researcher gathers the raw material, with a source link attached to every conclusion.
@Writer organizes the material into a publishable draft.
@Reviewer checks the draft against the sources and lists only issues that must be fixed.
Do not publish anything yet.Your messages can include attachments; Bot replies can also carry files, questions, and forms, and the answers you fill in go back to the Bot that asked.
You should see: each named Bot claims its task and reports in the group, with handoffs visible to everyone.
- Each stage has a single owner, and no two Bots are doing the same thing
Step 3: Keep replies in the group (don't DM me)
Why: A Bot may go answer you in its own one-on-one chat, or DM another Bot for a handoff—those messages only appear in their respective chats, invisible to people in the group.
Say it directly in the group:
Please reply in the group; don't DM me about this.To make it a rule, have each Bot remember:
Remember: in a group chat, reply in the group chat.You should see: the Bot's replies appear in the group; its DMs to other Bots appear in those Bots' own chats.
Three management rules:
- There's no toggle for Bot-to-Bot messages; manage them with instructions: tell them "Don't DM other Bots; ask me first." If a Bot keeps starting new work on its own, open its one-on-one chat and tell it to stop.
- To keep a helper Bot quiet without deleting it: turn off its notifications or hide it. Group chats have no per-Bot Notifications toggle.
- Every Bot reply counts toward your usage—including replies in the group and messages between Bots. Fewer Bots in the group, fewer replies.
Step 4: Hand off work between Bots (handoff)
Why: A handoff is an asynchronous message from one Bot to another—the receiving Bot is woken up, does the work, and replies later. It suits cases like "one Bot owns the data source, another owns the deliverable," "an expert Bot reviews a draft," or "a long task you don't want to babysit step by step."
In a one-on-one chat, just tell the Bot something like "hand the draft to @Reviewer for review."
You should see: the handoff appears in the conversation, and the receiving Bot wakes up to take the work.
Two disciplines:
- One owner per stage. Parallel handoffs create duplicated work and notification spam.
- A handoff requires the Bot to "act on behalf of someone" in that turn; whether it can hand off and where the reply lands depend on where you assign the work:
| Bot type | Where you assign the work | Can message other Bots | Acts on behalf of | Where the reply lands |
|---|---|---|---|---|
| Personal Bot | the app, or its Slack DM with you | ✅ Yes | you | the app chat (not in Slack) |
| Personal Bot | a Slack channel thread | ❌ No | no one (threads are shared) | the Bot will say it can't |
| Team Bot | Slack channel thread or DM | ✅ Yes, hand it off to the Bot of the person who mentioned it | the colleague who @-mentioned it | the same Slack thread |
Want Bots to hand off to each other inside a Slack channel? Move to the next step: share the Bot and connect it to Slack.
- The handoff worked: the receiving Bot woke up to take the work, and the reply landed where the table predicted
Step 5: Share the Bot with your team (Share and roles)
Why: A Team Bot is "the same Bot, with each person's chat private" — configuration stays unified and the knowledge the team learns is kept in one place, unlike templates where each person grows their own.
Before sharing, check its apps, secrets, skills, and files: they will take effect in every teammate's chat; keep only what you're willing to let everyone you share with use.
- In the top-right corner of the Bot chat, select Share.
- Under Who has access, choose the scope: your team, Everyone in your organization, or People you invite (only the specific people and groups you designate).
- Use Add people or groups to add people; to let someone edit it, open that person's role and select Manager:
- Collaborator: can chat with the Bot and teach it things
- Manager: can also change the Bot's settings, review what it learns, and share it
- Stop sharing: in Share choose Only you (only the owner can stop sharing).
A newly created Bot must be Published before teammates can find it; for the full workflow of creating, publishing, learning, and connecting to Slack / Teams, see Team Bot: One Bot for the Whole Team.
The owner and Managers can always use this Bot.
You should see: teammates can find this Bot under + → Browse Team Bots, labeled with its creator.
- Roles are assigned: give Collaborator to those who chat, Manager to those who change configuration
Step 6: Get teammates using the Team Bot (Browse, linking, and Slack)
Why: sharing only sends permissions; colleagues still have to add the Bot, and to use it in Slack they must first link their account.
| Method | What the colleague does |
|---|---|
| Browse Team Bots | Sidebar + → Browse Team Bots → choose Add (mobile: + → Browse Team Bots) |
| Share link | Open the link you sent and select Start a chat—the link opens the same Bot |
| Slack | owner/Manager: open the Bot's details → Bring to your team's Slack → Connect; if Awaiting admin approval is shown, wait for the Slack workspace admin to approve |
Two key points about Slack:
- Each teammate first links their own account: Settings → General → Team Bots → Link. If they send a message without linking, the Bot will reply with the linking steps.
- Once Connected is shown, teammates can DM this Bot or @ it in a channel—the Team Bot has its own Slack app and handle.
You should see: colleagues are chatting with this Bot in the sidebar or in Slack; it does work using the apps the owner configured, and asks first before using a colleague's own account.
- At least one teammate is using the Team Bot via Browse Team Bots or Slack
Checkpoint ✅
- Can start a group chat with
Cmd/Ctrl+Shift+Nand add 2–6 Bots in To: - Each stage in the group has only one owner; actions requiring approval are not scheduled in the group
- Can explain why a personal Bot cannot hand off work in a Slack channel thread (the thread is shared and represents no one)
- Cleaned apps, secrets, skills, and files before sharing; Collaborator/Manager roles assigned
- Know the usage rules: a Team Bot's replies are charged to the person who was answered, subject to each person's own quota
Pitfall reminders
❌ Waiting for approval cards in a group chat—they never come
Approval requests, key/login requests, email and Slack drafts never appear in group chats; handoff messages the Bot posts to the group are plain text too.
Correct approach: do actions that need approval in a one-on-one chat; if another Bot needs to see an image, send it Bot to Bot directly instead of counting on the image traveling with the group message.
❌ Using @everyone as a souped-up @
@everyone is for "announcements the whole group needs to know." Every Bot reply counts toward your usage—including replies in groups and Bot-to-Bot messages; the more people, the faster it burns.
Correct approach: only @ the Bot actually responsible; when multiple Bots are truly needed, name them one by one; use @everyone only for all-hands announcements.
❌ Don't put a Team Bot and local Bots in the same group
You can add a Bot shared by a colleague to a group chat, but it can't be in the same group as a Bot running on your own computer.
The right approach: a group should either contain only your own Bots, or include a Team Bot but not mix in local Bots.
❌ Treating sharing as copying, or assuming "once it's shared, it's safe"
Sharing doesn't copy: deleting a Team Bot is an owner-only action, and the entire team's access, individual chats, and routines disappear with it—irreversibly. The owner and Managers can't see your chats, but the apps/secrets configured by the owner take effect in every teammate's chats.
The right approach: before sharing, clean out your apps, secrets, skills, and files; "sharing a Bot" is not the same as a "security boundary"—tighten anything that needs tightening in the Approvals & Auto Review settings.
Advanced tips (optional)
- Team Bots in Slack: in channel threads it works on behalf of the teammate who @ mentioned it, can hand work off to that teammate's own Bot, and replies land back in the same thread; approvals use the Review an action card (Allow once / Deny / View details), and only the person who asked can answer; the Bot records who dispatched each message, and anyone can ask it; after a routine replies in a thread it keeps following the thread, so no further @ mentions are needed.
- Admin bulk distribution: in the Cursor dashboard's Grok Bot page → Manage Bots under Shared Bots: Access changes who can use it, and Auto-add (All team or specified groups) automatically adds it to members' sidebars—members who are auto-added cannot hide it themselves.
- Mobile and voice: on mobile, + → Browse Team Bots to add a Team Bot; chatting and answering Allow cards both work; a Team Bot cannot be set as the primary Bot; on desktop you can Start voice chat in your chat with it.
- Privacy and usage boundaries: Your DM with the Team Bot usually runs on your Grok Bot computer (which can access your files and logins); if your privacy mode is stricter than the owner's, this conversation runs on a different computer instead. To make all Team Bots ask again whether to use your personal account: Settings → General → Team Bots → Clear connector preferences.
Lesson recap
- ✅ Can create Grok Bot group chats:
Cmd/Ctrl+Shift+Nto create a new one, To: add 2–6 Bots; the group name and members can be changed at any time - ✅ Can assign work: let Bots discuss among themselves without naming anyone,
@/Replyfor targeted assignment,@everyonefor all-hands announcements only; one owner per stage - ✅ Can manage the group: tell a Bot to "reply in the group" and make it remember; there is no toggle for Bots messaging each other—control it with commands
- ✅ Handoffs supported: personal Bots can exchange messages in the app or in their own Slack DMs; handoffs within Slack channel threads rely on the Team Bot
- ✅ Can share: Share → Who has access → Collaborator/Manager; sharing does not copy the Bot, each person's chat stays private, and usage is billed to the person whose question is answered
Quick reference for key locations:
| Location | How to use |
|---|---|
Cmd/Ctrl+Shift+N (or Cmd/Ctrl+K → New group chat) | Create a new group chat |
| Right-click the group in the sidebar → Rename chat / click the group name at the top | Rename the group |
| Top right of the chat → Share | Sharing: who can use it, who is the Manager |
| Sidebar + → Browse Team Bots | Discover and add Team Bots |
| Settings → General → Team Bots → Link | Link a Slack account (each teammate links their own) |
| Settings → General → Team Bots → Clear connector preferences | Clear connector preferences so Team Bots ask again |
| Cursor dashboard → Grok Bot page → Shared Bots → Manage Bots | Admins: Access and Auto-add |
Next lesson preview
Bots can now work as a team inside the app; in the next lesson we take them to X: @bot and X Chat: assign work on X anytime.
You will learn:
- Prerequisites for assigning work to bots via @bot on X
- What a @bot reply means, and common reasons for no reply
- How to determine regional restrictions: based on the X account's country of registration; unavailable in some regions
- Available accounts for X Chat and basic troubleshooting