· Updated · 8 min read · Omkar Satpute and Milind Soni

Grok Bot Team Bots vs MausBot teams: shared agents compared

xAI's Grok Bot Team Bots, launched Sept 28, against MausBot's Team plan and free group chats: price for five people, who runs the bot, chats, approvals.

Grok Bot Team Bots are shared agents an owner publishes to a team. They launched on September 28 in public beta and are now on xAI's Team and Enterprise plans, so the price is a team seat: from $30 a person a month on The X Subscription's Premium, or an existing Cursor Teams plan, on models Grok Bot picks for you, on vendor-run cloud computers. A MausBot team is a set of bots your people can put in a group chat together: free in the app, or $100 a month for five people on the Team plan, run by us, with the models you already pay for. Verdict: pick Team Bots if your team lives in Slack or Microsoft Teams and wants one shared bot everyone chats with; pick MausBot if you want several agents in one room, more than one model, an approval level you set per bot, and a codebase you can read.

What a Grok Team Bot is

xAI announced Team Bots on September 28: "Give a Grok Bot the files, apps, and expertise it needs, then share it so your whole team can work from the same context." It launched in public beta, on the macOS app and in Slack. With Grok Bot 1.0 on November 2, Team Bots are listed for Team and Enterprise plans and can be brought into Microsoft Teams too. A Team Bot holds plugins, secrets, skills and files for everyone who uses it, plus a team memory; its plugins are its connected apps, such as Salesforce, Notion and GitHub. There are pre-built Team Bots for sales, product management, marketing, and data analytics.

One person, the owner, sets a bot up and publishes it to the team. Anyone on the team can share it unless an admin limits sharing to admins, and admins can auto-add it for the whole team or chosen groups from the Grok Bot dashboard. Team rules always apply, and each person's own rules can only make them stricter. After that each teammate gets a private chat with the bot. The owner and Managers cannot read those chats, and teammates cannot read each other's. What the bot learns about you personally stays between you and the bot; team memory and skills are shared, and suggested changes wait for the owner or a Manager.

In Slack, teammates @mention a shared bot in a channel or thread, and it acts for whoever mentioned it, replying in that thread. Full workspace members who have not linked their account can still mention it in channels, with some features limited, but must link first to message it directly. One bot in a channel with many humans is the normal case.

The computer model matters. In your own chat a Team Bot usually works on your own Grok Bot computer, and in Slack channels, threads, group DMs and group chats it uses one shared computer of its own. Each user's computer is dedicated and hardware-isolated. Billing follows the same line: a Team Bot reply uses the Grok Bot usage of the person it is answering, not the owner's. On The X Subscription that is the seat's weekly usage pool, shared with Grok and Cursor; on existing Cursor Teams plans it is the seat's weekly usage, and with on-demand usage off, Grok Bot stops until the weekly reset. Team seats on The X Subscription cost the same as the individual plans: $30 (Premium), $100 (Super) or $200 (Ultra) a person a month. There is no Team-Bots-specific price.

Enterprise, live since September 3, adds the controls a security team asks for: an organization-wide switch, SCIM 2.0 provisioning, directory groups with their own network policy, four network modes, Team Secrets, audit logs, OpenTelemetry export, and a Privacy Mode under which customer data is not used for training. Action Recording is off by default.

What a MausBot team is: AI agents for a small team

MausBot, published on GitHub as OpenMausBot, runs a team of the AI agents you already have: every contact is a bot with its own model, its own computer, and its own connected apps. A team is what happens when you put several of those in a group chat. All of this is in the free app:

  • Group chats. Bots share group chats, and a bot can be Chief of Staff and hand work to its teammates.
  • Approval levels per bot. Every new bot starts at Full access. Set any bot or conversation to Ask for approval, Auto-accept edits or Approve for me, and set its sends through connected apps to ask every time.
  • Memory you can read. Each bot keeps Markdown notes you can open, edit and undo, and every bot reads the same About me, so a preference you tell one bot reaches all of them.
  • A model per bot. Each bot runs on one of 16 agent engines, such as Claude Code, Codex or Grok, or on an API or local model, with the account you already have. The sales bot can be on Claude Code and the inbox bot on Codex, in the same group chat.

For a company that wants more than the free app, there are a hosted Team plan and a self-hosted option. Team is $40 a month for 2 people, plus $20 for each extra person, up to 50, so five people pay $100 a month: shared bots, rooms, and roles; shared team memory; an admin console for people, activity, and usage, where the team's owner adds seats; a Team Cloud with 4 vCPUs and 4 GB of memory, or 8 vCPUs and 8 GB of memory from 6 people; as many cloud computers as your bots need, with 300 computer-hours a month for 2 people, plus 100 for each extra person shared; priority email support. Business self-hosted is $299 a month, or $239 a month billed yearly by agreement, for up to 20 people on your own servers, with no caps on computers or hours because the hardware is yours. In every plan, model usage is on your own accounts or keys; MausBot does not sell model usage.

