The short answer

A Team Bot is one Grok Bot your whole team talks to, each person in a private chat. On the name: the official docs called it a Shared Bot from about October 28, 2026, but when we read docs.x.ai and Cursor's help on November 11 both said Team Bots again, and Cursor's help notes that a few screens, such as Browse shared Bots, still say shared Bots and that they are the same thing. Sections of this guide written during the rename still say Shared Bot. The owner sets it up once with plugins, secrets, skills and files, then shares it, and teammates use it in the app or in Slack. Shared Bots are for members of a Cursor team who have Grok Bot, and each person's chats use their own allowance.

They arrived in Grok Bot 0.61.0 on September 26, 2026, and SpaceXSI announced them two days later as Team Bots. This page follows the official Shared Bots documentation, Cursor's help and the changelog through 0.77.0 (October 26), read on October 28; we use the Shared Bot name throughout and keep Team Bot only where we quote the changelog, older app screens or page titles. The docs now describe sharing the way you would share a document: with everyone on the team, or with People you invite, and the sidebar's + button shows Browse shared Bots. We have not set up one ourselves.

Documentation: Team Bots (called Shared Bots in late October 2026) ↗ SpaceXSI: Team Bots, shared AI teammates that learn as they work (September 28, 2026) ↗ Grok Bot changelog (Team Bots, now Shared Bots, from 0.61.0) ↗ Grok Bot changelog: 0.77.0 (admin-only sharing, Bot-to-Bot messages in DMs, Slack edits, October 26) ↗

Personal BotPublic templateShared 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 any managers, 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 Shared Bots are for members of a Cursor team who have Grok Bot; if Browse shared Bots does not appear under + in the sidebar (Create new Team Bot after New chat in older builds), the help says you are not on a Cursor team or the app needs an update. On a self-serve Teams plan every member has Grok Bot by default. Existing Cursor Teams seats cost $40 (Standard) or $120 (Premium) per user a month, and Cursor's team pricing page gives a Premium seat 5x a Standard seat's usage. Since October 12, SpaceXSI's The X Subscription also sells team seats at $30 (Premium), $100 (Super) or $200 (Ultra) per seat a month, mixable within one team, each with Grok Bot and its own weekly usage pool. The Shared Bots documentation still describes Cursor Teams and Enterprise and does not yet mention X Subscription team plans. Enterprise pricing is custom.

We found no separate Shared 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; Slack posts from apps or workflows that are not linked to a Cursor account count against the owner; and, according to the docs and Cursor's help read November 11, a reply to someone in Slack who has not linked an account or is not on the team uses the team's usage. 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 (called Shared Bots in late October 2026) ↗ Team Bots (called Shared Bots in late October 2026) ↗ Cursor pricing (now showing The X Subscription plans) ↗ Cursor team pricing ↗ Cursor help: plans and billing ↗ The X Subscription docs: pricing and team seats ↗ The X Subscription docs: team plans and seats ↗

Set one up

Create and publish Shared 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. SpaceXSI's announcement also points to pre-built Shared Bots for sales, product management, marketing and data analytics.

Cursor's Shared Bots help, checked October 29, describes the current route differently: choose + in the sidebar, then Create a Bot, tell it what it should help the team with, follow its setup steps for apps, secrets, skills and files, then click the Bot's name at the top of the chat and choose Share. Under Who has access, pick your team or People you invite, which asks you to confirm with Limit access, and add people or groups as Collaborator (they chat with the Bot) or Manager (they can also change its instructions, skills, memory and apps). Teammates find it under + → Browse shared Bots and choose Add. On the phone, sharing and browsing need Grok Bot 1.19.0 or later on iPhone and Android; the help says earlier versions still open shared Bots already in your list, with some screens still saying Team Bots. Read again on November 11, the help adds a draft step: until you publish it, the Bot is a draft only you can see, and when the Bot says it is ready to share you choose Publish. It also says a Team Bot cannot be your primary Bot. The steps below are the flow as the docs and Cursor's help described it through October 25.

