The short answer

A Team Bot is one Grok Bot your whole team talks to, each person in a private chat. The owner sets it up once with plugins, secrets, skills and files, then publishes it, and teammates use it in the app or in Slack. Team Bots are in public beta on Cursor Teams and Enterprise plans, and each person's chats use their own allowance.

They arrived in Grok Bot 0.61.0 on September 26, 2026, and SpaceXAI announced them two days later. This page follows the official Team Bots documentation, last updated October 2, plus Cursor's help and the changelog. We have not set up a Team Bot ourselves.

Documentation: Team Bots ↗ SpaceXAI: Team Bots, shared AI teammates that learn as they work (September 28, 2026) ↗ Grok Bot changelog (Team Bots from 0.61.0) ↗

Personal BotPublic templateTeam Bot
Who talks to itOnly youEach person who adds it talks to their own copyEveryone on your team, each in their own chat
Who maintains itYouEach copy's new owner, separatelyThe owner, and changes reach everyone
MemoryYoursStarts from what the template shares, then separate per copyTeam memory, plus private notes with each person
Whose usageYoursThe person who added the copyThe teammate in each chat; the owner for posts from Slack workflows

Who can use them, and what they cost

Cursor's help says Team Bots are for members of a Cursor team who have Grok Bot; if Create new Team Bot does not appear after choosing New, they are not on for your team yet. On a self-serve Teams plan every member has Grok Bot by default. Teams seats cost $40 (Standard) or $120 (Premium) per user a month, or $32 and $96 billed yearly, and Cursor's team pricing page gives a Premium seat 5x a Standard seat's usage. Enterprise pricing is custom.

We found no separate Team Bots price. Usage works per person: a teammate's chats, in the app or Slack, count against that teammate's own allowance; a routine counts against whoever set it up; and Slack messages that do not come from a linked teammate, such as posts from a Slack workflow, count against the owner. A teammate who is out of usage is told so instead of drawing on the owner's. Our plan and pricing guide covers seats and on-demand usage.

Documentation: Cursor help: Team Bots ↗ Team Bots ↗ Cursor pricing (monthly and yearly) ↗ Cursor team pricing ↗ Cursor help: plans and billing ↗

Set one up

Create and publish Team Bots in the desktop app; teammates can then use them on desktop, mobile and Slack. You can start from scratch or publish a team copy of a Bot you already have. SpaceXAI's announcement also points to pre-built Team Bots for sales, product management, marketing and data analytics.

Documentation: Team Bots ↗ Cursor help: Team Bots ↗ SpaceXAI: Team Bots, shared AI teammates that learn as they work (September 28, 2026) ↗

  1. Choose New chat (Cmd/Ctrl+N), then Create new Team Bot. Or open an existing Bot's Share menu and choose Publish to Team.
  2. If you started from an existing Bot whose memories are mostly about you, choose Start fresh rather than Copy; the docs say a copy of a personal Bot will not do much for your team.
  3. Work through the setup cards for plugins, secrets, skills and files, choosing what the team copy gets. Memories you do not pick stay private.
  4. Give it one concrete job, try it on real tasks, and correct it. Until you publish, only you can see it.
  5. Write a description of up to 140 characters in the Bot's own voice, then choose Publish to team. Teammates find it under New chat → Team Bots, or through Copy link.

Plugins, secrets, skills and files

Plugins added to a Team Bot work in every conversation, but how a plugin signs in decides whose access the Bot uses. The docs' example: a Datadog plugin configured with a read-only key, so nobody signs in, and a Linear plugin each teammate connects, so tickets are created by the person who asked.

Secrets are for keys that have no plugin sign-in. Values are encrypted, never shown to teammates or to the Bot, and replaced with [REDACTED] in command output, files and plugin calls. The Bot can use every secret in any teammate's conversation, so the docs advise scoped, read-only service-account keys rather than personal credentials. A Team Bot holds up to 25 secrets. Files accept .txt, .md, .markdown, .csv, .json, .yaml and .yml, up to 256,000 characters each, and team skills apply in every teammate's chat.

Documentation: Team Bots ↗

Plugin typeWhose access the Bot usesSetup for teammates
Signs in with an account (OAuth)The person talking to the BotEach teammate connects their own account the first time
Configured with a key or tokenThe Bot's own credential, the same for everyoneNone
Custom MCP server, Remote HTTPSThe Bot's own credential, or each person's sign-in if the server uses OAuthNone, or a one-time sign-in
Custom MCP server, CommandRuns on the computer each conversation usesNone; a command that needs secrets works only in the owner's chat

Memory, privacy and which computer does the work

A Team Bot keeps team memory, read by every teammate's conversation, and private notes with each person. It saves to team memory only when someone says the whole team should have a fact, and tells you when it does. Every chat is private: the owner cannot read teammates' chats, and teammates cannot read the owner's.

The computer depends on the conversation. Your own chat with a teammate's Team Bot usually runs on your own Grok Bot computer, with your files and signed-in sites; Slack channels, group DMs and threads share one computer for that Bot. Do not put anything in a channel thread that everyone in the channel should not see. If your privacy mode is stricter than the owner's, Cursor's help says the chat cannot run on your computer. Team Bots always run in the cloud. Our shared-computer guide explains what a computer holds.

Documentation: Team Bots ↗ Cursor help: Team Bots ↗

ConversationComputer
The owner's own chatThe owner's computer
A teammate's chat in the app, or their 1:1 Slack DMThat teammate's own computer
Slack channels, group DMs and threadsOne shared computer for that Bot, separate from everyone else's

Add a Team Bot to Slack