Side by side

The Grok column comes from xAI's announcements, the Team Bots, Shared Bots and security docs, and The X Subscription's pricing page. Seat prices are the plans' list prices, checked on November 15, 2026. Where a company has not said, the cell says so.

Grok Bot Team BotsMausBot
Price per month for 5 people5 x $30 = $150 on The X Subscription's Premium team seats, up to 5 x $200 = $1,000 on Ultra; existing self-serve Cursor Teams plans keep it; each reply draws on the usage of the person it answersFree app, or $100 on the Team plan; model usage on your own Claude, ChatGPT, or Grok accounts
Who creates a botAn owner sets it up and publishes it; anyone on the team can share it unless admins limit sharing, and admins can auto-add it for everyone or chosen groupsYou make bots in the app, or move them from Grok Bot with Settings, Import; on a team plan, the team shares its bots
Who can read whose chatsNobody else: each teammate has a private chat with the Team Bot, and the owner and Managers cannot read itA group chat is shared by everyone in it. Free app: chats stay in ~/.openmausbot on that person's machine. Team plans: a bot's team chat is shared, each person's private chats can be read by no teammate and no admin, and the admin console shows people, activity, and usage
Where bots runIn your own chat, usually your own persistent cloud computer; in Slack channels, threads and group chats, one shared computer for that bot; each user's computer is hardware-isolatedYour own computer or server, or a cloud computer per bot on a Cloud plan; the Team plan gives the team as many cloud computers as its bots need, with 300 computer-hours a month for 2 people, plus 100 for each extra person shared
ModelsPicked by Grok Bot per task, xAI's or a third party's; no model picker16 agent engines (Claude Code, Codex, Grok and more), API and local models, chosen per bot
Bots talking to each other in one roomBot group chats of 2 to 6 bots exist in Grok Bot; the Team Bots docs describe a Team Bot in channels and group chats with several humans and do not say whether several Team Bots can share oneYes: group chats where a Chief of Staff bot hands work to its teammates
SlackTeammates @mention a shared bot in a channel or thread, or message it directly; Microsoft Teams too since version 1.0On the hosted team plans, teammates mention @MausBot in a channel or message it directly; each channel has a default bot, and +BotName picks another. On every plan and in the free app, Slack is also a connected app a bot can read and post to
Before it actsAuto Review runs most actions and stops sensitive ones for an approval card; team rules always apply, and members can only make them stricter; local commands ask every time by default, and admins can restrict themFull access by default, or Ask, Auto-accept edits or Approve for me per bot; sends can be set to ask every time
Admin controlsGrok Bot dashboard: auto-add bots for groups, who may share bots, team rules; Enterprise adds SCIM 2.0, network controls, Team Secrets and an organization-wide switchTeam plans: shared bots, rooms, and roles (Super admin, Admin, User), with an admin console for people, apps, and usage; SSO coming soon on Business
AuditEnterprise: audit logs and OpenTelemetry export; Action Recording off by defaultThe admin console shows people, activity and usage on every team plan
Self-hostNoYes: a one-command installer for your own Ubuntu server; Business self-hosted is $299 a month, or $239 a month billed yearly by agreement, for up to 20 people
Open sourceNoYes. Apache 2.0 on GitHub, apart from an enterprise/ folder

The questions a shared bot raises

A shared agent is a new object in a company, and the open questions about it are not about features. An analysis on note.com of the Team Bots launch put four of them plainly: whose credentials execute a shared bot's actions; which login and which computer a given run happens on; how the use of a credential is approved and audited; and what happens to the bot, its secrets, and its memories when the owner leaves. xAI's docs now answer the computer question (your own computer in your own chat, one shared computer per bot in Slack channels and group chats) and part of the credentials question: one teammate's connection is never used for someone else unless a Manager shares it as a shared connector, and owners are told to add only keys they are happy for everyone to use. The Enterprise tier answers audit. What happens to a Team Bot when its owner leaves is not spelled out on the Team Bots page as of November 15, 2026.

Reliability is the other thread. On September 1, 2026, Cursor staff confirmed that a stuck cloud computer made every bot on two users' accounts fail at once, and in early November users reported weekly allowances running out days early, as TNW reported. These are reports, not a verdict, but a team whose bots share a computer and a usage pool inherits them together. We covered the shared-computer design in Grok Bot vs MausBot.