Documentation: Team Bots (called Shared Bots in late October 2026) ↗ Cursor help: Team Bots (called Shared Bots in late October 2026) ↗ SpaceXSI: 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 start from an existing Bot whose memories or chat are mostly about you, it asks How should your Team Bot start?; choose Start fresh rather than the Copy option. Otherwise it makes the team copy right away. Your personal Bot keeps working and its chats stay with it.
  3. Work through the setup cards, choosing what the team copy gets: plugins, secrets, memories, skills, files and routines. Memories you do not pick stay private. Each routine either moves to the team copy or stays on your personal Bot, and runs only for you either way.
  4. Give it one concrete job, try it on real tasks, and correct it. Until you publish, only you can see it.
  5. Rename it from the default and write a description of up to 140 characters in the Bot's own voice; Cursor's help says teammates cannot see a Shared Bot that still has the default name and no description. 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 Shared 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 Shared Bot holds up to 25 secrets, each value between 8 characters and 4,096 bytes, and when it needs a new key it asks in the owner's or a manager's chat. 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 (called Shared Bots in late October 2026) ↗

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 Shared Bot keeps team memory, read by every teammate's conversation, and private notes with each person. Read on November 12, the docs say that when a teammate teaches it something for the team, the Bot suggests the change instead of saving it straight away: suggested memory and skill changes wait under Review learnings until the owner or a Manager chooses Approve or Reject, while changes the owner or a Manager makes in the Bot's main chat apply right away. 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 Shared 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 uses a separate computer for that conversation instead of yours. Shared Bots always run in the cloud. Our shared-computer guide explains what a computer holds.

Documentation: Team Bots (called Shared Bots in late October 2026) ↗ Cursor help: Team Bots (called Shared Bots in late October 2026) ↗

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 Shared Bot to Slack

A published Shared 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. Who it answers depends on how it is shared, according to the docs and Cursor's help read November 11. A Bot shared with Your organization, or with a team that is not in an organization or is the only team in one, answers any full member of the Slack workspace in channels and threads, even without a linked Cursor account or a seat on the team; without a linked account they are told once per thread that some features will be limited, and in a DM they still need to connect first. A Bot shared with your team or with certain people answers only those people. Slack guests, Slack Connect channels and other Slack workspaces are never included, and a team admin can turn workspace access off.

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. The October 11 entry adds that Bots answer Slack messages whose thread they cannot read, and that asking a teammate's Bot no longer adds it to your sidebar. Since 0.71.2 (October 14), Slack setup's Connect goes straight to Slack and Awaiting admin approval offers Resubmit. Since 0.75.5 (October 23), Bots record who asked for each message they post in Slack, so anyone in the thread can ask who requested it; they answer thread replies that were also sent to the channel; and when a Shared Bot's routine replies in a Slack thread, the Bot follows that thread and answers later replies without an @mention. That last change means a routine's thread can turn into a conversation billed to whoever replies, so keep routine posts in channels where that is welcome. Until 1.0.1 (November 11) Slack was the only chat app for Team Bots; Microsoft Teams is the second, covered in the next section. A Cursor staff member said on September 30 that the team is looking at a Google Chat connector, and teams were still asking for one on October 11.

Documentation: Team Bots (called Shared Bots in late October 2026) ↗ Grok Bot changelog (Team Bots, now Shared Bots, from 0.61.0) ↗ Grok Bot changelog: 0.71.2 (Messaging between Bots switch, Manage Bot Computers, October 14) ↗ Grok Bot changelog: 0.75.5 (Slack thread following, whose connector, October 23) ↗ Cursor help: Team Bots (called Shared Bots in late October 2026) ↗ Forum: Google Chat connector request (staff reply, September 30) ↗

  1. Publish the Bot first. The owner adds it to Slack; the docs say a manager can too, using the owner's Slack connection, so the owner connects Slack first.
  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, then Check approval once an admin approves. The Bot sends you a welcome DM in Slack when it is ready.
  4. Invite the Bot to channels, for example with /invite @BotName. Remove from Slack in the Bot's details deletes the Slack app; the Shared Bot keeps working in the app.
  5. Ask each teammate to link their Slack account once under Settings → General → Team Bots.

