Best Grok Bot
Blog

How to Build a Team of AI Agents in Grok Bot

A group of Best Grok Bot mascots standing together on the page's dark background.
TL;DR
  • Start with your primary Bot. Add a new Bot only when a job has its own sources, its own schedule or its own approval needs.
  • Give each Bot one job and one owner for each step, so two Bots don't work on the same thing.
  • All your Bots share one cloud computer and one weekly usage pool, so keep the roster small and the approvals with you.

A Grok Bot team of agents is a handful of Bots, each with one job, passing work to each other while you approve what goes out. This page shows how to decide when to add a Bot, how to keep them from doubling up, and what a team looks like on paper.

How do you build a team of AI agents in Grok Bot?

Start with your primary Bot, then give each new Bot one job, connect only the apps that job needs, and pick one owner for each step. Add Bots one at a time, and only when a job clearly needs its own sources, schedule or approval rules.

The official docs describe your primary Bot as your main point of contact. It checks in with you on its own and coordinates your other Bots. When the same kind of request keeps coming back with its own sources, rules or schedule, the docs suggest giving it its own Bot, or asking your primary Bot to create one.

For a bigger goal, the official guide on how Grok Bot works, checked Nov 17, 2026, says you can ask your primary Bot to create one. Give work its own Bot when it has its own sources, schedule or approval needs. They pass the work along, and you check the result. The same page still lists a marketplace starting point called dr eggbot, which asks you a few questions and sets up Bots with one job each.

If you're setting up the front-door role first, How to Set Up an AI Chief of Staff With Grok Bots walks through it step by step.

One Bot or many?

Start with one, and split off a job when it keeps coming back with its own sources, rules or schedule. The docs say most Bots work best with one clear job, because a Bot with one job builds up memory and context for that job, which a catch-all helper spread across everything can't do.

Each Bot has its own memory and its own conversation. A few facts about you, such as your name and time zone, are shared by all your Bots. So a Bot that only handles your inbox learns your inbox, and it doesn't have to wade through your bills and your leads to find it.

That doesn't mean more is better. The official docs don't give a number of Bots to aim for, and this page won't either. The official advice is to start in your primary Bot, give work its own Bot when it has its own sources, schedule or approval needs, or ask your primary Bot to create one.

The Best Grok Bot mascot with five specialist bots lined up behind it on a near-black background.

How many Bots do you need?

There's no official number, so let the work decide: before you add a Bot, check whether the job has its own sources, its own schedule or its own approval needs. If none of those apply, the job probably belongs with a Bot you already have.

The "when to add a Bot" test

QuestionIf yesIf no
---------
Does the job have its own sources (an inbox, a folder, a set of sites) that other jobs don't use?A separate Bot keeps those sources and that memory in one placeLeave it with the Bot that already has those sources
Does it run on its own schedule or trigger?A separate Bot can own that routine without crowding another Bot's workRun it as a one-off task with an existing Bot
Does it need different approval rules?A separate Bot makes it clear what needs your yesKeep it under the rules you already have

A routine, for this test, is a rule that tells one Bot when to run a job: on a schedule, or when something happens.

Keep the roster tidy as it grows. The official Bots page says you can pin active Bots, group Bots into sections by project, client or business, and hide a Bot from the sidebar without deleting its work or pausing its routines.

As of early November 2026, I run a front-door chief-of-staff bot that hands work to specialists for writing, building, research, inbox, and site work. I add a specialist when a job keeps coming back, and I pause bots that are not needed that week. I am not publishing a headcount, because that number changes.

How do Bots work together?

Bots work together through handoffs and group chats: in a handoff, one Bot sends a message to another, which wakes, does the work and replies later. In a group chat, two to six Bots share one stated outcome, and the chat names who owns the next step.

What the docs say about each:

  • Handoffs. A handoff is an asynchronous message from one Bot to another. You can see the handoff in the conversation, so you can check who passed what.
  • Group chats. A group holds two to six Bots, with a stated shared outcome and who owns the next step. Some things don't appear in a group: approval requests, secret and login requests, and email or Slack drafts. Messages a Bot hands to the group are text only.
  • One owner per step. The official best-practices section says to "make one Bot responsible for each step" in a group chat.

Several Bots can also work at the same time. Each one gets its own screen on your shared computer, and one Bot runs one computer-use task on its screen at a time.

How do you stop Bots from duplicating work?

Give every stage one owner, and don't hand the same job to two Bots at once. The collaboration docs warn that parallel handoffs lead to duplicate work and noisy updates, and there's no switch that stops Bots from messaging each other, so you set the rule yourself.

If you'd rather approve every Bot-to-Bot message, tell each Bot, in plain words, "Don't message other Bots. Ask me first." Then ask each Bot to remember it.

A few habits that keep the lines clear:

  1. Name the owner when you hand off. Say which Bot owns the next step, not "can someone look at this."
  2. One job per Bot. If two Bots both think the inbox is theirs, give it to one.
  3. Use group chats for a shared outcome, not as a crowd. State the outcome and the owner of the next step.
  4. Check the handoff in the conversation. If two Bots picked up the same task, stop one and say who owns it.