In the free app and on the self-hosted plan, more of the answers are structural. A bot acts with the connected apps you signed in to, and its computer is the one in front of you or your own server. Each bot's approval level is yours to set, from Full access, the default, to Ask for approval, and its sends through connected apps can ask every time. When someone leaves the free app, their bots and chats are a folder in their ~/.openmausbot, not a row in someone else's cloud. On the hosted team plans the workspace runs on our servers, with the admin console showing people, activity, and usage.

An Allow / Deny approval card in a MausBot chat, shown before a bot runs a shell command
With a bot set to Ask for approval, its actions stop here first, on your machine or on a cloud computer.

Where Team Bots are ahead

Be honest about the other column. If your company already runs on Slack or Microsoft Teams, a shared bot teammates can message there has a head start: it is live today. MausBot's Slack presence comes with the hosted team plans: a team admin adds MausBot to the company's Slack, teammates mention @MausBot in a channel or message it directly, and a channel conversation uses only the team's shared memory and apps. MausBot is not in Microsoft Teams. Team Bots ship with Salesforce, Notion, and GitHub plugins and four pre-built bots that a sales or marketing lead can publish without building anything, and on Team, Enterprise and Ultra plans, bots join video calls. Enterprise brings SCIM, network controls, Team Secrets, and audit logs; MausBot's team plans have an admin console, with SSO coming soon on Business, and rely on that console and, on the self-hosted plan, your own server for the rest. And "Teach a task", which records you doing a task once and is still rolling out, has no equivalent here; a MausBot bot does not learn a workflow by watching you.

There is also the question of scale. Team Bots are built for a company on xAI's Team or Enterprise plans. MausBot is a young project, started in August 2026, with about 23,000 GitHub stars and a Team plan for up to 50 people.

Which to choose for a small business

Choose Team Bots if your team is on xAI's Team or Enterprise plans or Cursor Teams already, lives in Slack or Microsoft Teams, is happy for Grok Bot to pick the model, and wants an owner to publish one bot that everyone chats with privately. For five new seats that is $150 a month on Premium before any additional usage, up to $1,000 on Ultra.

Choose MausBot if you want several agents in one room, each on the best model for its job; if you want to set each bot's approval level yourself rather than inherit an admin policy; if you need your data on your own machines or your own server; or if someone has to review the code before a bot touches company data. Start with the free app and a group chat of three bots. If the laptop needs to stay shut, the Team plan runs the whole team in the cloud, at $100 a month for five people.

If you are still deciding between the agent products themselves rather than the team layer, see Muse vs Grok Bot vs Dots vs Cue and the Grok Bot pricing breakdown.

Frequently asked questions

How much do Grok Bot Team Bots cost?
There is no separate Team Bots price. New teams get Grok Bot with team seats on The X Subscription, priced like the individual plans: Premium $30, Super $100 and Ultra $200 a person a month. Existing self-serve Cursor Teams plans keep it, and Enterprise goes through xAI's sales team. A Team Bot reply uses the Grok Bot usage of the teammate it is answering, not the owner's.
Can teammates see each other's chats with a shared bot?
No. Each teammate gets their own private chat with a Team Bot, what it learns about you personally stays between you and the bot, and the owner and Managers cannot read anyone else's chat. Plugins, secrets, skills, files and team memory are the shared parts, and suggested changes to team memory and skills wait for the owner or a Manager.
Does MausBot have team plans for a small business?
Yes. Team is $40 a month for 2 people, plus $20 for each extra person, up to 50, run by us, with shared bots, rooms, and roles, shared team memory, an admin console, a Team Cloud with 4 vCPUs and 4 GB of memory, or 8 vCPUs and 8 GB of memory from 6 people, as many cloud computers as your bots need, and 300 computer-hours a month for 2 people, plus 100 for each extra person. Business self-hosted is $299 a month, or $239 a month billed yearly by agreement, on your own servers. Model usage is always on your own accounts.
Can MausBot bots share a room and work together?
Yes, in the free app. Put bots in a group chat, and a bot can be Chief of Staff and hand work to its teammates. Every bot reads the same About me, so a preference you tell one reaches all of them. On a team plan, the whole team shares the bots and a team memory.
Which is open source?
MausBot, which is published on GitHub as OpenMausBot under the Apache 2.0 license, apart from an enterprise/ folder. Grok Bot and Team Bots are closed and run on cloud computers the vendor runs.

Get started with a team of agents

No seat minimum, no contract. Download for macOS, Windows, or Ubuntu, sign in with the AI account or API key you already have, make three bots, and put them in a group chat. Or read the source on GitHub first. When you want it run for the whole team, the Team plan runs it in the cloud for up to 50 people, and the AI Harness SDK gives it to your own customers.

This post is based on the products as they were on . Products change. If something here is out of date, tell us and we will correct it.