Add a Team Bot to Microsoft Teams (new in 1.0.1)

The 1.0.1 changelog entry (November 11) says Team Bots can join Microsoft Teams: a team admin turns it on, an owner or Manager connects the Bot, and a Teams admin approves it. docs.x.ai's new Microsoft Teams page, read November 12, says the Bot then works the way it does in Slack: your team can mention it in channels, chat with it directly and add it to group chats, and it acts for the person who asked, uses their usage and asks before risky actions. Cursor's Team Bots help did not mention Microsoft Teams when we read it the same day, and we have not connected one ourselves.

Before the steps, the docs list three requirements: a published Team Bot that you own or manage, Microsoft Teams turned on for your Cursor team by a team admin, and a Microsoft account in the organization that uses Teams. The admin turns it on from the Grok Bot page of the team dashboard, under Shared Bots, with Enable next to Enable Microsoft Teams, signing in with a Microsoft Teams or Global administrator account; Revoke turns it off, and Manage Microsoft Teams accounts lists the members who linked an account. A Microsoft Teams admin still approves each Bot in the Teams admin center.

In Teams, the docs say the Bot reads the thread it is in and the channels of the teams it joined, reads files attached to posts, and sends you files through your OneDrive; if you ask for a file in a channel or group chat, it asks you to message it directly. The first time you message it, it replies with a Link Account card only you can see, or you can link first under Settings → General → Team Bots. Removing the Bot from Microsoft Teams removes the app from your organization; disconnecting your Microsoft account disconnects it from every Bot you own in that organization, while Bots already in Teams keep answering; deleting the Bot also removes it from Teams. Having a Bot join a Teams call is a separate feature, covered in our meetings guide.

Documentation: Grok Bot changelog: 1.0.1 (Microsoft Teams, shared connectors, Review learnings, Bot sharing, November 11) ↗ Use Grok Bot in Microsoft Teams ↗ Teams and enterprises ↗ Team Bots (called Shared Bots in late October 2026) ↗ Cursor help: Team Bots (called Shared Bots in late October 2026) ↗

What you seeWhat the docs say it means
Microsoft Teams isn't enabled for your teamA team admin needs to choose Enable Microsoft Teams on the Grok Bot page of the team dashboard
Publish this Bot to your team first, then add it to Microsoft TeamsThe Bot is still a draft; choose Publish, then connect
Waiting on admin approvalYour Teams admin has not approved the Bot; send them the link in the dialog, then choose Check again
Your Teams admin declined the BotCheck their note, make changes and choose Resubmit
Microsoft Teams didn't accept the appYour organization does not allow custom apps in Teams; choose Download app package and send it to your Teams admin to upload
Blocked by your organization's Teams app policyA Microsoft Teams admin needs to allow the app in the Teams admin center
Need admin approvalThe Microsoft sign-in needs an admin's consent; send a Microsoft Teams or Global admin the link the dialog shows, then connect again
Microsoft Teams stopped working for your teamThe team's connection expired; a Cursor team admin needs to choose Reconnect Microsoft Teams on the dashboard
Finishing setup in Microsoft TeamsThe Bot is approved and Teams is still setting it up, which can take up to an hour
  1. Ask a Cursor team admin to choose Enable next to Enable Microsoft Teams on the dashboard's Grok Bot page and accept the permissions Microsoft shows.
  2. Publish the Bot. In its details, find Bring to your team's Microsoft Teams, or choose Manage and look under Channels, then choose Connect Microsoft Teams and sign in with Microsoft.
  3. While the dialog says Waiting on admin approval, send your Microsoft Teams admin the link it shows. The docs say Microsoft does not notify them; they approve the Bot in the Teams admin center under Teams apps, Manage apps, Pending approval.
  4. Choose Check again after they approve. Teams then finishes setting up the Bot on its own, which the docs say can take up to an hour.
  5. Add the Bot to a team from Microsoft Teams to use it in a channel, and have each teammate link their Microsoft account from the Link Account card.