A published Team Bot can have its own Slack app with its name and avatar, separate from the Cursor app in Slack. It answers direct messages, answers @mentions in channels it has been added to and then follows that thread, and ignores other top-level messages unless a channel-listener routine is set up. It answers only people who have linked their Slack account to Cursor.

Recent releases changed its Slack behaviour. Since 0.63.0 (September 29), a Bot that needs your approval in a Slack thread posts a Review an action card only you can answer. Since 0.66.0 its status line shows what it is working on. Since 0.68.1 (October 7) it can mention a Slack user group, while @here and @channel still do not ping anyone, and it stays quiet on untagged replies that do not need it.

Documentation: Team Bots ↗ Grok Bot changelog (Team Bots from 0.61.0) ↗

  1. Publish the Bot first; only the owner can add it to Slack.
  2. In the Bot's details, choose Bring to your team's Slack, then Connect Slack workspace, and approve Cursor in Slack.
  3. Pick a workspace you can install apps in and choose Connect. If the workspace needs admin approval, choose Send request in Slack and wait for Awaiting admin approval to clear.
  4. Invite the Bot to channels, for example with /invite @BotName.
  5. Ask each teammate to link their Slack account once under Settings → General → Team Bots.

Approvals in shared conversations

In a Slack thread or group chat, a Team Bot asks before using one of your own connectors: Allow once, Always allow for this Bot, Always allow for all Team Bots, or Skip. Undo remembered answers in Settings → General → Team Bots → Clear. Plugins set up on the Bot itself, and your own 1:1 chat, do not ask.

The rest of the approval model applies, with one difference the docs call out: in a conversation where nobody can answer an approval card, the Bot runs without Auto-review and stays within the permissions it was set up with, unless your team requires Auto-review. That is a reason to keep a Team Bot's plugins and secrets read-only where you can. See Is Grok Bot safe? for the wider security model.

Documentation: Team Bots ↗ Approvals, security and privacy ↗

Owners, managers and admins

The owner edits the Bot's name, description, plugins, secrets, skills, files and Slack app, and can Unpublish it to take it away temporarily or delete it permanently. The 0.64.0 changelog (September 30) adds Managers: the creator of a published Team Bot can add teammates who can then change its profile, skills, plugins, secrets and Slack app. The docs page, updated October 2, still says only the owner can change the setup, so check your own app.

Team admins work from the Grok Bot page of the Cursor dashboard. Under Manage Team Bots they choose who gets each Team Bot in their sidebar automatically, All team, None or specific groups, and members see Required by your admin. Admins can search Team Bots by Bot or creator name and delete any of them, which removes it for everyone along with its Slack app. On Enterprise, audit logs record Team Bot events. Team Bots follow the same connector policy, Team Rules and Auto-review settings as other Bots.

Documentation: Team Bots ↗ Grok Bot changelog (Team Bots from 0.61.0) ↗ Teams and enterprises ↗

Routines on a Team Bot

Routines are personal. A routine belongs to whoever set it up, runs as them, reports in their chat, and counts against their usage; no routine runs for the whole team at once. To share a routine's output, have it post somewhere shared, such as a Slack channel. You can also ask a Team Bot in Slack to set up, change, pause or delete your routines once your Slack account is linked. Our routines guide covers what to check when one does not run.

Documentation: Team Bots ↗ Grok Bot changelog (Team Bots from 0.61.0) ↗

Quick answers

How much do Grok Bot Team Bots cost?

There is no separate Team Bots price in any official page we checked. Team Bots are in public beta on Cursor Teams and Enterprise plans; Teams seats are $40 (Standard) or $120 (Premium) per user a month, or $32 and $96 billed yearly. When a teammate talks to a Team Bot, the usage counts against that teammate's own Grok Bot allowance, not the owner's.

Can the owner of a Team Bot read my chats with it?

No. The docs say every teammate gets a private chat, the owner cannot read teammates' chats, and teammates cannot read the owner's. The Bot's private notes about you stay out of other people's conversations. Team memory is different: anything saved there is read by every teammate's conversation.

Does a Team Bot use my Gmail or other accounts?

Only as you. A plugin that needs a sign-in uses the account of whoever is talking to the Bot, and a Team Bot never lends one person's access to another. In a shared conversation such as a Slack thread, it asks before using one of your own connectors, with Allow once, Always allow for this Bot, Always allow for all Team Bots, or Skip.

Can I use Team Bots on an individual plan?

No. Cursor's help says Team Bots are for members of a Cursor team who have Grok Bot, and SpaceXAI announced them as a public beta on Teams and Enterprise plans. Without access, a Team Bot link shows Team Bots Not Available.

Can a Team Bot be my primary Bot?

No. The 0.68.0 changelog (October 5) says Team Bots no longer appear in the primary Bot picker and cannot be a primary Bot.

Bots for this job

Directory listings that match this guide, read from each creator's public share page. They are not tested picks: check what a Bot can reach before you add it.

Browse: Teams & handoffs Bots · Bots for chief of staff

  • Chief of Staff by Vaibhav Arora: Morning digest with source, why it matters, and next action, then delegates routine work onward
  • Chief of Staff by Avid: A single-desk chief of staff that runs your day and your company at once
  • Alfred by Robin: Designs and keeps restructuring your whole roster of bots
  • AI PM OS by George Nurijanian: A product-management operating system packaged as one reusable setup
  • Grant General Manager by Jon ONeill: A general manager for a trades company that stands up the back office

Sources & next steps

Capabilities are grounded in the documentation below. The workflow design and acceptance checks are editorial suggestions.

Build your own workflow brief ↗