On Nov 13, 2026, I switched site work to a one-pass process — the writing is finished first, then one builder pass, then QA — because having bots work on the same thing at once was wasting usage.

Duplicate work also means duplicate usage from your one weekly pool. How to Keep a Grok Bot Team From Burning Your Weekly Usage has the full set of team habits for that.

What does a sample team look like?

Mine has a front-door bot that hands work to specialists for jobs such as inbox, leads, follow-up, scheduling and reporting, under handoff rules I wrote. The blueprint below maps each job to an owner, what it may do and what needs my approval, with my public templates as examples.

My front-door bot is my "chief of staff," and the team also follows usage rules I wrote. My standing rule for any bot that touches the outside world is drafts only, a person approves, and for anything that sends or cancels, one yes on the item and a second yes on the exact text and recipient.

Team blueprint

JobWhich Bot owns itWhat it may doWhat needs your approval
------------
Take requests and route themFront-door bot (your primary Bot)Take requests from you and hand work to the right specialistAnything that leaves the team
Inbox and calendarInbox bot (example template: Daily Email and Calendar Brief)Read email and calendar and give a short brief of what needs youSending anything to anyone but you
New leadsLeads bot (example template: Speed-To-Lead Bot for Insurance Agents)Flag new leads with no contact and draft the first text, email and call openerContacting a lead
Follow-upFollow-up bot (example template: Insurance Lead Follow-Up Writer)Turn stalled leads into a dated plan with draftsSending, scheduling or touching a CRM
SchedulingScheduling bot (no public template)Draft scheduling changes for review; it does not change the calendar on its ownAnything that is sent, and any calendar change
Reporting and adminReporting bot (example template: Agency Reports and Admin Helper)Draft report summaries, chase-ups and late-invoice remindersSending anything

The leads and follow-up examples are built for insurance agents. I don't have a public template for scheduling. Most of these templates draft and a person sends; the Daily Email and Calendar Brief may send only to you.

If you want a set of ready-to-install bots, in order, that look for money before they ask you to spend more of it, see The Payback Roadmap.

The official docs give three example teams of their own. Here's one of them, the campaign team, laid out the same way. The docs name only the three parts; the "may do" and approval columns are my suggestion.

JobWhich Bot owns itWhat it may doWhat needs your approval
------------
Sign-upsSign-up botTrack sign-ups for the campaignMessages to people who signed up
Launch draftsDrafting botDraft launch copyPublishing or sending any draft
Fact checkFact-check botCheck the drafts against your sourcesChanges to the facts

The other two official examples are month-end close (invoices, expenses, exceptions) and a support queue (ticket triage, bug repro, help pages). If you're starting from zero, The First 3 Grok Bots Every Business Owner Should Install covers which jobs to staff first.

What are the limits?

All your Bots share one cloud computer and one weekly usage pool, so they aren't separate, sealed workers with their own budgets and logins. Each Bot runs one computer-use task at a time, and drafts wait for your approval before anything goes out.

  • One shared computer. According to the official docs, all of one user's Bots share one cloud computer, including files, browser sessions and logins. The docs say not to use separate Bots as a security boundary.
  • One task at a time per Bot. Several Bots can work at once, but each runs one computer-use task on its screen at a time.
  • One weekly pool. Your Bots draw from the same weekly usage, so a bigger team doing more work draws more. Plan for that before you add Bots.
  • Your approvals. A Bot messages you when something needs approval, and approval requests don't show in group chats, so check your direct messages.
  • Templates need setup. If you build your team from templates, connected apps have to be reinstalled by each new Bot, and custom scripts and MCP servers don't come along. How to Install a Grok Bot Template (and What It Actually Copies) covers what a template copies.

FAQ: building a Grok Bot team of agents

How do I create a new Bot?

Choose New Bot in the sidebar, or ask your primary Bot to create one. The official guide on how Grok Bot works also names dr eggbot as a starting point that asks a few questions and sets up Bots with one job each.

Can Bots talk to each other?

Yes. A Bot can hand work to another Bot with an asynchronous message, and two to six Bots can share a group chat. If you'd rather approve those messages, tell each Bot "Don't message other Bots. Ask me first," and ask it to remember.

Can several Bots work at once?

Yes. Each Bot gets its own screen on your shared computer, and each runs one computer-use task at a time.

Can one Bot see another Bot's memory?

Each Bot has its own memory and conversation. A few facts about you, such as your name and time zone, are shared by all your Bots. Files, browser sessions and logins sit on the one computer they share.

What if two Bots do the same thing?

Stop one and name a single owner for that step. The official docs advise one owner at each stage, because parallel handoffs create duplicate work and noisy updates.

Do more Bots cost more?

More Bots doing more work draw more from the weekly usage they all share. Why Grok Bot Uses So Much Usage (and How to Make It Last) shows how to find which Bot is using the most.

If you want a set of ready-to-install bots, in order, that look for money before they ask you to spend more of it, see The Payback Roadmap.

This bot is one piece of a full AI team. See how I run my business with a team of Grok bots. The AI Chief of Staff: How I Run My Business With a Team of Grok Bots

Last checked: Nov 17, 2026, ET. This page needs a refresh if the official guidance on primary Bots, group chats, handoffs, shared memory or the shared computer changes, or if dr eggbot is removed.