Approvals in shared conversations

In a Slack thread or group chat, a Shared Bot asks before using one of your own connectors: Allow once, Always allow for this Bot, Always allow for all Team Bots, or Skip; the docs, checked October 29, now word the menu Always allow for your messages to this Bot or to every Shared Bot. Undo remembered answers in Settings → General → Team Bots → Clear. Plugins set up on the Bot itself do not ask. Cursor's help, read November 11, says that in your own chat a Team Bot can also use your apps, and that it asks before it uses one of your personal accounts, with the same Allow once, Always allow and Skip choices.

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 Shared Bot's plugins and secrets read-only where you can.

Cursor's help now matches the October 11 changelog entry, which said teammates can approve a Shared Bot's Auto-review requests, including Always allow, from their own DM with it. When we checked on October 25 the help said a Shared Bot asks the person it is answering before risky actions: you answer its cards in your own chat, only the person who asked can answer a Review an action card in a Slack thread, and in a group chat only the person whose message the Bot is answering can answer. It no longer says a Shared Bot asks only in its owner's chat. Since 0.75.5, teammates in their own DM can also react to messages and quote with Add to chat, and the general Auto-review changes apply: a denied card stops the Bot from retrying that action until you send another message. What a teammate's Always allow covers is still not spelled out, so treat it as widening what the Bot can do in that teammate's chats. Since 0.75.8 (October 24), Auto-review approval cards in Slack describe the action the way they do in the app, and Auto-review takes a second look before showing a card, so teammates should see fewer of them. See Is Grok Bot safe? for the wider security model.

Documentation: Team Bots (called Shared Bots in late October 2026) ↗ Approvals, security and privacy ↗ Cursor help: Team Bots (called Shared Bots in late October 2026) ↗ Grok Bot changelog (Team Bots, now Shared Bots, from 0.61.0) ↗ Grok Bot changelog: 0.75.5 (Slack thread following, whose connector, October 23) ↗

Owners, managers and admins

The owner edits the Bot's name, description, plugins, secrets, skills, files and Slack app. Since 0.64.0 (September 30) the owner can also add managers from the Managers section of the Bot's details: a manager can change the profile, skills, plugins, secrets and Slack app, and every change reaches the whole team, while publishing, unpublishing and deleting stay with the owner. Cursor's help, checked October 25, now agrees that the owner and Managers can change a Shared Bot and that only the owner can unpublish or delete it. Its Share this Bot card adds people or groups as a Collaborator, who can chat with the Bot, or a Manager, who can also change its setup and share it; since 0.75.5 someone who manages the Bot through a group sees their role as Manager there. Unpublish takes the Bot away until you publish again, and teammates' chats and routines come back when you do. Deleting it removes it for everyone, with their chats and routines, and cannot be undone. Read on November 11, the docs and help no longer mention unpublishing: they say only the owner can delete a Team Bot from the sidebar, and that a team admin can also delete it from Manage Bots in the Cursor dashboard. They also say that what a Team Bot learns from a teammate waits until the owner or a Manager approves it under Review learnings. The changelog lists Review learnings, the Allow Shared Logins shared connector and the Bot sharing setting as new in 1.0.1 (November 11), a day after we first read them in the docs, and adds that teammates' comments on a Team Bot's Pages now reach the Bot and that custom MCP connectors on a Team Bot show as shared with everyone, without a Share my account option. To set up a shared connector, the docs say the owner or a Manager opens the Bot's details, chooses Service accounts under Setup, picks an app under Shared connectors, and chooses Use individual accounts, Share your account, or, where the app supports it, the Bot's own account; the app's row shows whose account the Bot uses, and Stop sharing ends it. The docs advise sharing only an account that holds nothing sensitive or private.

