Grok Bot Shared Bots: one Bot for the whole team, private chats for everyone

A Shared Bot is a single Grok Bot your whole Cursor team uses, with every person in their own private chat. The owner configures it once (plugins, secrets, skills, files), shares it, and teammates use it in the app or Slack. Each person's chats come out of their own Grok Bot allowance.

The feature shipped in 0.61.0 on September 26, 2026, and SpaceXSI announced it two days later under the name Team Bots. By October 28 the docs called it Shared Bots. This guide covers the docs, Cursor's help and the changelog through 0.78.1 (October 27). We have not built one ourselves.

At a glance#

Who can use one, and who pays#

You need to be on a Cursor team with Grok Bot. If + → Browse shared Bots is missing from the sidebar, Cursor's help says you are either not on a team or need to update the app. On self-serve Teams, every member gets Grok Bot by default.

X Subscription seats can be mixed in one team, each with its own weekly usage pool. The Shared Bots docs do not yet mention these plans. We found no separate Shared Bots charge.

Billing follows the person. A teammate's chats bill that teammate. A routine bills whoever created it. Slack posts not from a linked teammate (say, a Slack workflow) bill the owner. A teammate out of usage is told so rather than drawing on the owner. See our pricing guide for seat details.

Building and sharing one#

Create and publish in the desktop app; teammates can use it on desktop, mobile and Slack. SpaceXSI also offers pre-built Shared Bots for sales, product management, marketing and data analytics.

Current flow (Cursor help, checked October 29)#

1. Choose + in the sidebar, then Create a Bot, and describe the team job.
2. Follow its setup steps for apps, secrets, skills and files.
3. Click the Bot's name at the top of the chat and choose Share.
4. Under Who has access, pick your team or People you invite (confirm with Limit access).
5. Add people or groups as Collaborator (can chat) or Manager (can also edit instructions, skills, memory and apps).
6. Teammates add it from + → Browse shared Bots.

On phones, sharing and browsing need Grok Bot 1.19.0 or later on iPhone and Android.

Converting an existing Bot#

Older builds used Publish to Team from a Bot's Share menu. If your Bot's memory is mostly about you, it asks how the team copy should start; choose Start fresh. Pick which plugins, secrets, memories, skills, files and routines carry over. Unpicked memories stay private, and your personal Bot keeps running. Give it a non-default name and a description of up to 140 characters, or teammates will not see it.

Plugins, secrets and files#

How a plugin signs in decides whose access the Bot uses. The docs' example: Datadog with a read-only key (nobody signs in) next to Linear that each teammate connects (tickets land under the requester).

Secrets cover keys without a plugin sign-in. Values are encrypted, hidden from teammates and the Bot, and shown as [REDACTED] in output. But the Bot can use every secret in any teammate's chat, so the docs recommend scoped, read-only service-account keys. Limits: 25 secrets, each 8 characters to 4,096 bytes.

Files accept .txt, .md, .markdown, .csv, .json, .yaml and .yml, up to 256,000 characters each. Team skills apply in every chat. For connector mechanics, see our plugins and MCP guide.

Privacy: memory, chats and computers#

Team memory is read by every conversation; private notes stay with each person. The Bot only writes to team memory when someone says the whole team should know a fact, and announces it. The owner cannot read teammates' chats, and vice versa.

If your privacy mode is stricter than the owner's, your chat gets a separate computer. Shared Bots always run in the cloud. Our shared computer guide explains what a computer holds.

Slack and approvals#

A published Shared Bot can get its own Slack app with its name and avatar. It answers DMs and @mentions, follows threads it joined, and only responds to people who linked Slack to Cursor. Slack is the only chat app supported; a Google Chat connector is under consideration but unconfirmed.

Connecting Slack#

1. Publish first. The owner connects Slack (a manager can add it using the owner's connection).
2. In the Bot's details, choose Bring to your team's Slack → Connect Slack workspace.
3. If admin approval is needed, choose Send request, then Check approval.
4. Invite it with /invite @BotName.
5. Each teammate links Slack under Settings → General → Team Bots.

In shared spaces the Bot asks before using your connector: Allow once, always-allow (this Bot or every Shared Bot), or Skip. Clear remembered answers under Settings → General → Team Bots → Clear. Where nobody can answer a card, the Bot runs without Auto-review inside its configured permissions, unless your team requires Auto-review. That alone is a reason to keep its plugins read-only. More in our permissions guide.

Watch this: since 0.75.5, a routine reply in a Slack thread keeps following that thread without @mentions, so replies become conversations billed to whoever replies.

Admin controls added in October#

• Manage Shared Bots on the Cursor dashboard: see access, edit, Auto-add to groups (members cannot hide those), search and delete.
• Messaging between Bots off switch (0.71.2).
• Link previews and collaborator routines toggles (0.75.2).
• Share list enforced (0.75.8): teammates not on it lose access.
• Admin-only sharing and template publishing scope (0.77.0).
• Only you sharing option (0.78.1).
• Enterprise: recreate or delete member computers, and Delete All Grok Bot Data (up to 100 members, type DELETE, irreversible).

Members can still create personal Bots; staff confirmed on October 10 there is no setting to stop that.

Common mistakes#

• Putting a personal key in Secrets. Every teammate's chat can use it. Use a scoped service account.
• Expecting a team-wide routine. Routines are personal; have one post to a shared Slack channel instead.
• Leaving the default name. Teammates will not see the Bot.
• Posting sensitive context in a channel thread. Everyone in the channel shares that computer.
• Assuming a teammate lost access by bug. Since 0.75.8, check the share list first.

SpaceXSI's October 27 sales case study shows a sane pattern: per-user permissions everywhere, plus a separate Deal Bot holding the discount-approval permission reps lack. It is a vendor example, not something we have run.

Our take#

Shared Bots are worth it for any team that keeps rebuilding the same Bot per person. Design it like a service account: read-only keys, OAuth plugins for anything that writes, and nothing in Secrets you would not hand every teammate. Start with one narrow job and a short Collaborator list before you open it to the whole team.

Frequently asked questions#

How much do Grok Bot Shared Bots cost?#

No official page lists a separate Shared Bots price. Existing Cursor Teams seats cost $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. A teammate's chats with a Shared Bot count against that teammate's own 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 conversations. Team memory is the exception: anything saved there is read by every teammate's conversation, and the Bot tells you when it saves something to team memory.

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 a Shared Bot never lends one person's access to another. In shared spaces such as a Slack thread, it asks before using your connector, offering Allow once, an always-allow option for this Bot or every Shared Bot, or Skip.

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 SpaceXSI announced them as a public beta on Teams and Enterprise plans. Without access, a shared Bot link shows Shared Bots Not Available, or Team Bots Not Available in older builds.

Can an admin stop members from creating their own Bots?#

Only partly. Since 0.77.0 on October 26, team admins can limit Bot sharing to admins, so members cannot publish Shared Bots. Nothing in the docs or changelog stops members creating personal Bots. Admins can still control who has Grok Bot at all, push chosen Shared Bots to groups, and keep each Bot's setup with its owner and managers.

Are Team Bots and Shared Bots the same thing?#

Yes. By October 28, 2026, docs.x.ai had replaced its Team Bots page with a Shared Bots page, and Cursor's Team Bots help address redirects to Shared Bots. The October 26 changelog still says Team Bot, so the app may show either name for a while. It is the same feature.