Skip to content
vibecodershq.
Submit a tool
SPONSOR SLOT · OPENPut your tool in front of builders choosing one right now. One slot, every page, $50 a week.Your tool here, $50 a weekClaim it

Grok Bot 8 min readUpdated 18 Oct 2026

How to build a Grok Bot team: one job per bot

How to build a Grok Bot team that stays useful: one job per bot, one voice, a won't-do list, approval before acting, and quiet when there's nothing new.

A good Grok Bot team is several small bots, each with one job, rather than one bot that tries to do everything. Give each bot one voice, write down what it won't do, have it show you a list and wait for your okay before it acts, and let it stay quiet when there's nothing to report. xAI's own docs describe a Bot as a durable AI teammate with a name and a job, and suggest creating a separate Bot when the work has a distinct goal, set of tools, working style, approval boundary or schedule (docs.x.ai, Create and manage Bots, checked Oct 18, 2026). The seven rules below are the ones our bot designer uses, with examples from the bots we list on Vibe Coders HQ.

What "team" means in Grok Bot

The word covers three different things in the official docs, and it helps to keep them apart.

  • Your own team of Bots. You can run several personal Bots, each with its own role and conversation. The docs recommend starting with the smallest useful roster: one Bot owns an end-to-end outcome, and you add another only when the work has a stable specialist role (docs.x.ai, Create and manage Bots, checked Oct 18, 2026). You can put two to six Bots in a group chat when the handoff itself needs to be visible, and Bots can send work to each other directly (docs.x.ai, Message and collaborate, checked Oct 18, 2026).
  • A Team Bot. This is one Bot your whole team talks to. The owner sets up its plugins, secrets, skills and files once and publishes it. Each teammate gets their own private chat, and a plugin that needs a sign-in uses the account of whoever is asking (docs.x.ai, Team Bots, checked Oct 18, 2026).
  • A Grok Bot team plan. This is the paid plan. On The X Subscription, team plans are priced per seat: Premium at $30, Super at $100 and Ultra at $200 per seat. Each seat gets the same usage as the matching individual tier, members can mix tiers, and Plus isn't available for teams (docs.x.ai, Pricing, checked Oct 18, 2026). x.ai's pricing page lists Teams from $30 per user per month (x.ai/pricing, checked Oct 18, 2026). Admins invite people and assign seats from the Members page at grok.com/dashboard (docs.x.ai, Team plans, checked Oct 18, 2026).

One more point from the docs matters for any team of Bots: all of your Bots share one cloud computer, so files and browser sign-ins are available across your roster. The docs say not to use separate Bots as a security boundary (docs.x.ai, Approvals, security, and privacy, checked Oct 18, 2026).

Rule 1: One job per bot

A bot with one job is easier to name, easier to trust, and easier to fix when it gets something wrong. Our bot pages show what that looks like:

  • Number Scrubber has one job: getting your phone number off people-search sites so you get fewer spam calls.
  • Grocery List turns the meals you plan into one shopping list sorted by aisle. It only writes the list.
  • Return Window warns you before a return window or warranty closes.

None of them also does your email, your calendar and your budget. In our view, when you're tempted to add a second job, that's the moment to create a second bot.

Rule 2: One voice

Each bot should answer in a consistent, predictable shape, so you can scan it quickly. Meeting Prep is a clear example. Every brief has the same five lines: who's attending and their role, why the meeting exists, what you last agreed, the relevant file, and one open question. If it can't find something, it writes "nothing found" instead of guessing.

School Inbox works the same way. Its digest puts to-dos, like a form to sign, at the top, and flags dates with a link to the original email.

Rule 3: A written won't-do list

A won't-do list sets the bot's limits in plain words, so it doesn't have to work them out mid-task. Every bot on our list has one:

  • Number Scrubber won't pay for anything, upload your ID, give a site more than its form asks for, claim the number is fully gone, or contact anyone.
  • Tax Folder never files a return, gives tax advice, logs in to IRS or state sites, pays anything, emails anyone, or shows full Social Security or account numbers.
  • School Inbox never emails the school, signs or pays for anything, deletes mail, or shares your kids' information.
  • Return Window never starts a return, contacts sellers, buys anything, or deletes mail.
  • Meeting Prep never changes your meetings, emails anyone, or edits your files.

xAI's docs support the same idea. They suggest putting rules that should always hold, such as "Never send external messages without approval," in the Bot's description rather than in a one-off message (docs.x.ai, Create and manage Bots, checked Oct 18, 2026).

Rule 4: Show the list, then wait for an okay

Before a bot does something on your behalf, it should show you what it's about to do and wait. Number Scrubber does this: each run, it shows a numbered list of listings with each site's link and how that site's free opt-out works, and it files an opt-out only after you say yes to that site.

Grok Bot has built-in tools for this. With Auto-review on, an Ask first rule always stops matching actions for your approval, and if an Ask first rule and an Allow automatically rule both match, Ask first wins. The docs recommend narrow rules, such as asking first before sending any external email (docs.x.ai, Approvals, security, and privacy, checked Oct 18, 2026). In our view, the list-then-okay habit and an Ask first rule work best together: the list tells you what will happen, and the rule makes sure nothing happens without you.

Rule 5: Stay quiet when there's nothing to say

A team of bots that messages you every day with nothing new soon gets ignored. Two of our bots are built around this:

  • School Inbox doesn't send a digest if no school mail came in that week.
  • Return Window offers a daily check that only messages you when something is about to close.

xAI's changelog notes a related change for Team Bots in Slack: in threads it follows, a Team Bot stays quiet on untagged replies that don't need it, such as emoji-only replies (x.ai, Grok Bot changelog, v0.68.1, Oct 7, 2026, checked Oct 18, 2026).

Rule 6: Hand off, don't overlap

When two jobs sit close together, each bot names the bot that owns the other job, so the two don't duplicate work. Vibe Coders HQ runs this way: one bot drafts our X posts, a person approves each one, and only one bot posts.

Rule 7: Connect only what the job needs

Give each bot only the accounts its job needs. Grocery List needs nothing connected. School Inbox connects Gmail or Outlook to read school email, and Google Calendar to add events.

Putting a team together

A simple way to start:

  1. Pick one recurring job and give one bot that job, with a short description and a won't-do list.
  2. Run it for a while and correct it as you go.
  3. Add a second bot only when a new job has its own sources, tools or schedule.
  4. Use a group chat only when you want to see the handoff between bots.
  5. Turn on Ask first rules for sending, paying, deleting and anything you can't undo.

In our view, most people should start with one or two bots. The docs' advice to begin with the smallest useful roster is a good default for AI agent teams of any kind.

You can browse all our bots at vibecodershq.com/bots. For setup basics, see the Grok Bot beginners guide and What can Grok Bot do?

FAQ

What is a Grok Bot teammate? xAI's docs describe a Bot as a durable AI teammate with a name, a job, its own conversation and working context that builds over time.

What's the difference between a Team Bot and a team of Bots? A Team Bot is one Bot your whole team talks to, each person in their own private chat. A team of Bots is several Bots, usually your own, each with a separate job.

How much is the Grok Bot team plan? xAI's docs list team seats at $30 (Premium), $100 (Super) and $200 (Ultra) per seat. Plus isn't available for teams. Checked Oct 18, 2026.

How many Bots should I start with? xAI's docs recommend the smallest useful roster. In our view, start with one bot and one job.

Are separate Bots a security boundary? No. xAI says all your Bots share one cloud computer, including files and sign-ins.

Sources