Team admins work from the Grok Bot page of the Cursor dashboard. Under Manage Shared Bots (Manage Team Bots before the rename) they see who can use each shared Bot, change it, and pick All team or groups under Auto-add so the Bot appears in members' sidebars; the docs say members who get a Bot this way cannot hide it, and that Auto-add applies only to groups that have access. Admins can search Shared 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 Shared Bot events. Shared Bots follow the same connector policy, Team Rules and Auto-review settings as other Bots. Read on November 11, the docs and help call the admin page Manage Bots, under Shared Bots on the dashboard's Grok Bot page, and list three Sharing settings there: Bot sharing (Everyone or Admins only); Allow Shared Logins, which lets Managers share their own app logins as shared connectors so that everyone who uses the Bot acts through that Manager's account, and is off by default; and Slack Workspace Access, which lets Slack workspace members who are not on the team use Bots shared with your organization, and is on by default.

What admins cannot do yet: a Cursor staff member said on October 10 that there is no setting to stop members creating their own Bots, or publishing their own Shared Bots. The controls available are who has Grok Bot at all (Manage Group Access), which Shared Bots are pushed to whom, and keeping each Shared Bot's setup with its owner and managers. Agent email, an address Bots can use for mail, is off for Cursor teams until an admin turns on Agent Email under Bot Capabilities, and a Shared Bot has no shared team address.

Documentation: Team Bots (called Shared Bots in late October 2026) ↗ Grok Bot changelog (Team Bots, now Shared Bots, from 0.61.0) ↗ Grok Bot changelog: 0.75.5 (Slack thread following, whose connector, October 23) ↗ Teams and enterprises ↗ Grok Bot changelog: 1.0.1 (Microsoft Teams, shared connectors, Review learnings, Bot sharing, November 11) ↗ Cursor help: Team Bots (called Shared Bots in late October 2026) ↗ Forum: admins cannot stop members creating their own Bots (staff reply, October 10) ↗ Cursor help: give your Bot an email address ↗

October admin controls: Pages, link previews and Bot messaging

Three releases between October 14 and 23 gave team admins new switches. The rows below paraphrase the changelog; where Cursor's help or the docs describe the same feature, we say so.

Documentation: Grok Bot changelog: 0.71.2 (Messaging between Bots switch, Manage Bot Computers, October 14) ↗ Grok Bot changelog: 0.75.2 (Page sharing, link previews, collaborator routines, October 22) ↗ Cursor help: Pages (sharing) ↗ Manage computers (Manage Member Computers and Data) ↗

ControlWhat the changelog saysWhere it lives, and caveats
Messaging between Bots (0.71.2)Team admins can turn off Messaging between BotsUnder Bot capabilities on the dashboard; the changelog does not say what default teams start with
Page sharing (0.75.2)Page owners can share a Page with their whole organization or another team; team admins can limit who can share Pages with everyone on the teamCursor's Pages help says public links are off on Enterprise teams and that Pages are not yet available on Enterprise teams; see our Pages guide
Link previews (0.75.2)Team admins can turn on link previews that show a Shared Bot's name, description, color and shape wherever its link is postedOff unless an admin turns it on; anyone who sees the link sees the description, so keep it free of internal detail
Team icon (0.75.2)Team admins can upload a team iconCosmetic
Collaborator routines (0.75.2)Shared Bot owners and managers can let collaborators create routines from ConfigureEach routine still runs as the person who set it up and counts against their usage
Manage Bot Computers (0.71.2, Enterprise)Enterprise admins can recreate, terminate or delete members' Grok Bot computers from the dashboard or the Admin APIThe docs now describe this under Security & Compliance as Manage Member Computers and Data. The docs page, updated November 3, also covers the Organization API route: organization admins can run the same operations from a script with an Organization API key that has the admin:* scope, and the API and dashboard share a limit of one operation per team at a time
Data deletion (0.75.2, Enterprise)Enterprise admins can permanently delete a member's Grok Bot data from Manage Member Computers and Data, or through the Admin APIThe docs say Delete All Grok Bot Data removes the member's Bots on every team, including Shared Bots teammates use, plus conversations, memory, routines, connected apps, email inboxes, files and computers. It works on up to 100 members at a time, is recorded in the Audit Log and cannot be undone (the docs page, updated November 3 and read November 4, does not mention typing DELETE to confirm)
Restart VMs (official docs, read October 30)Not in a changelog entry; the docs say that after some team setting changes the Grok Bot dashboard page shows Restart VMs to apply changed settings, and Restart all VMs, then Recreate VMs, recreates every member's computer with the current settingsTeam admins on an Enterprise team can run it, not only organization admins. Members see Updating Grok Bot's Computer, working Bots pause and continue on the new computer, and sign-in sessions inside it can drop
Terminate Inactive Computers (official docs, Enterprise)Off by default. When on, Cursor terminates a member's computer once it is asleep and nobody has messaged any of their Bots for 30 days; routines and other work a Bot starts on its own do not countNo grace period for members already past 30 days. The durable disk stays, so the next message starts a fresh computer with Bots, files and logins, but apps and packages members installed themselves are removed. An awake computer is never terminated

What changed for teammates in October

For people who use a Shared Bot rather than run it, the October releases are mostly about knowing whose account did what. Since 0.71.2 (October 14), when a Shared Bot asks to use your connected account, the card explains the access covers only your own messages, and allowing one of your plugins works right away. Since 0.75.5 (October 23), Shared Bots name connectors the way your plugin list does, such as Google Slides, when they ask to use one or say whose they used, and work a Shared Bot hands off in a shared chat can use the connectors you allowed, with its reply saying whose connector it used.

Smaller changes since 0.75.2 (October 22): Shared Bots shared with you open straight to their saved conversation; a shared Shared Bot's welcome in a team or group chat includes a Chat with me link, and an owner-only Bot greets only its owner. One personal feature does not carry over: Cursor's help says Vault, where personal Bots keep logins and cards, is not supported on Shared Bots, so a Shared Bot's keys still go under Secrets.

The 0.75.8 entry (October 24) tightens who can reach a Shared Bot: people not on its share list, including teammates, no longer have access to it until an owner shares it with them. If a teammate who used to see a Shared Bot cannot find it, the share list is the first place to look. Two Slack fixes land in the same entry: a Shared Bot's routines can read Slack channels you and the Bot are both in, instead of refusing every read, and when a Shared Bot edits one of its own Slack messages the message shows a muted (edited) label. For any Bot, a post it makes to Slack for you, such as from a routine, no longer notifies your phone or raises its unread badge, and when a safety check blocks a reply in Slack the Bot now says so and suggests a different message.

The 0.77.0 entry (October 26) adds more. In a DM with a Shared Bot, teammates can have it message other Shared Bots they can use; in Slack, Shared Bots can edit messages they posted and remove reactions they added; team admins can limit Bot sharing to admins, and can choose whether members publish Bot templates publicly, only to the team, or not at all; plugins a team admin would not allow show Disabled by team admin; and Enterprise audit logs record changes to a team's trusted CA certificates. Among its fixes: linked teammates on a Shared Bot use their own connectors and memory, a published Shared Bot no longer says everyone on the team can use it, Share on its team access card gives the team access, a teammate's own chat with your Shared Bot disables the computer permission buttons, and a Shared Bot that acknowledges a request without answering now follows up. The docs' Shared Bots page adds two error messages worth knowing: No Access to This Bot means it is shared only with certain people, and This Bot's owner has reached their usage limit means the reply was billed to the owner, so ask them to check their plan.

The 0.78.1 entry (October 27, also covering 0.78.0) changes who can reach a Shared Bot and what it can sign in with. In Share, Who has access lists your team and organization, and a Shared Bot can be limited to Only you. Managers can add logins to a Shared Bot's own Vault, in Configure under Tools, and the Bot signs in with them for the team; Cursor's secrets help, checked October 29, still says Vault is not supported on shared Bots and to use Secrets, so the two official sources disagree until the help catches up. When a Shared Bot routine needs one of your connectors, it asks in the routine's Slack thread and tags you. When a team limits sharing, share controls say Only team admins can share Bots; a team Page appears in the Library under every Bot that published it; Shared Bot Library rows get a Pin button; and the team dashboard groups setup scripts, setup files and team secrets under Bot computers, with one Security & compliance card for computer controls. The changelog also says the Grok Bot admin page now says Shared Bots, with Manage Shared Bots and Create Bot, which matched Cursor's help when we read it on October 29; by November 11 the help said Manage Bots under Shared Bots, and Team Bots elsewhere. Among the fixes: Share works for people on more than one team with no team selected, a Shared Bot's Shared with your team list shows only Pages that Bot made, Shared Bots search Slack when asked instead of refusing, and on Enterprise with Terminate Inactive Computers on, a computer counts as inactive after 30 days without a message to any of its Bots.

SpaceXSI's own sales team described its setup on October 27: an Account Intel Bot that briefs reps and updates Salesforce after calls, a Quote Bot that drafts proposals and order forms and shows a preview before changing Salesforce, and a Deal Bot with Deal Desk permissions that reps lack, so a rep cannot approve their own discount. SpaceXSI says every Bot acts with each user's permissions, rate limits guard against unintended bulk changes, and customer-facing messages still get human review. It is a vendor case study, not a setup we have run, but the pattern of per-user permissions plus a specialist Bot for the privileged step matches what the docs let you build.

On November 2 SpaceXSI described a second internal example, Data Bot, which its data science team teaches and maintains so other teams can query the warehouse without waiting for an analyst. Skills cover metrics definitions, A/B test checks, chart style and dashboards in Databricks or Hex, and dbt conventions. Teams can add it to Slack channels and give it a scheduled metric report to post. The post describes one memory step our Shared Bots section does not cover: the Bot proposes additions to its shared memory from daily use, and its managers approve or reject them before everyone gets them. SpaceXSI estimates Data Bot handled about 70 hours of work in one week and says complex analyses stay with its data scientists. That figure is the vendor's estimate, not something we measured, and we have not run this setup.

November added admin controls. 0.79.2 (November 5) says admins can set a Bot Computer Retention Period, after which inactive members' Bot computers are terminated; the changelog tags it Teams. docs.x.ai's Teams and Enterprise page, read November 10, lists the settings under Data Retention on the Grok Bot admin page, each off by default and described there as available on the Enterprise plan: Retention Period for Computers deletes a member's computer and its files once no one has messaged any of their Bots for a period of 30 to 365 days, Retention Period for Bots covers Bots no one has messaged for 60 to 365 days, with an email to the owner 30 days before deletion, and Retention Period for Messages deletes Bot messages and attachments older than 30 to 365 days without notifying anyone. The two sources differ on which plans have it, so ask your admin what is set. The same entry says asking a Bot to save a file to its Library puts it in Bot's files for everyone who can use the Bot, and that a custom connector your team policy blocks now shows the admin's reason. 0.78.4 (November 3) says plugin installs follow your team's allowlist, a blocked plugin says Your team admin has disabled this plugin's MCP servers, and GitHub shows Disabled by team admin only when your team's MCP rules actually block it.

Documentation: Grok Bot changelog: 0.79.2 (Bot Computer Retention Period, Bot's files, blocked connector reason, November 5) ↗ Grok Bot changelog: 0.78.4 (team plugin allowlist, GitHub admin label, November 3) ↗ Teams and enterprises ↗ Grok Bot changelog: 0.71.2 (Messaging between Bots switch, Manage Bot Computers, October 14) ↗ Grok Bot changelog: 0.75.2 (Page sharing, link previews, collaborator routines, October 22) ↗ Grok Bot changelog: 0.75.5 (Slack thread following, whose connector, October 23) ↗ Grok Bot changelog: 0.77.0 (admin-only sharing, Bot-to-Bot messages in DMs, Slack edits, October 26) ↗ Grok Bot changelog: 0.78.1 (Only you sharing, a Team Bot's own Vault, routines ask in Slack, October 27) ↗ Cursor help: store secrets securely (Vault and Shared Bot secrets) ↗ Team Bots (called Shared Bots in late October 2026) ↗ SpaceXSI: Your next sales teammate should be a Grok Bot (October 27, 2026) ↗ SpaceXSI: Giving every team a data scientist with Grok Bot (November 2, 2026) ↗ Cursor help: store secrets securely (Vault and Shared Bot secrets) ↗

Routines on a Shared 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 Shared Bot in Slack to set up, change, pause or delete your routines once your Slack account is linked. Since 0.75.2 (October 22), owners and managers can let collaborators create routines from Configure; the changelog does not say whether collaborators can create them without that switch. Since 0.75.5, a Shared Bot's routine that replies in a Slack thread keeps following that thread and answers later replies without an @mention. Our routines guide covers what to check when one does not run.

Documentation: Team Bots (called Shared Bots in late October 2026) ↗ Grok Bot changelog (Team Bots, now Shared Bots, from 0.61.0) ↗ Grok Bot changelog: 0.75.2 (Page sharing, link previews, collaborator routines, October 22) ↗ Grok Bot changelog: 0.75.5 (Slack thread following, whose connector, October 23) ↗

Quick answers

How much do Grok Bot Shared Bots cost?

There is no separate Shared Bots price in any official page we checked. docs.x.ai's Team Bots page, read November 12, says Team Bots are available on Team and Enterprise plans and no longer calls them a beta; existing Cursor Teams seats are $40 (Standard) or $120 (Premium) per user a month. Since October 12, The X Subscription also sells team seats at $30 (Premium), $100 (Super) or $200 (Ultra), each including Grok Bot; the Shared Bots docs do not yet mention these plans. When a teammate talks to a Shared Bot, the usage counts against that teammate's own Grok Bot allowance, not the owner's.

Can the owner of a Shared 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 Shared 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 the docs, read November 12, say one teammate's connection is never used for someone else unless a Manager shares it as a shared connector, which a team admin has to allow first. 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; the docs, checked October 29, now word the menu Always allow for your messages to this Bot or to every Shared Bot.

Can I use Shared Bots on an individual plan?

No. Cursor's help says Shared Bots are for members of a Cursor team who have Grok Bot, and docs.x.ai says they are available on Team and Enterprise plans; SpaceXSI announced them in September as a public beta and, with Grok Bot 1.0 in November, no longer describes them that way. Without access, a shared Bot link shows Shared Bots Not Available (Team Bots Not Available in older builds).

Can an admin stop members from creating their own Bots?

Partly, since 0.77.0. A Cursor staff member said on October 10 that any member with Grok Bot access can create personal Bots and publish their own Shared Bots, and passed on the request for an admin-only setting. The October 26 changelog entry (0.77.0) answers the sharing half: team admins can limit Bot sharing to admins, and share controls then say Your admin has disabled Bot sharing; the docs, read November 12, give the message as Only team admins can share Bots, shown when you hover the disabled Share button. Nothing in the notes or the docs stops members creating personal Bots; admins can still limit who has Grok Bot at all, push chosen shared Bots to everyone, and keep each shared Bot's setup with its owner and managers.

Are Team Bots and Shared Bots the same thing?

Yes. When we read the official docs on October 28, 2026, docs.x.ai had replaced its Team Bots page with a Shared Bots page, every other docs page said shared Bot, and Cursor's Team Bots help address redirected to a Shared Bots page. The changelog entry of October 26 still says Team Bot, so the app may show either name for a while. The docs describe the same feature: one Bot shared with a Cursor team, each person in a private chat, run in the cloud.

Can a Shared Bot be my primary Bot?

No. The 0.68.0 changelog (October 5) says Shared 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
  • DOGE (Department of Grok Efficiency) 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 →