# Grok Bot Wiki: full guide text

> Independent, unofficial guide and directory for Grok Bot, SpaceXSI's always-on agent product. 4,005 community templates are listed at https://www.grokbotwiki.com/bots. Not affiliated with SpaceXSI, xAI or X. The site map is at https://www.grokbotwiki.com/llms.txt.

# What is Grok Bot? SpaceXSI's always-on AI agent, explained

> Grok Bot is SpaceXSI's always-on agent: named Bots on a cloud computer using your apps. What it does, what it costs, how it differs from Grok and OpenClaw.

- Canonical page: https://www.grokbotwiki.com/guides/what-is-grok-bot
- Sources checked: 2026-10-29
- Evidence: Official product pages, docs, changelog, Cursor help and SpaceXSI news checked October 11, 2026 · x.ai/bot, x.ai/news and the changelog (through 0.78.1) read in a browser October 29, 2026 · docs.x.ai/grok-bot, The X Subscription docs, cursor.com/pricing and Cursor help rechecked October 25, 2026 · The X Subscription announcement and x.ai/pricing last read October 14, 2026. Suggested workflows have not been independently tested.
- Publisher: Grok Bot Wiki, an independent guide not affiliated with SpaceXSI, xAI or X.

## What is Grok Bot?

Grok Bot is SpaceXSI's (formerly SpaceXAI and xAI) agent product: named AI teammates that share a persistent cloud computer with a browser, files and a terminal, sign into your apps, and keep working after you close your laptop. It launched in beta on August 11, 2026. Since October 12, 2026 it is included with the Premium, Super and Ultra tiers of The X Subscription, and existing paid Cursor and SuperGrok plans still include it.

You create named Bots, give each a job, and message them like coworkers. Every account gets a persistent cloud computer with a browser, a file system and a terminal; Bots sign into your apps with your own logins, use plugins where they exist and the browser where they do not, and keep working while your laptop is closed. Bots can share context, hand tasks to each other, learn skills by watching you, and run routines on a schedule. Our [glossary](https://www.grokbotwiki.com/guides/grok-bot-glossary) defines each of these terms.

It ships as desktop apps for macOS, Windows and Linux (the x.ai/bot downloads list Windows 10 and 11), plus iPhone and Android apps that connect to the same cloud computer; the iOS app also runs on iPad. Access is bundled with other subscriptions rather than sold on its own. SpaceXSI announced on August 26 that Grok Bot was included with SuperGrok, Cursor Pro and all Cursor Teams plans, and Cursor's help also lists seats on a self-serve Grok Business plan. On October 12 SpaceXSI introduced The X Subscription, one plan for Grok, Grok Bot, Cursor and X Premium, which includes Grok Bot from Premium ($30 a month) up; SpaceXSI says existing plans continue unless subscribers choose to switch. By October 25 the x.ai/bot pricing panel showed Premium at $30, Super at $100 and Ultra at $200 a month, and its FAQ said Grok Bot is included with Premium, Super, Ultra, Teams and Enterprise.

The maker's name has changed twice. SpaceX announced it had acquired xAI in February 2026 and the company then traded as SpaceXAI; in October 2026 x.ai switched its branding to SpaceXSI, with the legal entity still SpaceXAI LLC. The company says Cursor became part of it on August 14, 2026, three days after Grok Bot launched. The product name, Grok Bot, is unchanged.

Sources: https://x.ai/news/introducing-grok-bot, https://x.ai/news/grok-bot-more-plans, https://x.ai/news/x-subscription, https://x.ai/pricing, https://docs.x.ai/grok-bot/overview, https://docs.x.ai/grok-bot/faq, https://x.ai/bot, https://x.ai/news, https://x.ai/news/grok-bot-customer-support, https://cursor.com/help/grok-bot/supergrok

## Four things called Grok that are not Grok Bot

The name collides with several older products, which is why search results for 'grokbot' mix agent tutorials with chatbot news. If a page describes an assistant that operates a computer for you, it means Grok Bot. If it describes answering questions in a chat window, it means the chatbot.

Two X handles are easy to mix up. @grok is the chatbot answering in replies. @bot is part of Grok Bot: the docs, updated October 7, say tagging @bot in a post hands that post to your main Bot as a task, @bot replies on X only with a confirmation, and the work happens in the Grok Bot app using your weekly usage. It needs a Grok account with your X account connected and is not yet available to X accounts based in the EU, the UK, Australia, Iceland, Liechtenstein or Norway.

| Name | What it is | Where you use it |
| --- | --- | --- |
| Grok Bot | Always-on agents on a cloud computer that finish work in your apps | Grok Bot desktop and mobile apps, x.ai/bot |
| Grok (the chatbot) | SpaceXSI's conversational assistant and model family | grok.com, the Grok app, @grok on X, the API |
| @grok on X | The chatbot answering mentions inside X posts | Reply to a post tagging @grok |
| Grok Build | SpaceXSI's separate coding agent and developer tooling, with its own documentation and Wikipedia entry | The terminal, web and mobile, not the Bot apps |
| Grok in OpenClaw | Using Grok models, or a SuperGrok subscription, inside the open-source OpenClaw agent platform | Your own OpenClaw Gateway |

Sources: https://en.wikipedia.org/wiki/Grok_(chatbot), https://en.wikipedia.org/wiki/Grok_Build, https://x.ai/news/grok-openclaw, https://docs.x.ai/grok-bot/tag-on-x

## What has changed since launch

Grok Bot ships updates several times a week. The biggest changes since launch: Shared Bots, one Bot shared by a whole team, in public beta on Teams and Enterprise plans since late September; Projects, which let a Bot start a Cloud Agent that plans the work and runs its own agents (0.57.0, September 18); and in October, Connect Apps replacing the in-app Marketplace, automatic updates on by default, and a starred primary Bot that can offer to take work. Our monthly [what's new](https://www.grokbotwiki.com/guides/grok-bot-whats-new) page tracks each release; when we checked on October 29 the latest was 0.78.1, in a changelog entry dated October 27 that also covers 0.78.0. The official docs and Cursor's help now call Team Bots Shared Bots; the changelog still said Team Bot on that date, while noting that the team admin page says Shared Bots.

The October 11 entry (0.69.0 to 0.70.2) added an email address for your Bots: Cursor's help says it is at mail.grokbot.com, one per account and permanent once claimed. Bots can also search and read public X without an X account, show some connected apps such as Figma, Notion and Canva as cards in the chat, and pay with X Money or Stripe Link, and before an action they cannot undo they check your messages for approval. Separately, you can start work from X by tagging @bot, documented on October 7.

Three releases followed. 0.71.2 (October 14) raised attachments to 20 per message with a 200 MB total, files up to 250 MB and videos up to 1 GB, let Bots use up to 200 skills from your installed plugins instead of 24, and made Bot replies and questions notify you on your Mac or Windows PC instead of your phone while you use Grok Bot there. 0.75.2 (October 22) added Pages, reports, memos and dashboards you edit together or have the Bot keep up to date, video creation from a description or an image, a Pinned section in the Library, and Shop Pay at checkout. 0.75.5 (October 23) added a Vault in Settings where Bots can save your logins, cards and contact info and fill them in, and email forwarding; an email or Slack message you ask a Bot to send now goes out once Auto-review allows it, while sends from routines and other turns still wait as drafts. Routines can now run up to 300 times an hour in total, and each routine up to 200 times. 0.75.8 (October 24) lets a Bot offer to add, change or remove one of your Auto-review rules on a card you confirm, shows fewer approval cards for safe actions, lets Bots use a connector's new tools without a reconnect, and limits a Shared Bot to the people on its share list. 0.77.0 (October 26) adds a Permissions section in Settings that lists every Auto-review rule, a Payments tab in Vault where you pick which payment method Bots use first, a 1Password connection that no longer needs a shared vault, cards that ask several questions at once, and Import Memory, which brings your preferences from another AI assistant into your primary Bot; approval cards now stay open for 30 minutes. 0.78.1 (October 27, also covering 0.78.0) turns shopping into cards with photos, rating, price and store, where Buy now starts an order you approve and the Bot then tracks the shipment; adds templates that start a free trial and cancel it before it bills, cancel subscriptions you pick and watch renewal prices; lets Shop Pay connect from Vault's Payments tab; and, where Grok Bot used to offer a free trial, now offers Get Grok Bot with a unified plan.

Sources: https://x.ai/changelog/bot, https://x.ai/changelog/bot#v0.78.1, https://x.ai/changelog/bot#v0.77.0, https://x.ai/news, https://docs.x.ai/grok-bot/tag-on-x, https://cursor.com/help/grok-bot/agent-email, https://docs.x.ai/grok-bot/computer-and-apps, https://cursor.com/help/grok-bot/secrets, https://docs.x.ai/grok-bot/shared-bots

## Spellings you will see

Officially it is Grok Bot, two words. Grokbot, grok-bot and GrokBot appear in repository names, domain names and forum posts. Grocbot, Grokboth and Grok Both are typos that show up in search data. This wiki uses the official two-word form and treats the rest as the same product.

## Where to go next

If you are deciding whether to pay for it, read [the plan and pricing guide](https://www.grokbotwiki.com/guides/grok-bot-which-plan) for every price and the trial terms. If you already have access, [How to use Grok Bot](https://www.grokbotwiki.com/guides/getting-started) walks from install to a first checkable task. If you are comparing it with something else, start with [Grok Bot alternatives](https://www.grokbotwiki.com/guides/grok-bot-alternatives), and read [Is Grok Bot safe?](https://www.grokbotwiki.com/guides/is-grok-bot-safe) before you connect your accounts. Community-made Bots you can add are in our [Bot directory](https://www.grokbotwiki.com/bots).

Sources: https://x.ai/bot

## Quick answers

### Is Grok Bot the same as Grok?

No. Grok is the chatbot, available at grok.com, in the Grok app, and as @grok on X. Grok Bot is a separate product launched in beta on August 11, 2026: named agents that run on a cloud computer, sign into your apps, and keep working after you close your laptop.

### How do you spell it: Grokbot, Grok Bot, Grocbot?

SpaceXSI writes it as two words, Grok Bot. Grokbot and grok-bot are common one-word forms. Grocbot and Grokboth are misspellings we see in search; they all mean the same product.

### Is Grok Bot built on OpenClaw?

No. Grok Bot is a closed, hosted product that runs on Cursor's cloud; SpaceXSI says Cursor became part of the company on August 14, 2026. OpenClaw is an open-source agent platform you run yourself. Separately, SpaceXSI lets you use a SuperGrok subscription inside OpenClaw, which is where the confusion comes from. See [Grok Bot vs OpenClaw](https://www.grokbotwiki.com/guides/grok-bot-vs-openclaw).

### What does Grok Bot cost?

There is no standalone price. Since October 12, 2026, new customers get it with The X Subscription's Premium plan at $30 a month, Super at $100 or Ultra at $200, or team seats at the same prices; SpaceXSI's Free and $8 Plus plans do not include it. Existing Cursor plans (Pro from $20 a month, Teams from $40 a seat), linked SuperGrok and X Premium+ subscriptions, and self-serve Grok Business seats keep working for people who already have them. See [our plan and pricing guide](https://www.grokbotwiki.com/guides/grok-bot-which-plan).

### Can I use Grok Bot inside the Grok app or my Tesla?

On the older plans, only with SuperGrok. A Cursor staff member said on October 11 that the Bots section inside the main Grok app is currently available only with a SuperGrok subscription; a Cursor plan does not unlock it, so the Grok app and Grok in a Tesla show an upgrade screen instead of your Bots. Cursor-plan users work in the separate Grok Bot apps. Staff suggested voice chat in the Grok Bot phone app over the car's Bluetooth as a workaround. x.ai/pricing says The X Subscription's shared pool covers Bot within Grok; we have not confirmed what the Grok app shows on those plans.

### Who makes Grok Bot: xAI, SpaceXAI or SpaceXSI?

All three names refer to the same company. SpaceX announced on February 2, 2026 that it had acquired xAI, which later traded as SpaceXAI. In early October Elon Musk said it would be renamed SpaceXSI, and by October 11 x.ai's page titles, articles and X handle (@SpaceXSI) used the new name; the site footer still names the legal entity SpaceXAI LLC. Cursor, whose cloud and accounts Grok Bot uses, became part of the company on August 14, 2026, according to its own news post.

## Sources

- [Grok Bot docs: Shared Bots (the docs' name for Team Bots)](https://docs.x.ai/grok-bot/shared-bots)
- [Grok Bot changelog: 0.77.0, Permissions, Vault payments and question cards (October 26)](https://x.ai/changelog/bot#v0.77.0)
- [Grok Bot changelog: 0.78.1, shopping cards and subscription templates (October 27)](https://x.ai/changelog/bot#v0.78.1)
- [SpaceXSI: Introducing Grok Bot (August 11, 2026)](https://x.ai/news/introducing-grok-bot)
- [SpaceXSI: Introducing The X Subscription (October 12, 2026)](https://x.ai/news/x-subscription)
- [x.ai pricing: The X Subscription plans](https://x.ai/pricing)
- [SpaceXSI: Grok Bot is now included with more plans (August 26, 2026)](https://x.ai/news/grok-bot-more-plans)
- [SpaceXSI news: xAI joins SpaceX, Grok Bot announcements](https://x.ai/news)
- [SpaceXSI: using Grok Bot to scale customer support (Cursor joined August 14)](https://x.ai/news/grok-bot-customer-support)
- [Grok Bot product page](https://x.ai/bot)
- [Grok Bot changelog](https://x.ai/changelog/bot)
- [Grok Bot overview](https://docs.x.ai/grok-bot/overview)
- [Billing and access FAQ](https://docs.x.ai/grok-bot/faq)
- [Cursor plans and billing for Grok Bot](https://cursor.com/help/grok-bot/plans)
- [Cursor pricing](https://cursor.com/pricing)
- [Grok chatbot on Wikipedia](https://en.wikipedia.org/wiki/Grok_(chatbot))
- [Grok Build on Wikipedia](https://en.wikipedia.org/wiki/Grok_Build)
- [SpaceXSI: Use Grok in OpenClaw](https://x.ai/news/grok-openclaw)
- [Grok Bot on the App Store](https://apps.apple.com/us/app/grok-bot/id6794501026)
- [Grok Bot on Google Play](https://play.google.com/store/apps/details?id=ai.x.grok.bot)
- [Tag @bot on X](https://docs.x.ai/grok-bot/tag-on-x)
- [Computer and apps: search and read X](https://docs.x.ai/grok-bot/computer-and-apps)
- [Cursor help: link SuperGrok or a Grok Business seat](https://cursor.com/help/grok-bot/supergrok)
- [Cursor help: give your Bot an email address](https://cursor.com/help/grok-bot/agent-email)
- [Cursor help: store secrets securely (Vault)](https://cursor.com/help/grok-bot/secrets)
- [Forum: Cursor plan does not unlock Bots in the Grok app or a Tesla (staff reply, October 11)](https://forum.cursor.com/t/grok-bot-subscribed-with-cursor-how-to-access-in-grok-app/174183)

---

# How to use Grok Bot: install, first Bot, plugins, routines

> Step-by-step Grok Bot tutorial from the official docs: install and sign in, set up your first Bot, connect a plugin, run a checkable task, add a routine.

- Canonical page: https://www.grokbotwiki.com/guides/getting-started
- Sources checked: 2026-10-29
- Evidence: Steps from the official docs (docs.x.ai, Cursor's docs and help pages, checked October 11, 2026; Cursor's getting-started docs rechecked October 27); docs.x.ai, The X Subscription docs and Cursor help rechecked October 25, 2026 with the changelog through 0.75.5 · x.ai/pricing last read October 14, 2026 · not a recorded run by us · example briefs are original templates · approval expiry rechecked in Cursor's how-to help and the official approvals docs October 29, 2026. Suggested workflows have not been independently tested.
- Publisher: Grok Bot Wiki, an independent guide not affiliated with SpaceXSI, xAI or X.

## The short version

To start using Grok Bot, install the desktop app from x.ai/bot, sign in with the account that holds an eligible plan, rename the first Bot setup creates and give it one job, then ask for one small task you can check. Connect a plugin only when a task needs it, set approvals, and add a routine last.

Each step below follows the official documentation from docs.x.ai and Cursor's docs and help pages, checked on October 11, 2026. Where the two disagree, we say so. We have not recorded our own run of these steps; the example briefs are original templates you should adapt.

| Step | Where in the app | Done when |
| --- | --- | --- |
| 1. Install and sign in | x.ai/bot → Download, then Sign in | The browser confirms sign-in and the app shows your plan |
| 2. Set up your first Bot | Click the Bot's name at the top of its chat, or New chat (+) → Create new Bot | The Bot has a short name and you have told it one job |
| 3. Give it a bounded task | The chat composer | You can check the result against the source |
| 4. Connect a plugin or sign in | Connect Apps in the sidebar, or the Bot's computer | The plugin shows as installed and authorized |
| 5. Set approvals | Approval cards, and Settings → General → Auto-review | Sends, purchases and deletes stop for you |
| 6. Save a skill, then a routine | Ask the Bot; manage under the Bot's routines | A test run produced the result you expected |
| 7. Watch usage | Settings → Usage & Billing | You know your weekly usage and on-demand setting |

Sources: https://docs.x.ai/grok-bot/get-started, https://cursor.com/help/grok-bot/onboarding

## Before you begin

You need an eligible plan. Since October 12, 2026, new customers buy The X Subscription, where Grok Bot is included on Premium ($30 a month), Super and Ultra and on team seats, but not on Free or Plus. Existing plans still work: any paid individual Cursor plan, Cursor Teams, an individual SuperGrok, SuperGrok Plus, SuperGrok Heavy or X Premium+ subscription linked to your Cursor account, or an assigned seat on a self-serve Grok Business plan. Our [plan and pricing guide](https://www.grokbotwiki.com/guides/grok-bot-which-plan) compares them and explains switching.

Grok Bot requires cloud data storage. The getting-started page says accounts using Legacy Privacy Mode must move to a supported Cursor data setting before Grok Bot can start; on a team, an administrator changes it.

Sources: https://docs.x.ai/grok-bot/get-started, https://x.ai/news/x-subscription, https://x.ai/pricing, https://docs.x.ai/x-subscription/grok-bot, https://cursor.com/help/grok-bot/plans, https://cursor.com/help/grok-bot/supergrok

## 1. Install the app and sign in

The desktop app runs on macOS (Apple silicon and Intel), Windows and Linux (x64 and Arm64). Linux builds and the other platforms are under More downloads on x.ai/bot and on Cursor's download page; Cursor's docs add that the installer is also on the Grok Bot page of the Cursor dashboard. Our [platforms guide](https://www.grokbotwiki.com/guides/grok-bot-platforms) shows how to tell which build you need. There is no separate Grok Bot login. SpaceXSI's X Subscription docs say Grok Bot uses the shared xAI sign-in path, which may show Grok or xAI branding, and that signing in does not link or combine your X, Grok or Cursor accounts or switch your plan.

1. Download the app for your computer from x.ai/bot and install it. On a Mac, drag Grok Bot to Applications; on Windows, run the installer.
2. Open Grok Bot and choose Sign in, then finish authentication in the browser window that opens. If your organization uses single sign-on, complete that sign-in.
3. Return to Grok Bot after the browser confirms the sign-in.
4. If your access comes from SuperGrok or X Premium+, first check that you signed in with the Cursor account that should keep it, because a link is permanent. Then choose Link Grok Account: Cursor's help says the access screen opens Get Started with Grok Bot in your browser, and X Premium+ links through the same button by signing in to Grok with that X account.
5. If your company assigned you a seat on a self-serve Grok Business plan, there is nothing to buy or link: sign out, sign back in, and choose Sign in with Grok with the Grok account that holds the seat.
6. Click through the short introduction. The docs say it asks which tools you use to shape suggestions; the answers do not connect anything by themselves.

Sources: https://docs.x.ai/grok-bot/get-started, https://cursor.com/help/grok-bot/onboarding, https://x.ai/bot, https://cursor.com/help/grok-bot/supergrok, https://cursor.com/docs/grok-bot/get-started, https://docs.x.ai/x-subscription/grok-bot-sign-in

## 2. Set up your first Bot

The official sources describe this step differently. Cursor's onboarding help and Cursor's own getting-started docs say Grok Bot sets up your first Bot, named Grok Bot, and opens a chat with it, which matches the 0.51.0 changelog entry (September 14): setup now creates your first Bot for you. The docs.x.ai getting-started page, updated October 9, still describes choosing a suggested teammate from Meet a future teammate, or Create your own. Use whichever your app shows.

Either way, give the Bot a short name, then use your first message to tell it its one job, which sources to use and when to ask for approval, and ask it to remember that. Rename it, or add a label for its job, by clicking its name at the top of the chat. Put the job in chat rather than relying on a settings field: Cursor staff said on October 5 and 9 that the redesigned desktop details pane no longer shows a Bot's instructions, and there is no desktop editor for them yet. The docs say focused Bots build more useful context than one catch-all Bot. Add more later from New chat (the + button) → Create new Bot when the work splits into distinct roles. Every Bot on your account shares one cloud computer and its logins, so a separate Bot is a separate role, not a separate security boundary; see [the shared-computer guide](https://www.grokbotwiki.com/guides/grok-bot-shared-computer).

Sources: https://cursor.com/help/grok-bot/onboarding, https://cursor.com/docs/grok-bot/get-started, https://x.ai/changelog/bot, https://docs.x.ai/grok-bot/get-started, https://docs.x.ai/grok-bot/faq, https://forum.cursor.com/t/grok-bot-macos-unable-to-see-or-edit-bot-instructions-or-skills-on-desktop/173803

## 3. Give it a first task you can check

Start with a short task that has a clear result and changes nothing outside the chat. The docs say a strong request names the outcome, the sources, the constraints, the deliverable and a review point. Attach a document you already understand, such as meeting notes, so you can judge the answer without learning a new system first. Since 0.71.2 (October 14), one message can carry up to 20 attachments with a 200 MB total, and on 0.70.2 or later files can be up to 250 MB and videos up to 1 GB; the docs' Files and results page still gives the older limits of six attachments, 25 MB per file and 200 MB per video.

Compare the result against the source: one ordinary item, one ambiguous item, and one commitment with no deadline. Then state the lasting preference explicitly, for example the report format you want next time. The brief below is our template; the practice pack on this page has fictional notes and an answer key for it. Our guide to [writing a workflow brief](https://www.grokbotwiki.com/guides/write-a-workflow-brief) goes further.

Editorial template (replace placeholders and review access before running):

```text
Use the attached [document name/version] to create an action register. Return a table with action, named owner, explicit deadline, source passage, and uncertainty. Include only commitments supported by the document. Mark missing owners or dates as unspecified; do not infer them. Then list ambiguous statements that need a human decision. Preserve the original file. Do not contact anyone or create tasks in another app. Finish with the number of commitments found and anything you could not read.
```

Sources: https://docs.x.ai/grok-bot/get-started, https://cursor.com/help/grok-bot/onboarding, https://x.ai/changelog/bot, https://docs.x.ai/grok-bot/files-and-results

## 4. Connect a plugin, or sign in on the computer

When a task needs Gmail, Google Calendar, Slack, Notion or another supported service, connect a plugin. Since version 0.67.0 (October 2) the in-app Marketplace is called Connect Apps; follow a Connect card in chat or open it from the sidebar (on the phone, tap your avatar), add the plugin, and finish the provider's sign-in in your browser. Added means installed, not signed in: check that it is authorized. In chat, type @ to attach a connector to a task. Our [plugins, connectors and MCP guide](https://www.grokbotwiki.com/guides/grok-bot-plugins-mcp) covers the details.

For a website without a plugin, the Bot asks you to take over its computer: open Agent Computer from the conversation, choose the takeover control, sign in yourself, and hand control back. The browser session then stays on your shared computer for every Bot. Avoid pasting passwords or codes into chat, and until Cursor confirms a fix for the October 5 snapshot report (none was posted by October 11), type passwords on the screen yourself rather than through the in-chat form.

Since 0.75.5 (October 23), on Grok Bot 0.75.2 or later, you can instead save logins, cards and contact info under Settings → Vault, on desktop or the phone. Cursor's secrets help says the Bot fills them in to sign in or check out without seeing a saved password, card number or security code, that everything in Vault is available to every Bot on your account, and that Vault is not supported on Shared Bots (formerly Team Bots). Cursor's getting-started docs, checked October 27, now describe the same order: when a Bot reaches an app that needs a sign-in it uses a login saved in Vault or a connected password manager, or asks you with a Secure Form, and hands you the computer for single sign-on, a passkey or another step a form cannot handle.

Sources: https://docs.x.ai/grok-bot/computer-and-apps, https://cursor.com/help/grok-bot/connect-apps, https://x.ai/changelog/bot, https://docs.x.ai/grok-bot/get-started, https://forum.cursor.com/t/grok-bot-browser-snapshot-shows-a-password-filled-by-the-secure-form-requestuserform-in-plain-text/173748, https://cursor.com/help/grok-bot/secrets

## 5. Set approvals before the Bot can change things

When an action needs approval, the chat shows an approval card with the proposed operation. Allow once lets that action continue, Always allow can save a matching rule, and Deny blocks it. The onboarding help suggests Allow once while you learn how a Bot handles a workflow.

With Auto Review on, Grok Bot checks tool calls and computer actions before they run. Add rules in Settings → General → Auto-review: Ask first rules always stop matching actions for you, and if an Ask first rule and an Allow automatically rule both match, Ask first wins. Since 0.68.0 Settings calls saved rules Custom Rules. Running commands on the computer in front of you is a separate setting whose default is Ask every time. Our [permission boundaries guide](https://www.grokbotwiki.com/guides/permission-boundaries) has a worksheet, and [Is Grok Bot safe?](https://www.grokbotwiki.com/guides/is-grok-bot-safe) covers the rest of the security model.

Two changes in 0.75.5 (October 23) affect this step. An email or Slack message you ask a Bot to send now goes out once Auto-review allows it, while sends from routines and other turns you did not start still wait as drafts; Cursor's email help adds that instructions inside an email the Bot received never count as your permission to send. And after you deny an approval card, the Bot stops and does not try that action again until you send another message.

- [ ] Sending email or messages, purchases, deletions and publishing are behind Ask first rules.
- [ ] Email and Slack drafts stay on. Since 0.75.5 a send you ask for in chat can go out once Auto-review allows it, so keep an Ask first rule for sending if you want to review every message.
- [ ] Execution on Local Computer is Ask every time or Never allow.
- [ ] Nothing signed into the shared computer would be a problem if any of your Bots used it.

Sources: https://docs.x.ai/grok-bot/approvals-security-and-privacy, https://cursor.com/help/grok-bot/onboarding, https://x.ai/changelog/bot, https://cursor.com/help/grok-bot/agent-email

## 6. Save a skill, then add a routine

Once a task produces the result you expect, ask the Bot to save the method as a skill: when to use it, the inputs and access it needs, the steps, how to check the result, what to return, and what needs approval. Private skills are one library shared by all your Bots; type / in the composer to use one. Where Teach a task is available, you can instead record up to ten minutes of your own browser work.

Only then ask the owning Bot for a routine, with the schedule, time zone, input, expected result and what to do when a source is missing. A test run performs real work, so use safe inputs. A new routine waits for its next scheduled time rather than running when created. An approval requested by a routine, a trigger or another Bot expires and the action does not run after about 30 minutes; the official docs and Cursor's how-to help both said so when we checked on October 29. Turn on notifications for Bots that run routines, or choose Always allow for actions you trust. Cursor's routines help warns that an hourly schedule, a short interval or a Slack trigger on a busy channel can use a week of usage in a day. It also sets hourly limits: up to 300 runs an hour across your routines (0.75.5 raised this from 100) and up to 200 for any one routine; a run past either limit fails with Automation run rate limit exceeded. Our guides to [skills and routines](https://www.grokbotwiki.com/guides/skills-vs-routines) and [routines that do not run](https://www.grokbotwiki.com/guides/grok-bot-routines-not-running) go deeper.

Editorial template (replace placeholders and review access before running):

```text
Every weekday at 8:00 AM in [time zone], run the [skill name] skill on [source]. Post a short result in this conversation with source links. Do not send, edit or delete anything outside this chat. If the source is unavailable, empty or unchanged since the last run, say so in one line and do not reuse an earlier result.
```

Sources: https://docs.x.ai/grok-bot/skills-routines-and-automations, https://cursor.com/help/grok-bot/routines, https://cursor.com/help/grok-bot/how-to, https://docs.x.ai/grok-bot/approvals-security-and-privacy, https://x.ai/changelog/bot

## 7. Keep an eye on usage

Every plan includes weekly usage, measured in agent steps and tokens rather than messages. Settings → Usage & Billing shows your included usage and, since 0.63.0, when it resets. When it runs out, work stops unless on-demand usage is enabled, and the On-demand monthly limit is not a hard stop for a run already in progress. Start one Bot on one task, read the meter, and add Bots and routines from there. On The X Subscription the weekly pool is shared with your Grok and Cursor use, extra use is paid from prepaid top-ups, and usage is shown under Usage at grok.com/dashboard. See [why the weekly limit runs out](https://www.grokbotwiki.com/guides/grok-bot-weekly-usage-limit).

Sources: https://cursor.com/help/grok-bot/plans, https://x.ai/changelog/bot, https://docs.x.ai/grok-bot/settings-and-notifications, https://docs.x.ai/x-subscription/usage-limits, https://docs.x.ai/x-subscription/grok-bot

## Quick answers

### Do I need to keep my computer on for Grok Bot to work?

No. Bots work on a persistent cloud computer, and the FAQ says closing the app, laptop or phone does not stop a background turn or a routine. The desktop and mobile apps are clients for that computer.

### Why does my account already have a Bot called Grok Bot?

Setup creates one. Cursor's onboarding help says Grok Bot sets up your first Bot, named Grok Bot, and opens a chat with it, and the changelog for 0.51.0 (September 14) says setup now creates your first Bot for you. Rename it by clicking its name at the top of the chat and give it one job, or add a new Bot from New chat (the + button) → Create new Bot.

### Can I set up Grok Bot on my phone?

Yes, on iPhone, iPad and Android, with the same Cursor account. You can message Bots, create Bots, install plugins and approve drafts from a phone, but editing a routine's schedule or instructions and running a test need the desktop app. See [our platforms guide](https://www.grokbotwiki.com/guides/grok-bot-platforms).

### What should my first task be?

Something small with an answer you can check, that changes nothing outside the chat. The official docs suggest attaching a document and asking for a five-bullet summary that lists every date, decision and open question with a citation. The practice pack on this page gives you notes and an answer key for the same idea.

## Sources

- [Get started](https://docs.x.ai/grok-bot/get-started)
- [Grok Bot overview](https://docs.x.ai/grok-bot/overview)
- [Computer and apps](https://docs.x.ai/grok-bot/computer-and-apps)
- [Approvals, security and privacy](https://docs.x.ai/grok-bot/approvals-security-and-privacy)
- [Skills and routines](https://docs.x.ai/grok-bot/skills-routines-and-automations)
- [Grok Bot for Mobile](https://docs.x.ai/grok-bot/mobile)
- [Grok Bot FAQ](https://docs.x.ai/grok-bot/faq)
- [Settings: usage and billing](https://docs.x.ai/grok-bot/settings-and-notifications)
- [Files and results: attachments](https://docs.x.ai/grok-bot/files-and-results)
- [Cursor docs: get started with Grok Bot](https://cursor.com/docs/grok-bot/get-started)
- [Cursor help: onboarding](https://cursor.com/help/grok-bot/onboarding)
- [Cursor help: link SuperGrok or a Grok Business seat](https://cursor.com/help/grok-bot/supergrok)
- [Cursor help: how-tos (approvals, notifications)](https://cursor.com/help/grok-bot/how-to)
- [Cursor help: connect apps](https://cursor.com/help/grok-bot/connect-apps)
- [Cursor help: routines](https://cursor.com/help/grok-bot/routines)
- [Cursor help: plans and billing](https://cursor.com/help/grok-bot/plans)
- [Cursor help: store secrets securely (Vault)](https://cursor.com/help/grok-bot/secrets)
- [Cursor help: give your Bot an email address (who can send)](https://cursor.com/help/grok-bot/agent-email)
- [SpaceXSI: Introducing The X Subscription (October 12, 2026)](https://x.ai/news/x-subscription)
- [x.ai pricing: The X Subscription plans](https://x.ai/pricing)
- [The X Subscription docs: Grok Bot on The X Subscription](https://docs.x.ai/x-subscription/grok-bot)
- [The X Subscription docs: Grok Bot sign-in](https://docs.x.ai/x-subscription/grok-bot-sign-in)
- [The X Subscription docs: usage limits](https://docs.x.ai/x-subscription/usage-limits)
- [Grok Bot changelog](https://x.ai/changelog/bot)
- [Grok Bot downloads (x.ai/bot)](https://x.ai/bot)
- [Forum: password filled by the Secure Form shown in a page snapshot (staff reply, October 5)](https://forum.cursor.com/t/grok-bot-browser-snapshot-shows-a-password-filled-by-the-secure-form-requestuserform-in-plain-text/173748)
- [Forum: desktop details pane no longer shows a Bot's instructions (staff replies, October 5 and 9)](https://forum.cursor.com/t/grok-bot-macos-unable-to-see-or-edit-bot-instructions-or-skills-on-desktop/173803)

---

# Grok Bot pricing (October 2026): X Subscription $30–$200 and older plans

> Grok Bot now comes with The X Subscription's Premium ($30), Super ($100) and Ultra ($200), not Free or Plus. Older Cursor and SuperGrok plans, and what to do.

- Canonical page: https://www.grokbotwiki.com/guides/grok-bot-which-plan
- Sources checked: 2026-10-29
- Evidence: x.ai/bot pricing panel and FAQ read in a browser October 29, 2026, unchanged since October 25 · Grok Bot changelog entry 0.78.1 (October 27) read October 29 · SpaceXSI's new referral program docs and Cursor's plans help read October 28 · Cursor's team pricing docs checked October 27 · cursor.com/pricing, cursor.com/docs/grok-bot and docs.x.ai/grok-bot rechecked October 26, 2026, no change found · SpaceXSI's X Subscription docs and Cursor's legacy-plan and team pricing pages rechecked October 25, 2026 · The X Subscription announcement and x.ai/pricing last read October 14, 2026 (x.ai/pricing also returned a Cloudflare block October 26) · Cursor staff forum replies attributed · not a purchase test. Suggested workflows have not been independently tested.
- Publisher: Grok Bot Wiki, an independent guide not affiliated with SpaceXSI, xAI or X.

## The short answer

Grok Bot still has no standalone price, but how you buy it changed on October 12, 2026. SpaceXSI's announcement introduced The X Subscription, one plan for Grok, Grok Bot, Cursor and X Premium, available to new customers from that day and rolling out globally over the following days. Grok Bot is included on Premium ($30 a month), Super ($100) and Ultra ($200), and on team seats at the same prices. The Free and Plus ($8) plans do not include it.

If you already pay for Cursor Pro, Pro+, Ultra or Teams, a linked SuperGrok or X Premium+ subscription, or have a self-serve Grok Business seat, nothing changes unless you choose to switch. SpaceXSI says those plans keep their price and features, and switching gives a prorated refund for the old plan. By October 25, x.ai/bot and Cursor's Grok Bot plan help both showed The X Subscription, and Cursor now calls its older plans legacy plans, but the Grok Bot pages on docs.x.ai still describe only the older plans, so expect mixed information for a while.

| Pick | Price (October 26, 2026) | Pick it if |
| --- | --- | --- |
| X Subscription Premium | $30 a month, or $300 a year | You are new and want Grok Bot; SpaceXSI recommends it for new AI users |
| X Subscription Super | $100 a month, or $1,000 a year | You use agents daily; 15x Plus usage (x.ai/bot: 3.5x Premium) and priority model access at peak times |
| X Subscription Ultra | $200 a month, or $2,000 a year | You run many Bots all week; 50x Plus usage (x.ai/bot: 12x Premium) |
| X Subscription Teams | $30, $100 or $200 per seat a month | A team needs it; seat tiers can be mixed |
| Keep your existing plan | Unchanged | You already have Cursor, SuperGrok, X Premium+ or a Grok Business seat and it covers your use |

Sources: https://x.ai/news/x-subscription, https://x.ai/pricing, https://docs.x.ai/x-subscription/pricing, https://docs.x.ai/x-subscription/grok-bot, https://x.ai/bot, https://cursor.com/help/grok-bot/plans

## The X Subscription plans

SpaceXSI's announcement describes paid plans with one pool of Grok model usage shared across Grok (the apps and the Grok tab on X) and Cursor. x.ai/pricing says that within Grok the pool covers Chat, Imagine, Voice and Bot, that it refreshes weekly, and that beyond it you buy top-ups or wait for the refresh. The usage column below is x.ai's own wording, relative to Plus, which cursor.com/pricing and SpaceXSI's pricing docs still used on October 25; no absolute allowance is published. The x.ai/bot pricing panel words it differently, relative to Premium: Super has 3.5x Premium usage and Ultra 12x. By the Plus figures those ratios would be 3.75x and 12.5x, and neither page explains the difference. Annual prices come from SpaceXSI's X Subscription pricing docs. Prices exclude taxes.

The announcement says each plan includes at least twice as much coding usage with SpaceXSI models as the comparable Cursor plan, and that Premium bundles the benefits of SuperGrok, Cursor Pro and X Premium+, which it puts at $90 a month combined. Third-party models in Cursor, such as Claude or GPT, are not in the pool: the docs say they are billed at API list prices from the first use, from prepaid credit. Paid plans also include Grok API access, billed separately at model rates.

| Plan | Monthly | Billed annually | Usage (x.ai's wording) | Grok Bot |
| --- | --- | --- | --- | --- |
| Free | $0 | $0 | Limited | Not included |
| Plus | $8 | $80 a year | Base | Not included |
| Premium | $30 | $300 a year | 4x Plus | Included |
| Super | $100 | $1,000 a year | 15x Plus | Included |
| Ultra | $200 | $2,000 a year | 50x Plus | Included |
| Teams | $30, $100 or $200 per seat | Not stated | 4x to 50x Plus, by seat | Included |
| Enterprise | Custom | Custom | Pooled | Included, with access, network and audit controls for Grok Bot |

Sources: https://x.ai/news/x-subscription, https://x.ai/pricing, https://docs.x.ai/x-subscription/pricing, https://docs.x.ai/x-subscription/usage-limits, https://cursor.com/pricing, https://x.ai/bot

## If you already pay for Cursor, SuperGrok or X Premium

You do not have to do anything. SpaceXSI's docs say switching is optional and your current plan continues unless you change or cancel it; existing Cursor customers can still move between their current Cursor plans, and existing teams can still add seats, without switching. The announcement adds that limited-time switching offers appear in account billing settings.

If you switch, it is permanent and support cannot undo it. The Cursor, SuperGrok and paid X Premium subscriptions you combine are cancelled at checkout with an automatic prorated refund, and a new billing cycle starts that day. Grok Bot usage then comes from the new shared weekly pool, and you manage usage at grok.com/dashboard instead of cursor.com/dashboard. If you linked SuperGrok to more than one Cursor account, you pick a primary account and the rest are combined into it.

Two cases need care. A Cursor plan bought through Apple's App Store is not cancelled when you switch: SpaceXSI says to cancel it yourself in iPhone or iPad Settings, or Apple keeps billing you, and it must be switched before its tier can be changed. Grok or X Premium bought through Google Play may still be set to renew; check Google Play afterwards. If you have X Premium+, choose Premium or higher to keep its X benefits.

| If you have… | What the docs say | Our suggestion |
| --- | --- | --- |
| Cursor Pro, Pro+ or Ultra on the web | Continues; switching cancels it with a prorated refund | Stay until you have compared a week of usage; switch if you also want Grok or X Premium+ |
| Cursor bought in the iPhone app | Not cancelled or refunded by switching | If you switch, cancel the Apple subscription the same day |
| A linked SuperGrok, Plus or Heavy | Continues; after switching, Grok Bot uses the shared pool | Pick your primary Cursor account before switching |
| X Premium or X Premium+ | Can switch; X Premium is cancelled and refunded | Premium or higher keeps X Premium+ benefits and adds Grok Bot |
| A Cursor or Grok team | An owner or admin starts the switch at cursor.com/unify/team | Decide each member's seat tier first |
| Grok Enterprise or a negotiated contract | Cannot switch yet | Ask your account team |

Sources: https://docs.x.ai/x-subscription/do-i-have-to-switch, https://docs.x.ai/x-subscription/overview, https://docs.x.ai/x-subscription/grok-bot, https://docs.x.ai/x-subscription/eligibility, https://docs.x.ai/x-subscription/app-store, https://x.ai/news/x-subscription

## Where the official pages disagree

On October 14, two days after the launch, x.ai/bot and most of Cursor's Grok Bot help still listed only the older plans. By October 25 most pages had caught up. The x.ai/bot pricing panel shows Premium at $30, Super at $100 and Ultra at $200 a month, and its FAQ says Grok Bot is included with Premium, Super, Ultra, Teams and Enterprise. Cursor's help pages on plans, SuperGrok linking and mobile purchase, and its team pricing page, now cover The X Subscription first and call the older plans legacy.

Two gaps remain. The Grok Bot overview, FAQ, getting-started and mobile pages on docs.x.ai, and Cursor's own Grok Bot docs, still list only Cursor plans, SuperGrok links and Grok Business seats. And the usage multiples differ: cursor.com/pricing and SpaceXSI's pricing docs give 4x, 15x and 50x Plus, x.ai/bot gives Super 3.5x and Ultra 12x Premium usage, and Cursor's team pricing docs, checked October 27, put a Super seat's weekly pool at 3.75x and an Ultra seat's at 12.5x Premium. We treat the X Subscription pages as current for new purchases and the older pages as accurate for people who keep an existing plan, which SpaceXSI says continues. One smaller difference: cursor.com/pricing says Plus includes Grok models only, while the announcement says third-party models in Cursor are available on Premium and above. The rollout is gradual, so your account may not offer The X Subscription yet.

Sources: https://x.ai/bot, https://x.ai/pricing, https://x.ai/news/x-subscription, https://cursor.com/pricing, https://cursor.com/help/grok-bot/plans, https://cursor.com/help/grok-bot/supergrok, https://cursor.com/help/grok-bot/mobile-purchase, https://docs.x.ai/grok-bot/faq, https://docs.x.ai/grok-bot/get-started, https://docs.x.ai/x-subscription/pricing, https://cursor.com/docs/account/teams/pricing, https://cursor.com/docs/grok-bot

## Existing plans: every price

These are the plans that included Grok Bot before October 12. They continue for current subscribers. The Cursor and SuperGrok prices below are as we last saw them listed on cursor.com/pricing and x.ai/bot on October 12; on October 14 cursor.com/pricing showed only The X Subscription, and by October 25 x.ai/bot did too. Cursor's legacy plans page still lists the monthly Pro, Pro+, Ultra and Teams prices, and pairs each with its closest X Subscription tier: Pro with Premium, Pro+ with Super, Ultra with Ultra, a Teams Standard seat with a Premium seat and a Teams Premium seat with a Super seat. The usage column quotes Cursor's billing page, which publishes relative tiers rather than numbers.

| Plan | Monthly | Billed yearly | Grok Bot usage (Cursor's wording) |
| --- | --- | --- | --- |
| Cursor Pro | $20 | $16 a month | Weekly usage, below Pro+; same tier as SuperGrok |
| Cursor Pro+ | $60 | $48 a month | Generous weekly usage, below Ultra; same tier as SuperGrok Plus |
| Cursor Ultra | $200 | $160 a month | Highest weekly usage; same tier as SuperGrok Heavy |
| Cursor Teams Standard | $40 per seat | $32 per seat a month | Follows the Teams plan allowance |
| Cursor Teams Premium | $120 per seat | $96 per seat a month | Follows the seat; a Premium seat has 5x a Standard seat's usage |
| Cursor Enterprise | Custom | Custom | Managed by your admin |
| SuperGrok, linked | $30 | Not listed on x.ai/bot | Linked usage, below Plus |
| SuperGrok Plus, linked | $100 | Not listed on x.ai/bot | Generous linked usage, below Heavy |
| SuperGrok Heavy, linked | $300 | Not listed on x.ai/bot | Highest linked usage |
| X Premium+, linked | Billed by X; not listed on x.ai/bot | Not listed | Linked usage, below SuperGrok Plus; same tier as Pro |
| Grok Business seat (self-serve) | Set by your company | Set by your company | Matches the seat's license: SuperGrok or SuperGrok Heavy |
| Grok Enterprise | n/a | n/a | Ask your account manager |
| SuperGrok Lite | n/a | n/a | Not included |

Sources: https://cursor.com/pricing, https://x.ai/bot, https://cursor.com/help/grok-bot/plans, https://cursor.com/docs/account/teams/pricing, https://cursor.com/help/grok-bot/supergrok, https://cursor.com/docs/account/pricing/legacy-cursor-plans

## Decide by what you already pay for

Most people already have one of these subscriptions. On the existing plans, Grok Bot usage is metered on your Cursor account; a SuperGrok or X Premium+ link grants usage to that Cursor account while the subscription stays active. On The X Subscription, usage sits on a workspace managed at grok.com/dashboard.

| If you… | Pick | Why |
| --- | --- | --- |
| Pay for nothing yet | X Subscription Premium, $30 a month | The cheapest new plan with Grok Bot; Free and Plus do not include it |
| Already pay for Cursor Pro, Pro+ or Ultra | Keep it, or switch if you also want Grok and X Premium+ | Grok Bot stays included, and a SuperGrok link on top adds no usage |
| Already pay for individual SuperGrok, Plus or Heavy | Keep the link, or switch to one plan | The link grants Grok Bot usage without a Cursor plan; it is permanent |
| Have X Premium+ | Link it, or switch to Premium or higher | Cursor lists its linked usage below SuperGrok Plus; Premium keeps X Premium+ benefits |
| Have SuperGrok Lite or X Subscription Plus | Move to a plan that includes Grok Bot | Neither includes Grok Bot |
| Have a seat on a self-serve Grok Business plan | Sign in with Grok using that account | The seat includes Grok Bot; there is nothing to buy or link |
| Are on Grok Enterprise | Ask your account manager | Cursor's help says Grok Enterprise does not qualify through a link, and it cannot switch yet |
| Want Bots inside the Grok app or a Tesla | SuperGrok, or check Premium first | Cursor staff, October 11: a Cursor plan does not unlock the Bots section in the Grok app |
| Work on a team | X Subscription team seats, or keep Cursor Teams | Seats from $30; existing Cursor Teams seats continue |

Sources: https://docs.x.ai/x-subscription/grok-bot, https://x.ai/pricing, https://cursor.com/help/grok-bot/plans, https://cursor.com/help/grok-bot/supergrok, https://forum.cursor.com/t/grok-bot-subscribed-with-cursor-how-to-access-in-grok-app/174183, https://docs.x.ai/x-subscription/eligibility, https://docs.x.ai/x-subscription/team-plans

## Decide by how much you will use it

On The X Subscription, the tiers differ only in how much shared usage they include: Premium has 4x the usage of Plus, Super 15x and Ultra 50x, according to x.ai/pricing and cursor.com/pricing, while x.ai/bot puts Super at 3.5x and Ultra at 12x Premium usage. Remember that the same pool also pays for your Grok chat and Cursor coding, so a heavy Cursor week leaves less for your Bots. SpaceXSI recommends Premium for new AI users, Super for daily agent users and Ultra for power users.

The light, regular and heavy grouping below is our editorial suggestion, not SpaceXSI's or Cursor's, and the columns are not official equivalents: no source compares an X Subscription tier's Grok Bot allowance with an existing Cursor or SuperGrok tier. Cursor's legacy plans page pairs Pro with Premium, Pro+ with Super and Ultra with Ultra as the closest tiers, but it compares coding usage, saying each X Subscription plan includes at least twice as much coding usage with Cursor models, not Grok Bot allowances. Usage is measured in agent steps and tokens, not messages, so one long browser task can cost more than dozens of short replies.

| How you will use it | The X Subscription | Existing Cursor plan | Existing SuperGrok link |
| --- | --- | --- | --- |
| Light: one or two Bots, short tasks, a few routines | Premium, $30 a month | Pro, $20 a month | SuperGrok, $30 a month |
| Regular: several Bots or daily routines | Super, $100 a month | Pro+, $60 a month | SuperGrok Plus, $100 a month |
| Heavy: many Bots, long browser sessions, frequent routines | Ultra, $200 a month | Ultra, $200 a month | SuperGrok Heavy, $300 a month |

Sources: https://x.ai/pricing, https://docs.x.ai/x-subscription/usage-limits, https://cursor.com/help/grok-bot/plans, https://x.ai/bot, https://cursor.com/pricing, https://cursor.com/docs/account/pricing/legacy-cursor-plans

## Check which trial you are starting

The X Subscription's Free plan does not include Grok Bot, and the only Grok Bot trial its docs describe comes through a referral. A referral program page, new on SpaceXSI's docs by October 28, 2026, says a friend who opens your link, signs up and enters a credit card gets a two-week free trial of Premium and a reminder seven days before the first charge. To refer, you need a paid Premium, Super or Ultra plan on The X Subscription, to be based in the US, and to be at least seven days past checkout; Plus, Team, Cursor and SuperGrok plans cannot refer. The friend must be new to Grok and anywhere except China, and purchases through Apple or Google do not count. The referrer gets one usage reset per friend who becomes a paid subscriber, added seven days after the payment, valid for six months, removed if the payment is refunded, and with no cash value. The link is behind a gift icon in the Grok Bot apps or at grok.com/dashboard/referrals, and Cursor's plans help now points to the same program. Cursor's help still describes two older trials, without saying whether either is offered to new X Subscription accounts. The in-app offer changed too: the 0.78.1 changelog (October 27) says that where Grok Bot offered a free trial, it now offers Get Grok Bot with a unified plan and See Unified Plans.

The Grok Bot usage-credit trial is measured in agent steps and tokens, not days, though a seven-day window also applies; a long first task can use most of it at once, and used credit is not restored. It never becomes a paid plan. On a free account, Cancel Trial on the plan screen ends it immediately. An Apple introductory offer is different: it becomes a paid Apple subscription unless you cancel before it ends in Apple ID → Subscriptions. Cursor says Android has no in-app trial. Read the offer shown on your account before confirming it.

Sources: https://x.ai/changelog/bot#v0.78.1, https://x.ai/pricing, https://docs.x.ai/x-subscription/referral-program, https://cursor.com/help/grok-bot/plans, https://cursor.com/help/grok-bot/mobile-purchase

## Buying on iPhone or Android

If your account already includes Grok Bot, sign in to the mobile app with the same account and access carries over; Cursor says not to buy a second subscription through Apple or Google Play. Cursor's mobile help, which now lists Premium, Super and Ultra, including team seats, among the plans that carry over, says only monthly individual plans are sold in the app, and that yearly billing, Teams and Enterprise are bought on the web. Apple's US App Store listing has shown in-app prices of $25.99 for Pro, $77.99 for Pro+ and $259.99 for Ultra, above the web prices.

Store purchases are the awkward case for The X Subscription. SpaceXSI's docs say a Cursor plan billed by Apple is not cancelled or refunded when you switch on the web, so you could be billed twice until you cancel it in iPhone or iPad Settings. Grok, Grok Bot or X Premium bought through Apple is cancelled for you, with Apple deciding the refund; anything bought through Google Play should be checked in Google Play afterwards.

Sources: https://cursor.com/help/grok-bot/mobile-purchase, https://apps.apple.com/us/app/grok-bot/id6794501026, https://cursor.com/help/account-and-billing/on-demand-usage-for-mobile-subscriptions, https://docs.x.ai/x-subscription/app-store, https://docs.x.ai/x-subscription/grok-bot

## Cursor Ultra or SuperGrok Heavy?

This question is about the existing plans; do not confuse Cursor Ultra with the new X Subscription Ultra, which is also $200 a month. For Grok Bot, Cursor Ultra and SuperGrok Heavy are the same tier, as Cursor's billing page states. A Cursor staff member said on September 10 that both give the highest weekly Grok Bot quota with no difference in models, speed or priority, and another said on September 22 that there is no tier above Ultra and no published dollar figure for the weekly allowance.

The difference is everything else. Cursor Ultra also includes Ultra-level usage for the Cursor editor, Agent and Cloud Agents. Heavy is a SpaceXSI subscription with SuperGrok Heavy features in the Grok apps and no Cursor plan. Cursor Ultra was $200 a month, or $160 billed yearly, and Heavy $300, so for Grok Bot alone Ultra was the cheaper way to the top existing tier.

Sources: https://forum.cursor.com/t/supergrok-heavy-vs-cursor-individual-ultra/170888, https://forum.cursor.com/t/grok-bot-usage-too-low-even-on-cursor-ultra/172584, https://cursor.com/help/grok-bot/plans, https://x.ai/bot, https://x.ai/pricing

## Rules to know before you pay

On The X Subscription, one weekly pool per paid seat covers Grok, Grok Bot and Cursor; it is not a separate Grok Bot allowance. Beyond it, further use is Additional Usage paid from prepaid credit. SpaceXSI's docs describe four separate controls: the weekly pool, the prepaid balance, a monthly additional usage limit and Auto Top-up, which is off unless you turn it on. They call the monthly limit the way to put a hard stop on paid Additional Usage, and note that adding credit does not raise it. Spend alerts warn but do not stop usage.

On the existing plans, plans do not stack: on Pro+, linking SuperGrok Plus adds no usage, and both subscriptions keep billing on their own. A SuperGrok or X Premium+ link is permanent and cannot be moved to another Cursor account, so sign in with the right Cursor account first. After upgrading SuperGrok, allow up to 24 hours for weekly usage to move. After weekly usage runs out, work continues only with on-demand enabled, up to the On-demand monthly limit, which Cursor says a run already in progress can finish past.

Switching to The X Subscription is also permanent. Read the confirmation screen, which SpaceXSI says shows the tier, price, effective date and any refund.

- [ ] You know whether you are buying The X Subscription or keeping an existing plan.
- [ ] On The X Subscription, you picked Premium or higher; Free and Plus do not include Grok Bot.
- [ ] A monthly additional usage limit (or the existing plans' on-demand limit) is set, or extra usage is deliberately off, before any routine runs unattended.
- [ ] If you pay for Cursor through Apple and switch, you cancelled the Apple subscription.
- [ ] You are not buying a second subscription expecting more usage.

Sources: https://docs.x.ai/x-subscription/usage-limits, https://docs.x.ai/x-subscription/spending-caps, https://docs.x.ai/x-subscription/overview, https://cursor.com/help/grok-bot/plans, https://cursor.com/help/grok-bot/supergrok, https://docs.x.ai/grok-bot/faq

## Teams and Enterprise

The X Subscription sells team seats on Premium at $30, Super at $100 and Ultra at $200 per seat a month, which Cursor's team pricing docs describe as the same prices and weekly usage as the matching individual plans, while putting the Super pool at 3.75x and the Ultra pool at 12.5x Premium. Members can have different seat tiers, Plus is not available for teams, each paid seat has its own weekly pool, and the team shares one prepaid balance for Additional Usage. The same docs, checked October 27, add a $0 Free seat that any member or admin can hold: it has no team usage allowance, so that person's usage draws on their own personal plan, and it is assigned by email invite or the Seat menu, not an invite link. The announcement says these seats cost less than the older Cursor Teams seats while including 3x more coding usage, and adds SSO, admin controls, consolidated billing, usage analytics and SOC 2.

Existing Cursor Teams plans continue: Standard is $40 and Premium $120 per seat a month, Grok Bot is on by default for every member, and on-demand usage is on by default. Shared Bots (formerly Team Bots), one Bot shared by a team, are in public beta on Teams and Enterprise plans; see our [Shared Bots guide](https://www.grokbotwiki.com/guides/grok-bot-team-bots). On Enterprise, x.ai/pricing lists access, network and audit controls for Grok Bot and one pooled usage across Grok and Cursor. Cursor Enterprise customers without a Grok account can switch through their account team; other Enterprise accounts cannot switch yet.

Sources: https://docs.x.ai/x-subscription/pricing, https://docs.x.ai/x-subscription/team-plans, https://docs.x.ai/x-subscription/usage-limits, https://x.ai/news/x-subscription, https://x.ai/pricing, https://docs.x.ai/grok-bot/teams-and-enterprises, https://cursor.com/help/grok-bot/plans, https://cursor.com/docs/account/teams/pricing, https://x.ai/news/team-bots, https://x.ai/news/grok-bot-for-enterprise

## When each plan got Grok Bot

Grok Bot launched in beta on August 11, 2026. On August 26 SpaceXSI announced that Grok Bot was included with SuperGrok, Cursor Pro and all Cursor Teams plans. Enterprise availability was announced on September 3, and Shared Bots on September 28. On October 12 SpaceXSI introduced The X Subscription, which includes Grok Bot from Premium up, for new customers first and rolling out globally over the following days.

Sources: https://x.ai/news/introducing-grok-bot, https://x.ai/news/grok-bot-more-plans, https://x.ai/news/grok-bot-for-enterprise, https://x.ai/news/team-bots, https://x.ai/news/x-subscription

## If your account does not show access

On The X Subscription, check that your plan is Premium or higher; SpaceXSI's docs say Grok Bot is available as soon as you subscribe or switch to one of those plans. On an existing plan, check that you signed in with the Cursor account that holds the plan or the SuperGrok link. For a Grok Business seat, sign out and sign back in with Sign in with Grok; since 0.75.5, if your seat does not cover Grok Bot yet, the usage limit message says to ask your Grok Business admin to connect your team. Grok Bot needs cloud storage, and accounts using Legacy Privacy Mode must move to a supported data setting first. Our [Windows sign-in guide](https://www.grokbotwiki.com/guides/grok-bot-sign-in-error-windows) covers sign-in loops, and the [platforms guide](https://www.grokbotwiki.com/guides/grok-bot-platforms) lists every download.

Sources: https://docs.x.ai/x-subscription/grok-bot, https://docs.x.ai/grok-bot/get-started, https://docs.x.ai/grok-bot/faq, https://cursor.com/help/grok-bot/plans, https://cursor.com/help/grok-bot/supergrok, https://x.ai/changelog/bot

## Changes to this page

October 28, 2026: added SpaceXSI's new Grok Bot referral program (a two-week Premium trial for the friend, a usage reset for a US-based Premium, Super or Ultra referrer) to the trial section and FAQ. Reread x.ai/bot in a browser: unchanged. We did not refer anyone or buy a plan.

October 27, 2026: reread x.ai/bot in a browser (unchanged: Premium $30, Super $100 at 3.5x Premium usage, Ultra $200 at 12x; Grok Bot included with Premium, Super, Ultra, Teams and Enterprise) and Cursor's team pricing docs, which now put Super and Ultra team seats at 3.75x and 12.5x Premium usage and describe a $0 Free seat with no team allowance.

October 25, 2026: x.ai/bot now shows The X Subscription's Premium, Super and Ultra and says Grok Bot is included with Premium, Super, Ultra, Teams and Enterprise, so we removed our note that it still listed the older plans. Cursor's plans, SuperGrok and mobile purchase help now cover The X Subscription and call the older plans legacy. Added x.ai/bot's 3.5x and 12x Premium usage wording beside the 15x and 50x Plus figures, Cursor's closest-tier pairings, and the new Grok Business seat message. We did not buy or switch a plan.

October 14, 2026: added The X Subscription, launched October 12: its tiers, monthly and annual prices, which tiers include Grok Bot, the shared weekly pool, team seats, what existing subscribers can do, and where SpaceXSI's and Cursor's pages still disagree. Relabelled the Cursor and SuperGrok prices as existing plans, since cursor.com/pricing now shows only The X Subscription. We did not buy or switch a plan.

October 11, 2026: added self-serve Grok Business seats, which Cursor's help now lists as including Grok Bot, and Cursor's official tier pairing (Pro with SuperGrok and X Premium+, Pro+ with Plus, Ultra with Heavy). Corrected where Link Grok Account appears and that a link can now be made from the phone. Added that a Cursor plan does not unlock Bots inside the Grok app. Rechecked monthly Cursor and Teams prices.

October 7, 2026: merged our separate pricing, access and download guide into this page; its old address now redirects here, and download details moved to the platforms guide. Added yearly prices from Cursor's pricing page, the mobile in-app purchase rules and App Store prices, a pick-this-if table, and when each plan got Grok Bot. Rechecked every monthly price.

September 20 to October 2, 2026, on the two earlier pages: corrected an earlier statement that iPad was unsupported, replaced an outdated eligibility list that omitted base plans, added SuperGrok, X Premium+ and Teams prices, the non-stacking rule and trial cancellation, and separated the usage-credit trial from the Apple introductory offer.

## Quick answers

### How much does Grok Bot cost?

There is still no standalone price. Since October 12, 2026, new customers get Grok Bot with The X Subscription's Premium plan at $30 a month, Super at $100 or Ultra at $200, or a team seat at the same prices; the Free and $8 Plus plans do not include it. Existing Cursor Pro ($20), Pro+ ($60), Ultra ($200), Cursor Teams ($40 or $120 a seat), linked SuperGrok and X Premium+ subscriptions, and self-serve Grok Business seats keep working for people who already have them.

### What is The X Subscription?

One subscription from SpaceXSI that covers Grok, Grok Bot, Cursor and X Premium benefits, announced October 12, 2026 and rolling out globally over the following days. Paid plans include one weekly usage pool shared across Grok and Cursor; x.ai/pricing says that within Grok it covers Chat, Imagine, Voice and Bot. Grok Bot is included on Premium, Super, Ultra, Teams and Enterprise.

### Does the $8 Plus plan include Grok Bot?

No. x.ai/pricing marks Grok Bot as not included on Free and Plus, and SpaceXSI's docs say to choose Premium or higher to use it. Plus does include Cursor's agent and Grok Build.

### I already pay for Cursor or SuperGrok. Do I have to switch?

No. SpaceXSI says existing SuperGrok, Cursor and X Premium plans continue at the same price unless you change or cancel them. If you switch, the old web subscriptions you combine are cancelled with a prorated refund, and the switch is permanent. A Cursor plan bought through Apple's App Store is not cancelled for you: cancel it in your iPhone or iPad settings, or Apple keeps billing.

### Is there a yearly Grok Bot plan?

Yes. SpaceXSI's X Subscription pricing docs list Premium at $300 a year, Super at $1,000 and Ultra at $2,000. Cursor's yearly Pro, Pro+ and Ultra prices are no longer shown on cursor.com/pricing, which listed only The X Subscription plans when we checked on October 25; Cursor's legacy plans page lists their monthly prices only.

### Is there a Grok Bot free trial?

Only by referral, as far as the docs say. The X Subscription's Free plan does not include Grok Bot, but a referral program page that appeared on SpaceXSI's docs by October 28 says a friend who opens a referral link, signs up and enters a credit card gets a two-week free trial of Premium, with a reminder seven days before the first charge; the referrer must be on a paid Premium, Super or Ultra plan, based in the US and at least seven days past checkout, and earns one usage reset per friend who becomes a paid subscriber. Cursor's help still describes its older usage-credit trial with a 7-day window, which never becomes a paid plan, and an App Store introductory offer, which renews into a paid Apple subscription unless you cancel in Apple ID → Subscriptions. The 0.78.1 changelog (October 27) says that where Grok Bot offered a free trial, it now offers Get Grok Bot with a unified plan and See Unified Plans instead.

### Is X Subscription Ultra the same as Cursor Ultra?

No, despite the same name and the same $200 monthly price. X Subscription Ultra is a new plan with 50x the usage of Plus, shared across Grok and Cursor, plus X Premium+ benefits; x.ai/bot describes it as 12x Premium usage. Cursor Ultra is the existing Cursor plan, which Cursor's help now calls a legacy plan and pairs with SuperGrok Heavy as the top Grok Bot tier. Cursor's legacy plans page names X Subscription Ultra as its closest comparable plan, but neither company publishes how the two allowances compare for Grok Bot.

### Can I combine Cursor Pro and SuperGrok for more Grok Bot usage?

Not on the existing plans. Cursor's billing page says a Cursor plan and a SuperGrok or X Premium+ link do not stack, and Grok Bot uses whichever grants more weekly usage. The X Subscription replaces both with one plan and one shared pool; for more, move up a tier or buy top-ups.

### Can I move my SuperGrok link to another Cursor account?

No. Cursor says a SuperGrok or X Premium+ link is permanent once created. If you switch to The X Subscription and have more than one Cursor account, SpaceXSI's docs say you choose a primary Cursor account and the others are combined into it.

### Does my Cursor plan unlock Grok Bot inside the Grok app?

No. A Cursor staff member said on October 11 that the Bots section inside the main Grok app, and Grok in a Tesla, was available only with SuperGrok. x.ai/pricing now says the X Subscription pool covers Bot within Grok, but we have not confirmed what the Grok app shows on a Premium plan.

### What happens when I run out before the week resets?

It depends on your plan. On The X Subscription, further use is paid from prepaid top-up credit, and SpaceXSI's docs say a monthly additional usage limit is the hard stop; Auto Top-up stays off unless you turn it on. On the existing Cursor plans, work stops unless on-demand usage is on, and Cursor says its monthly limit does not stop a run in progress. See our [weekly usage limit guide](https://www.grokbotwiki.com/guides/grok-bot-weekly-usage-limit).

## Sources

- [Grok Bot changelog: 0.78.1 (free-trial offer replaced by Get Grok Bot with a unified plan, October 27)](https://x.ai/changelog/bot#v0.78.1)
- [SpaceXSI: Introducing The X Subscription (October 12, 2026)](https://x.ai/news/x-subscription)
- [The X Subscription docs: refer friends to Grok Bot (referral program)](https://docs.x.ai/x-subscription/referral-program)
- [x.ai pricing: The X Subscription plans](https://x.ai/pricing)
- [The X Subscription docs: pricing, annual prices and team seats](https://docs.x.ai/x-subscription/pricing)
- [The X Subscription docs: what is The X Subscription?](https://docs.x.ai/x-subscription/overview)
- [The X Subscription docs: Grok Bot on The X Subscription](https://docs.x.ai/x-subscription/grok-bot)
- [The X Subscription docs: usage limits](https://docs.x.ai/x-subscription/usage-limits)
- [The X Subscription docs: spending caps](https://docs.x.ai/x-subscription/spending-caps)
- [The X Subscription docs: do I have to switch?](https://docs.x.ai/x-subscription/do-i-have-to-switch)
- [The X Subscription docs: who can combine accounts](https://docs.x.ai/x-subscription/eligibility)
- [The X Subscription docs: team plans and seats](https://docs.x.ai/x-subscription/team-plans)
- [The X Subscription docs: Cursor subscriptions bought through the App Store](https://docs.x.ai/x-subscription/app-store)
- [Cursor pricing (now showing The X Subscription plans)](https://cursor.com/pricing)
- [Cursor plans and billing for Grok Bot (existing plans)](https://cursor.com/help/grok-bot/plans)
- [Cursor: subscribe from the mobile app](https://cursor.com/help/grok-bot/mobile-purchase)
- [Cursor: link SuperGrok for Grok Bot](https://cursor.com/help/grok-bot/supergrok)
- [Cursor: on-demand usage for mobile subscriptions](https://cursor.com/help/account-and-billing/on-demand-usage-for-mobile-subscriptions)
- [Cursor team pricing (X Subscription seats and legacy Teams seats)](https://cursor.com/docs/account/teams/pricing)
- [Cursor docs: legacy Cursor plans](https://cursor.com/docs/account/pricing/legacy-cursor-plans)
- [Cursor docs: Grok Bot (still lists only the older plans)](https://cursor.com/docs/grok-bot)
- [Grok Bot product page (shows The X Subscription plans since October 2026)](https://x.ai/bot)
- [Grok Bot on the App Store (in-app purchase prices)](https://apps.apple.com/us/app/grok-bot/id6794501026)
- [SpaceXSI: Introducing Grok Bot (August 11, 2026)](https://x.ai/news/introducing-grok-bot)
- [SpaceXSI: Grok Bot is now included with more plans (August 26, 2026)](https://x.ai/news/grok-bot-more-plans)
- [xAI: Grok Bot for Enterprise (September 3, 2026)](https://x.ai/news/grok-bot-for-enterprise)
- [SpaceXSI: Team Bots (September 28, 2026)](https://x.ai/news/team-bots)
- [Eligibility and installation](https://docs.x.ai/grok-bot/get-started)
- [Grok Bot FAQ](https://docs.x.ai/grok-bot/faq)
- [Teams and enterprises](https://docs.x.ai/grok-bot/teams-and-enterprises)
- [Grok Bot changelog (Grok Business seat usage message, 0.75.5)](https://x.ai/changelog/bot)
- [Forum: SuperGrok Heavy vs Cursor Ultra (staff reply, September 10)](https://forum.cursor.com/t/supergrok-heavy-vs-cursor-individual-ultra/170888)
- [Forum: usage too low even on Cursor Ultra (staff reply, September 22)](https://forum.cursor.com/t/grok-bot-usage-too-low-even-on-cursor-ultra/172584)
- [Forum: confused over Grok Bot (staff replies, September 17 and 21)](https://forum.cursor.com/t/confused-over-grok-bot/171745)
- [Forum: Cursor plan does not unlock Bots in the Grok app (staff reply, October 11)](https://forum.cursor.com/t/grok-bot-subscribed-with-cursor-how-to-access-in-grok-app/174183)

---

# Grok Bot download for Windows, Mac, Linux, iPhone, Android

> Download Grok Bot for each device: supported versions (Windows 10 and 11, iOS 18, Android 9), Linux packages, and what the mobile apps can't do yet.

- Canonical page: https://www.grokbotwiki.com/guides/grok-bot-platforms
- Sources checked: 2026-10-30
- Evidence: Official mobile docs (phone apps, routines) read October 30, 2026; changelog entry 0.78.1 (October 27) and Cursor's secrets and Shared Bots help read October 29, 2026; changelog entry 0.77.0 (October 26) read October 28, 2026; official documentation and Cursor help and docs rechecked October 25, 2026 with the changelog through 0.75.5; x.ai/bot FAQ read October 25; download pages and store listings checked October 11; x.ai/bot download list checked October 7 · not a device test. Suggested workflows have not been independently tested.
- Publisher: Grok Bot Wiki, an independent guide not affiliated with SpaceXSI, xAI or X.

## Which devices run Grok Bot

Grok Bot has desktop apps for macOS (Apple silicon and Intel), Windows (x64 and Arm64) and Linux (x64 and Arm64), and mobile apps for iPhone on iOS 18 or later, iPad on iPadOS 18 or later, and Android 9 or later. Every app connects to the same cloud computer, so your Bots, conversations and routines sync across devices and keep working when the app is closed; the October 11 changelog adds that pinned Bots now sync between desktop and phone. The docs list no browser version.

The docs give processor architectures but no minimum macOS or Linux version. The More downloads list on x.ai/bot, checked October 7, describes the Windows build as Windows 10 and 11 (x64); the docs and Cursor's download page also offer a Windows Arm64 installer.

| Platform | Supported builds | Where to get it | Main limits |
| --- | --- | --- | --- |
| macOS | Apple silicon or Intel | x.ai/bot or Cursor's download page | None documented beyond the general ones below |
| Windows | Windows 10 and 11; x64, or Arm64 from Cursor's download page | x.ai/bot or Cursor's download page | None documented beyond the general ones below |
| Linux | x64 or Arm64 as .deb, .rpm or AppImage | More downloads on x.ai/bot, or Cursor's download page | Hardware security keys not yet supported; update to 0.70.2 or later if the app froze while a notification was showing |
| iPhone | iOS 18 or later | Grok Bot on the App Store | Editing routines and test runs need desktop |
| iPad | iPadOS 18 or later | The same App Store app runs on iPad | Same as iPhone |
| Android | Android 9 or later | Grok Bot on Google Play | Same as iPhone; the share sheet accepts text only |

Sources: https://docs.x.ai/grok-bot/get-started, https://docs.x.ai/grok-bot/faq, https://docs.x.ai/grok-bot/mobile, https://x.ai/bot, https://cursor.com/download/bot, https://apps.apple.com/us/app/grok-bot/id6794501026, https://play.google.com/store/apps/details?id=ai.x.grok.bot, https://x.ai/changelog/bot

## Where to download Grok Bot

Use the official pages only. The x.ai/bot page offers the build for your computer, with every other platform under More downloads: Windows 10 and 11 (x64), iPhone and iPad on the App Store, Android phones and tablets on Google Play, Intel Macs, and Linux as .deb, AppImage or .rpm for x64 and arm64. Cursor's download page at cursor.com/download/bot lists every installer, including Windows Arm64 and each Linux format for both architectures.

The mobile apps are Grok Bot on the App Store and ai.x.grok.bot on Google Play, separate from the Grok chatbot app. If your Cursor account already includes Grok Bot, sign in with it; Cursor's help says not to buy a second subscription in the app, and that only monthly individual plans are sold there. Plans and prices are in our [plan and pricing guide](https://www.grokbotwiki.com/guides/grok-bot-which-plan).

Sources: https://x.ai/bot, https://cursor.com/download/bot, https://apps.apple.com/us/app/grok-bot/id6794501026, https://play.google.com/store/apps/details?id=ai.x.grok.bot, https://cursor.com/help/grok-bot/mobile-purchase

## Desktop: install the right build

Since 0.65.0 (September 30) Automatic Updates is on by default, so Grok Bot restarts to apply updates while you are away; turn it off in Settings → Updates, where Check for Updates forces a check. Cursor's help says Grok Bot requires an update when your version is more than 14 days old and a newer one is out; on Linux that screen may give you an apt or dnf command to copy instead. To see your version, open the account menu, then Support, then About. If an update does not stick, Cursor's help says to download the latest build from the Grok Bot page of your Cursor dashboard and install it over the app; your Bots and chats belong to your account. The app and the cloud computer update separately: updating the desktop app does not reset the cloud computer, which has its own Update control in the same section.

On September 18 a user reported that the direct Windows x64 link for version 0.57.0 returned Access Denied. Cursor staff shared the 0.56.1 installer and said they were tracking the problem. If a direct link fails, start again from the download page rather than an old link.

1. Mac: Apple menu → About This Mac shows Chip for Apple silicon or Processor for Intel. Open the disk image, drag Grok Bot to Applications, and choose Open if macOS asks. Since 0.66.0, a copy running from the disk image or Downloads offers Move to Applications. Since 0.78.1 (October 27), on an Apple silicon Mac the Intel version of Grok Bot offers to download the Apple silicon version.
2. Windows: Settings → System → About → System type shows x64 or Arm64. Run the installer, then open Grok Bot from the Start menu.
3. Linux: run uname -m; x86_64 means x64 and aarch64 means Arm64. Install the .deb or .rpm with your package manager, or make the AppImage executable and run it.
4. Choose Sign in, finish Cursor authentication in the browser, and return to the app. If your access comes from SuperGrok, link it when the app asks.

Sources: https://x.ai/changelog/bot#v0.78.1, https://docs.x.ai/grok-bot/get-started, https://docs.x.ai/grok-bot/troubleshooting, https://cursor.com/download/bot, https://forum.cursor.com/t/grok-bot-download-link-not-working/172302, https://x.ai/changelog/bot, https://cursor.com/help/grok-bot/how-to

## iPhone, iPad and Android: what works and what doesn't

The mobile app connects to the same Bots, conversations, routines, connectors and shared computer as desktop. From a phone you can message Bots, dictate, start a voice chat, attach photos and files, mention Bots in group chats, take over the computer for a password or CAPTCHA, create Bots and groups, install plugins, and approve or discard drafted emails and Slack messages.

The limits: testing a routine needs the desktop app. On a phone you can pause, resume and delete routines, the mobile docs (read October 30, 2026) say Add routine on a Bot's profile starts a new one, and Edit routine opens the Bot's chat with a draft request, so you describe the change and the Bot makes it. Updating, recovering or resetting the cloud computer is desktop-only too. Some advanced desktop controls and teach-by-demonstration are not on mobile. Shared Bots (formerly Team Bots) can be chatted with on a phone but are created, published and connected to Slack on desktop. On iPhone the share sheet sends photos, files, links and text into a chat; on Android it currently accepts text only. Cursor's help lists 12 languages on the phone against 37 on desktop. Since 0.75.5, Settings → Vault, for saved logins, cards and contact info, is on the phone as well as desktop. Cursor's secrets help, checked October 29, notes one phone bug: on Grok Bot for iPhone 1.18.0 with iOS 26 or later, a new login in Settings → Vault shows no Save button, which is fixed in iPhone 1.19.0 as it rolls out on the App Store; until you update, add the login from the desktop app or from the Secure Form the Bot shows in chat. Cursor's Shared Bots help says sharing and browsing shared Bots on the phone also need 1.19.0 on iPhone and Android.

The mobile docs, read October 30, 2026, also describe a feature no changelog entry has announced yet: in your own chat with a Bot you own, the Bot can use some apps on your phone while Grok Bot is open on it. On iPhone and Android it can read and change Calendar events (not repeating ones, and it never invites anyone), look people up in Contacts without changing them, read the phone's current position, and set a one-off alarm up to 24 hours ahead or a timer; on iPhone it can also manage Reminders and Apple Home accessories, including locks, garage doors and security systems. It does not work in group chats, in Slack or with a shared Bot someone else owns. Each app needs your phone's permission, given ahead of time under Settings → Connect apps or when the chat shows a Grok Bot needs permission card, and Settings → Bot → Manage your devices lists the phones and computers where you use Grok Bot. A team admin's limit on local execution applies to phones too. We have not tried it.

Android arrived on September 2, 2026, according to Cursor's forum announcement. If your access comes from SuperGrok, the mobile access screen offers Link Grok Account and then Finished Linking? Refresh My Status.

Sources: https://cursor.com/help/grok-bot/shared-bots, https://docs.x.ai/grok-bot/mobile, https://docs.x.ai/grok-bot/get-started, https://forum.cursor.com/t/grok-bot-is-now-live-on-android/170384, https://cursor.com/help/grok-bot/mobile, https://cursor.com/help/grok-bot/how-to, https://cursor.com/help/grok-bot/secrets, https://x.ai/changelog/bot

## What differs between desktop platforms

The three desktop apps share one feature set in the docs, with a few documented differences.

- [ ] Hardware security keys: the Bot's browser can use a key plugged into your desktop. The setting is on by default on macOS and Windows and not yet supported on Linux.
- [ ] Local computer access: a Bot runs commands on the computer in front of you only when Execution on Local Computer allows it. The default is Ask every time, and the docs describe it for Mac and Windows.
- [ ] Shortcuts use Cmd on macOS and Ctrl on Windows and Linux; dictation is Cmd/Ctrl+D and Settings is Cmd/Ctrl+,.
- [ ] Several saved accounts, with Switch account and Add account, are a desktop feature. The October 11 changelog says switching accounts now lands within seconds even when another account's computer is asleep.
- [ ] On a Mac, View → View Unread shows only Bots with unread messages (changelog, October 11).
- [ ] Notifications: since 0.71.2 (October 14, on 0.70.2 or later), while you use Grok Bot on a Mac or Windows PC, replies and questions from Bots you own notify you there instead of on your phone. The docs say a Bot that needs your input still notifies your phone about 3 minutes later unless you open it first. On Linux, notifications are suppressed while Grok Bot is focused and your phone is notified as usual.
- [ ] 1Password: the changelog's 0.77.0 entry (October 26) says that on Windows and Linux the Bot now notices an installed 1Password app and can offer to connect it, and that 1Password connects without a shared vault on Grok Bot 0.68.0 or later; the glossary's Mac-only note dates from 0.53.0.
- [ ] Languages and time zones: 0.77.0 adds Português (Portugal) to the app's languages, relabels Brazilian Portuguese as Português (Brasil), and adds Europe/Kyiv to the time zone picker.

Sources: https://docs.x.ai/grok-bot/approvals-security-and-privacy, https://docs.x.ai/grok-bot/chat-and-collaboration, https://docs.x.ai/grok-bot/settings-and-notifications, https://x.ai/changelog/bot

## One account and one allowance on every device

Your plan and usage do not depend on the device. Cursor's billing page says macOS and iOS share a single usage bucket tied to your Cursor account, because both apps call the same backend. If you subscribed in the iOS or Android app, Cursor says to set on-demand usage on the web. Plans and prices are in our [plan and pricing guide](https://www.grokbotwiki.com/guides/grok-bot-which-plan), Windows sign-in problems have [their own guide](https://www.grokbotwiki.com/guides/grok-bot-sign-in-error-windows), and [How to use Grok Bot](https://www.grokbotwiki.com/guides/getting-started) covers the first steps after installing.

Sources: https://cursor.com/help/grok-bot/plans, https://cursor.com/help/grok-bot/mobile-purchase

## Where official pages disagree

Some official pages lag behind. When we checked on October 25, the FAQ on x.ai/bot still said to use Grok Bot on desktop (macOS or Windows) or your phone with the iOS app, although the same page's More downloads list includes Linux and Android. Cursor's Grok Bot docs page, which on October 11 named iOS but not Android, now says macOS, Windows, Linux, iOS and Android, matching Cursor's mobile help. The docs.x.ai FAQ, mobile page and getting-started page list Linux, Android and iPad. The x.ai/bot list, as we checked it on October 7, names Windows x64 only, while the docs and Cursor's download page also offer Arm64. We follow docs.x.ai and the download pages.

Sources: https://x.ai/bot, https://cursor.com/docs/grok-bot, https://cursor.com/help/grok-bot/mobile, https://docs.x.ai/grok-bot/faq, https://docs.x.ai/grok-bot/mobile, https://docs.x.ai/grok-bot/get-started, https://cursor.com/download/bot

## Quick answers

### Does Grok Bot run on Windows 10?

The More downloads list on x.ai/bot, checked October 7, 2026, offers the Windows build for Windows 10 and 11 (x64). The docs list Windows x64 and Arm64 builds but no minimum Windows version, and Cursor's download page also offers an Arm64 installer.

### Is there a Grok Bot app for iPad?

Yes. The docs say the iOS app also runs on iPad with iPadOS 18 or later. Install Grok Bot from the App Store on the iPad and sign in with the same Cursor account.

### Does Grok Bot work on Linux?

Yes. Linux builds are published with every stable release for x64 and Arm64, as a .deb package for Debian and Ubuntu, an .rpm for Fedora and RHEL, or an AppImage. They are under More downloads on x.ai/bot and on Cursor's download page. Hardware security keys are not yet supported on Linux, and the desktop notifications that replace phone alerts on Mac and Windows do not apply on Linux. The changelog entry of October 11 (0.69.0 to 0.70.2) fixes a Linux problem: the app now stays responsive and can quit while a notification is showing.

### Is there a web version of Grok Bot?

Not in the docs we checked, which list only the desktop and mobile apps. A shared template link opens a preview on x.ai, but the docs say you need the Grok Bot app to finish adding it.

### Is the Grok Bot app the same as the Grok app?

No. Grok Bot has its own store listings, which the docs link: Grok Bot on the App Store and ai.x.grok.bot on Google Play. The Grok chatbot app is a separate download, so check the name before installing. The Grok app has its own Bots section, but a Cursor staff member said on October 11 that it currently works only with a SuperGrok subscription; with a Cursor plan, use the Grok Bot apps.

### How do I update Grok Bot on Linux?

Settings → Updates → Check for Updates works on every desktop. When the app says Update required on Linux, Cursor's help says it may show a command instead: sudo apt update && sudo apt install --only-upgrade grok-bot on Debian or Ubuntu, or sudo dnf upgrade --refresh grok-bot on Fedora and other RPM systems. Since 0.71.2 (October 14), the Update required screen on .deb and .rpm installs links the latest package. Then restart Grok Bot.

### Does closing the app stop my Bots?

No. Bot work runs on the cloud computer, and the FAQ says closing the app, laptop or phone does not stop a background turn or a routine. The apps are clients for that computer.

## Sources

- [Get started: install the desktop app](https://docs.x.ai/grok-bot/get-started)
- [Grok Bot FAQ: supported platforms](https://docs.x.ai/grok-bot/faq)
- [Grok Bot for Mobile](https://docs.x.ai/grok-bot/mobile)
- [Grok Bot overview](https://docs.x.ai/grok-bot/overview)
- [Official troubleshooting: updates](https://docs.x.ai/grok-bot/troubleshooting)
- [Approvals: security keys and local computer](https://docs.x.ai/grok-bot/approvals-security-and-privacy)
- [Message and collaborate: voice and shortcuts](https://docs.x.ai/grok-bot/chat-and-collaboration)
- [Settings: accounts and language](https://docs.x.ai/grok-bot/settings-and-notifications)
- [Create and manage Bots: Share a Bot](https://docs.x.ai/grok-bot/bots)
- [Cursor: download Grok Bot](https://cursor.com/download/bot)
- [Grok Bot on the App Store](https://apps.apple.com/us/app/grok-bot/id6794501026)
- [Grok Bot on Google Play](https://play.google.com/store/apps/details?id=ai.x.grok.bot)
- [Grok Bot changelog: 0.77.0 (Portuguese (Portugal), 1Password on Windows and Linux, October 26)](https://x.ai/changelog/bot#v0.77.0)
- [Grok Bot product page and FAQ](https://x.ai/bot)
- [Cursor docs: Grok Bot](https://cursor.com/docs/grok-bot)
- [Cursor plans and billing for Grok Bot](https://cursor.com/help/grok-bot/plans)
- [Cursor help: subscribe from the mobile app](https://cursor.com/help/grok-bot/mobile-purchase)
- [Cursor help: how-tos (updates, versions, languages)](https://cursor.com/help/grok-bot/how-to)
- [Cursor help: Grok Bot on mobile](https://cursor.com/help/grok-bot/mobile)
- [Grok Bot changelog: 0.78.1 (Intel build offers the Apple silicon version, October 27)](https://x.ai/changelog/bot#v0.78.1)
- [Cursor help: Shared Bots (phone version needed for sharing)](https://cursor.com/help/grok-bot/shared-bots)
- [Cursor help: store secrets securely (Vault)](https://cursor.com/help/grok-bot/secrets)
- [Forum: Bots in the Grok app need SuperGrok (staff reply, October 11)](https://forum.cursor.com/t/grok-bot-subscribed-with-cursor-how-to-access-in-grok-app/174183)
- [Grok Bot changelog](https://x.ai/changelog/bot)
- [Forum: Grok Bot is now live on Android (staff, September 2)](https://forum.cursor.com/t/grok-bot-is-now-live-on-android/170384)
- [Forum: Windows download link not working (staff reply, September 18)](https://forum.cursor.com/t/grok-bot-download-link-not-working/172302)

---

# What's new in Grok Bot: October 2026 updates

> Grok Bot 0.63 to 0.78.1 (Sept 29–Oct 27, 2026) in plain English: shopping cards, subscription templates, a Permissions screen, Vault payments, question cards, Pages, Shared Bots.

- Canonical page: https://www.grokbotwiki.com/guides/grok-bot-whats-new
- Sources checked: 2026-10-29
- Evidence: Grok Bot changelog entry for 0.78.1 (October 27, also covering 0.78.0) read October 29, 2026; entry for 0.77.0 (October 26), SpaceXSI's October 27 sales post and docs.x.ai's new Vault and Shared Bots pages read October 28, 2026; entry for 0.75.8 (October 24) read October 27; entries for 0.71.2 (October 14), 0.75.2 (October 22) and 0.75.5 (October 23) read October 25, 2026; Cursor help (Pages, Vault, routines, agent email, Shared Bots), docs.x.ai and the Secure Form forum thread checked October 25 · earlier entries as read October 14 · summaries and impact notes are ours · features not tested by us. Suggested workflows have not been independently tested.
- Publisher: Grok Bot Wiki, an independent guide not affiliated with SpaceXSI, xAI or X.

## The short version

Grok Bot shipped versions 0.63.0 to 0.78.1 between September 29 and October 27, 2026. The newest entry, 0.78.1 (October 27, also covering 0.78.0), turns shopping into cards: products show as cards with photos, rating, price and store, Buy now starts an order you approve, the Bot tracks the order until it arrives, Shop Pay connects from Vault's Payments tab, and three templates start free trials and cancel them before they bill, cancel subscriptions you pick, and watch renewal prices. The same entry lets a Shared Bot be limited to Only you, lets managers give a Shared Bot logins in its own Vault, and replaces the free-trial offer with Get Grok Bot with a unified plan. Before it, 0.77.0 (October 26, also covering 0.76.0) is the longest of the month: Settings gets a Permissions section that lists every Auto-review rule, Vault gets a Payments tab where you pick which payment method Bots use first, 1Password connects without a shared vault, Bots can ask several questions on one card, Import Memory brings your preferences from another AI assistant, approval cards stay open for 30 minutes instead of 10, and the Bot's computer should fail less often with Couldn't Reach Grok Bot's Computer. Outside the app, the docs now call Team Bots Shared Bots. 0.75.8 (October 24) let a Bot offer to add, change or remove one of your Auto-review rules on a card you confirm and cut the number of approval cards. 0.75.5 (October 23) added Vault and email forwarding, 0.75.2 (October 22) added Pages, video creation and Shop Pay, and 0.71.2 (October 14) raised attachment limits and let Bots use up to 200 plugin skills.

This page summarizes the official changelog in plain English and says what each change means in practice. The wording of each change is SpaceXSI's; the impact notes are ours, and we have not tested the features. Each entry rolls several versions together and does not say which change landed in which, so the tables are grouped by topic.

| Release | Headline | What it means for you |
| --- | --- | --- |
| 0.78.1 · Oct 27 | Shopping cards and subscription templates | Product cards and carousels, Buy now with your approval, order tracking, Shop Pay in Vault; templates that start and cancel free trials, cancel unused subscriptions and watch renewal prices; Shared Bots limited to Only you; the free-trial offer becomes Get Grok Bot with a unified plan |
| 0.77.0 · Oct 26 | Permissions, Vault payments, and question cards | One Settings screen for every Auto-review rule; a default payment method and hints in Vault; 1Password without a shared vault; multi-question cards; approval cards wait 30 minutes; Import Memory from another assistant |
| 0.75.8 · Oct 24 | Auto-review rule cards and smarter connectors | A Bot can propose a change to your Auto-review rules on a card you confirm; fewer safe actions need an approval card; connectors pick up new tools without a reconnect; a Shared Bot is reachable only by the people on its share list |
| 0.75.5 · Oct 23 | Vault, email forwarding, and fewer approval cards | Saved logins and cards let Bots sign in and pay without asking you each time; requests you make in your own words stop less often |
| 0.75.2 · Oct 22 | Pages, new chat cards, and video creation | Bots build shareable Pages and videos, pay with Shop Pay, and edit several Calendar events at once; routines can read the Bot's inboxes |
| 0.71.2 · Oct 14 | Smarter notifications and larger file attachments | Up to 20 attachments per message and 250 MB files; desktop notifications replace phone ones while you work; 200 plugin skills |
| 0.69.0–0.70.2 · Oct 11 | Bot email addresses, X search, and in-chat apps | Bots get their own mail address and read public X; irreversible actions and bank or brokerage data get an extra approval check |
| 0.68.1 · Oct 7 | Slide decks and Bot-colored chats | Bots can build slide decks and send formatted email; Stop now ends a stuck Bot within about 30 seconds |
| 0.68.0 · Oct 5 | New languages and computer removal | Email drafts can go out from a verified Gmail send-as address; saved approval rules are now called Custom Rules |
| 0.67.0 · Oct 2 | Connect Apps and new working status | Marketplace is renamed Connect Apps and Bot templates live on the web; connected Google accounts show their email address |
| 0.66.0 · Oct 2 | Proactivity, primary Bot and more reliable updates | Your starred primary Bot can offer to take work; a Bot that hangs stops itself with a note |
| 0.65.0 · Sep 30 | Shared Bot voice chat and automatic updates | Automatic Updates is on by default; teammates can voice-chat with a Shared Bot |
| 0.64.0 · Sep 30 | Shared Bot managers and refreshed avatars | Shared Bot creators can add managers; draft cards can be switched off for a Bot so it sends directly |
| 0.63.0 · Sep 29 | Slack approvals and faster browsing | Marketplace shows only plugins; a used-up plan shows the usage limit notice instead of Bot failed to respond |

Sources: https://x.ai/changelog/bot, https://x.ai/changelog/bot#v0.78.1, https://x.ai/changelog/bot#v0.77.0, https://x.ai/changelog/bot#v0.75.8, https://x.ai/changelog/bot#v0.75.5, https://x.ai/changelog/bot#v0.75.2, https://x.ai/changelog/bot#v0.71.2

## 0.78.1 (October 27): shopping cards and subscription templates

The October 27 entry covers 0.78.0 and 0.78.1. Its new features are about buying and paying: products as cards, orders you approve and the Bot then tracks, Shop Pay in Vault, and three templates that act on free trials and subscriptions. It also tightens who can reach a Shared Bot, gives Shared Bots their own Vault logins, and carries a long list of fixes, several of which answer symptoms in our Fix problems guides.

| Area | What the changelog says | What it means for you |
| --- | --- | --- |
| Shopping | Shopping with a Bot shows products as cards with photos, rating, price and store, plus up to two badges such as Top rated; three or four results scroll in a carousel and you can swipe through each product's photos; on a product page, in-stock options come first, options no store has are disabled, and Buy now starts an order you approve; after you order, the Bot tracks it and tells you when it ships or arrives, and shipment cards show the carrier and stage | A purchase is still an approval, but a saved card in Vault fills in without one; see [our safety guide](https://www.grokbotwiki.com/guides/is-grok-bot-safe) |
| Shop Pay and Vault | Connect Shop Pay in the Vault's Payments tab, then pick it under Pay with or make it the payment method Bots use first; editing a Vault contact offers Add email, Add phone and Make primary | Shop Pay joins Link and X Money as a wallet a Bot can pay with |
| Subscriptions | The Try it, don't pay for it template starts a free trial for you and cancels it, or reminds you, before it bills; Find unused subscriptions cancels plans you pick from the ones you still pay for, and Watch subscription prices checks renewal prices; Bots can cancel a subscription or look up its price and renewal date, and confirm with you before changing anything | Three official templates that act on money; read the confirmation card before you approve a cancellation |
| Shared Bots | 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; when a Shared Bot routine needs one of your connectors, it asks in the routine's Slack thread and tags you; when your 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; the Grok Bot admin page says Shared Bots, with Manage Shared Bots and Create Bot | Cursor's secrets help still says Vault is not supported on shared Bots, so the two official sources disagree; see [our Shared Bots guide](https://www.grokbotwiki.com/guides/grok-bot-team-bots) |
| Plans | Where Grok Bot offered a free trial, it now offers Get Grok Bot with a unified plan and See Unified Plans; buying a plan during desktop sign-in returns you to the approval screen, so the app finishes signing in | The in-app trial offer is gone; the referral trial in [our plan guide](https://www.grokbotwiki.com/guides/grok-bot-which-plan) is the one the docs describe |
| Connectors | App cards, plugin rows, sign-in errors and connector errors show the connector's name instead of an internal ID; on Cloudflare, Coinbase, Gusto, YouTube, Railway, Google Ads, Meta Ads and TikTok for Business sign-in pages, the Bot offers that connector; when a connector needs a permission its connection cannot request, the Bot says reconnecting will not help; after 10 minutes a connect card asks Still signing in?; signing in to a Google account that is already connected reuses it, with one reconnect card; Remove from Slack now disconnects Slack; the Tailscale plugin shows Not available yet on accounts that cannot use it | Fewer mystery IDs and duplicate cards; see [our plugins guide](https://www.grokbotwiki.com/guides/grok-bot-plugins-mcp) |
| Email and Slack | Gmail drafts the Bot writes in plain text open in rich text; Gmail drafts and sends can attach a file from the Bot's computer in more cases; Bot emails retry once when the mail server connection times out; in Slack, people whose account is not linked learn that some features are limited and how to link it; Copy on a reply keeps headings, lists and links when you paste into Slack, Gmail, Docs or Notion | Three Gmail fixes in [our Gmail guide](https://www.grokbotwiki.com/guides/grok-bot-gmail-google-workspace) |
| The Bot's computer and your own | The computer card stays on Asleep during brief background wakes and shows Waking up… as soon as you wake it; with Route traffic through this computer on, Settings says when the Bot's computer is asleep and that routing reconnects when it wakes, and pages no longer fail right away when only another host on them is refused; approved browser actions no longer fail when the page has not changed; when the Bot's computer has been refusing saves, Reset and Recover keep the current disk instead of restoring an older backup; on an Apple silicon Mac, the Intel version offers to download the Apple silicon version; the Bot's browser types one character at a time and moves the mouse on every website it fills in | Several rows in [our not-responding guide](https://www.grokbotwiki.com/guides/grok-bot-not-responding) |
| Routines and cloud agents | Routines made in a new Bot's first chat run in your time zone instead of UTC; clicking a webhook routine opens its details, including the webhook URL; Bots can start cloud agents in a custom mode you name and keep replying to them in it | A time zone explanation for routines that fired hours off from a brand-new Bot; see [our routines guide](https://www.grokbotwiki.com/guides/grok-bot-routines-not-running) |
| Updates, usage and chat | Update installs the version you clicked, an open Update ready dialog switches to the newest finished download, and when a restart is refused every Update button says why; the usage limit banner closes once you are back under your limit; usage breakdowns from a Bot label the catch-all row Deleted bots, group chats and other people's bots; single-choice question cards show Something else again; specific working statuses show right away while generic ones wait a moment; task lists and thread names refresh after the app reconnects; two saves to the same memory at once no longer overwrite each other; spend totals use the right currency | Housekeeping, plus one memory fix worth knowing if two Bots write to the same memory |
| Pages and code review | Bots apply several Page edits at once and leave the Page unchanged if any edit does not fit; diagrams on a Page wrap long labels; Bots using the built-in code review tools act with your access and never approve your own pull request | See [our Pages guide](https://www.grokbotwiki.com/guides/grok-bot-pages) |
| Enterprise | With Terminate Inactive Computers on, a computer counts as inactive after 30 days without a message to any of its Bots | Admins: check that threshold against how your team uses Bots |

Sources: https://x.ai/changelog/bot#v0.78.1, https://cursor.com/help/grok-bot/secrets

## 0.77.0 (October 26): Permissions, Vault payments and question cards

The October 26 entry covers 0.76.0 and 0.77.0 and runs to well over a hundred items. Most of the new features need Grok Bot 0.75.2 or later; the 1Password change and the new typeface need 0.68.0 or later. The rows below group the changes most people will meet; the fixes are summarized at the end.

| Area | What the changelog says | What it means for you |
| --- | --- | --- |
| Permissions | Settings has a Permissions section that lists Auto-review rules under Always Ask and Allow without Asking, each with its own Add Rule button; rule cards in chat show each rule as a sentence and name any older Allow rule removed to make room; approval cards stay open for 30 minutes instead of 10, in the app and in Slack | One screen to audit every rule, and a longer window for routines whose approvals used to expire. See [our permission boundaries guide](https://www.grokbotwiki.com/guides/permission-boundaries) |
| Auto-review | Lets through more private actions you can undo without an approval card, keeps an approval when only your open tabs change, and background work you start in your own words no longer asks for approval to start; when a safety filter stops a computer task, the Bot tries another model before asking you to do that step | Fewer cards again; an explicit Ask first rule is still the only guarantee of a card |
| Question cards | Bots can ask several questions on one card that steps through them, with Your own answer when none of the choices fit; answered questions stay answered | Fewer back-and-forth turns before a Bot starts |
| Vault and payments | The Vault has a Payments tab where you pick the payment method Bots use first, and you still approve every purchase; entries have a Hints field that tells Bots when to use each one; saved addresses, phones and emails appear together as Contact info; Bots try your saved Vault logins and cards before a password manager or another way to pay, and can update a saved entry's name, hint and card details for you; Link one-time cards are offered only in the US and Canada | A default payment method is a convenience and a risk: our [safety guide](https://www.grokbotwiki.com/guides/is-grok-bot-safe) says keep cards out of Vault if you want to approve each payment |
| 1Password | 1Password connects without a shared vault: you approve each login in 1Password, which fills it in the Bot's browser without the Bot seeing it; fills recover from a sleeping extension or an expired approval; on Windows and Linux the Bot notices an installed 1Password app and can offer to connect it | The shared-vault setup is no longer required; the Google sign-in gap we track in [our Gmail guide](https://www.grokbotwiki.com/guides/grok-bot-gmail-google-workspace) is not mentioned |
| Memory | Import Memory to Grok Bot, in Settings, brings your preferences and context from another AI assistant into your primary Bot | An import, not an export: there is still no one-click way to export a Bot's memory, see [our shared-computer guide](https://www.grokbotwiki.com/guides/grok-bot-shared-computer) |
| Connectors | Connector buttons say Connect everywhere, a signed-out connector shows Not connected, and Your plugins offers Reconnect; in Connect Apps, Add installs a plugin and opens its sign-in in one click; custom MCP servers that use a private certificate authority work once you approve that authority; connector sign-ins can finish up to an hour after you start them; when Google throttles requests, Google apps stay connected and the Bot says to try again later | Fewer false sign-outs; see [our plugins guide](https://www.grokbotwiki.com/guides/grok-bot-plugins-mcp) |
| Gmail | When Gmail signs you out, such as after Google revokes access, your primary Bot tells you in its chat and offers to reconnect; adding a second Gmail or Google Drive account opens Google's account picker; Gmail replies quote the original so Gmail folds the thread; Ask first and Block rules for Gmail searches and reads hold even when the Bot calls them by another name; email draft cards have a Discard button again | The second-account picker closes a gap in [our Gmail guide](https://www.grokbotwiki.com/guides/grok-bot-gmail-google-workspace) |
| Email | Every email a Bot sends from its own address to one other person now includes a one-click unsubscribe, not just the first; Bots no longer send email to addresses that have permanently bounced | Expect the unsubscribe footer on every one-to-one email from a Bot's address |
| Chat and tables | Tables in chat have a copy button for Slack or markdown, and wide tables open full screen with zoom; dictation writes words while you are still speaking; the dock badge counts unread conversations instead of messages; Grok Bot has a new typeface for text and code, including on Pages | Cosmetic, but the table copy button is handy for reports |
| Pages | Page owners can delete a Page from the Library, which removes it for everyone it was shared with; teammates see Pages shared with the team in a Shared Bot's Library under Shared with your team; links to Grok Bot inside a Page open in the app | Deleting from the Library is now as final as deleting from the dashboard; see [our Pages guide](https://www.grokbotwiki.com/guides/grok-bot-pages) |
| Templates | Order Concierge and Deal Watcher templates track your orders, refunds and returns, and watch prices and coupons, never buying without your OK; team admins choose whether members can publish Bot templates publicly, only to the team, or not at all | Two more official templates, and a third option for admins; see [our Marketplace guide](https://www.grokbotwiki.com/guides/grok-bot-marketplace-templates) |
| Slack | Message drafts show a formatted preview and who the message notifies; the Bot checks what a reply is answering before acting, and in shared conversations checks each post against who can read it; people without a linked Grok Bot account cannot use the owner's logins or private data through the owner's Bot | Safer shared channels; the preview is worth reading before you approve |
| The Bot's computer | The computer stays up when memory runs low and recovers faster after a crash, so fewer turns end on Couldn't Reach Grok Bot's Computer; commands that wait for input, such as package install prompts, finish instead of hanging; the Bot's browser keeps site logins after its last window closes; keys stored in the system keyring survive when the computer is recreated; browser screenshots keep their full size; with Route traffic through this computer on, plain http pages load and the Bot says when your computer goes offline | Two symptoms in [our not-responding guide](https://www.grokbotwiki.com/guides/grok-bot-not-responding) have a fix here |
| Shared Bots | 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; linked teammates on a Shared Bot use their own connectors and memory; plugins a team admin would not allow show Disabled by team admin; Enterprise audit logs record changes to a team's trusted CA certificates | The admin-only sharing switch answers an October 10 forum request; see [our Shared Bots guide](https://www.grokbotwiki.com/guides/grok-bot-team-bots) |
| Updates and usage | When an update is ready while a Bot is working, Grok Bot offers Stop and Update; when usage cannot load, Usage & Billing keeps the last reading with Try again; when your plan does not include routines, the Bot names the plan that does | Fewer dead ends |
| Languages and smaller changes | Português (Portugal) joins the app's languages and Brazilian Portuguese is labeled Português (Brasil); plugin search finds an app named in Chinese, Japanese or Korean; the time zone picker includes Europe/Kyiv; right-click an emoji to pin it; after you connect your first app, the Bot offers one that pairs with it, such as Google Calendar after Gmail | Housekeeping |

Sources: https://x.ai/changelog/bot#v0.77.0, https://docs.x.ai/grok-bot/vault

## 0.75.8 (October 24): Auto-review rule cards and smarter connectors

The October 24 entry covers 0.75.6, 0.75.7 and 0.75.8. It adds one feature and a list of improvements and fixes, most of them to approvals, connectors and Shared Bots. The rule card and the finished-background-work change need Grok Bot 0.75.2 or later; the connector sign-in fix needs 0.71.2 or later.

| Area | What the changelog says | What it means for you |
| --- | --- | --- |
| Auto-review rules | In the app, a Bot can offer to add, change or remove one of your Auto-review rules on a card you confirm | Rules can now change from inside a chat, not only in Settings; read the card before you confirm, because a rule outlasts the conversation. See [our permission boundaries guide](https://www.grokbotwiki.com/guides/permission-boundaries) |
| Fewer cards | Auto-review takes a second look before showing an approval card, so fewer safe actions need one; a Bot saving or editing one of its routines no longer counts as risky by itself; approval cards in Slack describe the action, as they do in the app | Fewer interruptions, and the same Ask first rules still stop what you tell them to |
| Background work | When background work finishes, the Bot completes what you asked, including steps you said to take once it was done, and says what it would do next instead of acting on its own or on another agent's approval | A handed-off task should no longer stop short, and should not carry on past your request |
| Status and files | A Bot's status line shows up right after you send, even for quick replies; in a chat only you can see, a Bot reads your own private files without asking first | Less waiting to know a Bot is working; expect fewer prompts about your own files |
| Calendar | Scheduling uses the calendar you've connected, Google Calendar or Outlook Calendar, and offers to connect one only when neither is | Connect the calendar you actually use once; see [our Gmail and Workspace guide](https://www.grokbotwiki.com/guides/grok-bot-gmail-google-workspace) |
| Plugins and connectors | When a Bot installs a plugin while working, it can use the plugin's skills right away; when a connector such as X adds tools or fields, Bots can use them without you reconnecting it; a connector whose sign-in expired shows Authenticate in the app instead of Connected | Connected now means connected; if a connector shows Authenticate, sign in again. See [our plugins guide](https://www.grokbotwiki.com/guides/grok-bot-plugins-mcp) |
| Connector files | Images a connector returns as files reach the Bot as images, and other binary files are no longer read as garbled text | Attachments from Slack, Drive and similar connectors should read correctly |
| X Money | X Money connects in one tap for more X accounts, and if it can't connect yours, the Bot says so instead of offering a sign-in | A clearer failure instead of a dead-end sign-in |
| Slack | When a Bot posts to Slack for you, such as from a routine, your phone isn't notified and its unread badge doesn't go up; when a safety check blocks a Bot's reply in Slack, the Bot says so and suggests a different message | Routine posts stop pinging you; a silent Slack Bot may have hit a safety check |
| Your own computer | For most accounts, with Route traffic through this computer on, the connection comes back as soon as the Bot's computer wakes | One less reason to Recover after a sleep; see [our not-responding guide](https://www.grokbotwiki.com/guides/grok-bot-not-responding) |
| Shared Bots | People not on a Shared Bot's share list, including teammates, no longer have access to it until an owner shares it with them; a Shared Bot's routines can read Slack channels you and the Bot are both in, instead of refusing every read; a Shared Bot's edited Slack messages show a muted (edited) label | Check the share list if a teammate lost access; see [our Shared Bots guide](https://www.grokbotwiki.com/guides/grok-bot-team-bots) |

Sources: https://x.ai/changelog/bot#v0.75.8

## 0.75.5 (October 23): Vault, email forwarding and fewer approval cards

The October 23 entry covers 0.75.3, 0.75.4 and 0.75.5. Vault and forwarding need Grok Bot 0.75.2 or later, so update the app first if you do not see them.

| Area | What the changelog says | What it means for you |
| --- | --- | --- |
| Vault | Bots can save your logins, cards and contact info to a Vault in Settings and fill them in to sign in or check out | Cursor's help says the Bot never sees a saved password, card number or security code, but every Bot on your account can use every item, and a saved card can be used at checkout without asking you first |
| Auto-review | It asks less often for an action you asked for in your own words, falls back to an approval card less often, and no longer waves through an action your request said to stop before, such as sending a message you asked only to draft | Fewer interruptions for what you clearly asked for; say draft only or stop before sending when that is what you mean |
| Sending | Emails and Slack messages you ask a Bot to send go out once Auto-review allows them; sends on routine and other turns still wait as drafts | A request in chat is now enough to send. Routine output still stops for you |
| Denying a card | After you deny an approval card, the Bot stops and does not try that action again until you send another message | Deny is now a real stop, not a prompt to find another route |
| Email forwarding | Bots can forward an email from their own inbox with its original formatting, images and attachments | Useful for receipts and reports that land in the Bot's mail.grokbot.com address |
| Routine limits | Your routines can run up to 300 times an hour in total instead of 100, and each routine up to 200 times | Busy triggers fail less often; Cursor's help notes a separate shared limit can still cause rate-limit failures |
| Slack | Bots record who asked for each message they post in Slack; they answer thread replies that were also sent to the channel; a Shared Bot's routine that replies in a thread follows it and answers later replies without an @mention | Anyone in a thread can ask the Bot who requested a post |
| Sign-in | When the Bot hands you its computer to sign in to a site that has a connector, it also offers that connector's connect card | Choose the connector when you can: its sign-in stays out of the shared browser |
| X and X Money | Asking about your X account connects X through your linked X account, even if you removed the X plugin; connecting X also connects X Money, and asking about your X Money balance, activity or card installs X Money | Removing the X plugin is no longer enough to keep X out of a Bot's reach if your account is linked |
| Shared Bots | Teammates in their own DM can react, quote with Add to chat and answer cards; Shared Bots name connectors as your plugin list does and say whose they used | Clearer about whose account did the work; see [our Shared Bots guide](https://www.grokbotwiki.com/guides/grok-bot-team-bots) |
| Smaller changes | Settings shows how many sites were blocked for resolving to a private or VPN address when Route traffic through this computer is on; a pumpkin Bot shape for Halloween; after an account merge you keep managing the Bots you created | Mostly housekeeping |

Sources: https://x.ai/changelog/bot#v0.75.5, https://cursor.com/help/grok-bot/secrets, https://cursor.com/help/grok-bot/routines

## 0.75.2 (October 22): Pages, new chat cards and video

The October 22 entry is the largest of the month, covering 0.72.0 through 0.75.2. The rows below pick the changes most people will notice.

| Area | What the changelog says | What it means for you |
| --- | --- | --- |
| Pages | Bots can build Pages, such as reports, memos and dashboards, that you edit together or have the Bot keep up to date; the dashboard's Pages section lists the Pages you've shared, where you can unshare or delete them | A shareable home for work that changes, instead of a new file each week. Our [Pages guide](https://www.grokbotwiki.com/guides/grok-bot-pages) covers sharing and limits |
| Library | You can pin Library pages, files and links to a Pinned section that stays at the top and syncs across devices; hovering a row shows who sent the item, when, and who can see a Page | Pin the handful of Pages and files you open every week |
| Video | Bots can create videos from a description or from an image you share, and a task the Bot hands off can create images and videos for the chat | New creative output; check usage, since the notes give no cost |
| Payments | Bots can pay with Shop Pay, through Shop checkout where a store accepts it and with a one-time Shop card elsewhere; X Money connects in one tap; when the Bot asks how to pay, you choose on a card | More ways to spend: keep an Ask first rule on purchases |
| Chat cards | Cards in chat have a new design, from approvals and questions to files, links and tables; Auto-review approval cards describe the action in one sentence, name the app with its logo, and flag irreversible or sensitive changes | Approval cards are easier to read; the flag is a prompt to slow down, not a guarantee |
| Gmail and Calendar | The built-in Gmail connection can attach files, reply all, add a note when forwarding and set label colors; Bots can create, update or delete several Calendar events in one step | Closes the attachment gap in our [Gmail guide](https://www.grokbotwiki.com/guides/grok-bot-gmail-google-workspace) |
| Connectors | Zoho CRM can be connected with a regional data center; the GitHub connector can list repositories, compare commits and read branch and issue comments; naming a service shows its connect card; a sign-out or rejected sign-in now says why | See [our plugins guide](https://www.grokbotwiki.com/guides/grok-bot-plugins-mcp) |
| Routines | Routines can read the Bot's inboxes; a routine that hits a signed-out connector shows that connector's Reconnect card, at most once a day; a webhook routine's menu shows its URL and key | Mail-driven routines get simpler; see [skills vs routines](https://www.grokbotwiki.com/guides/skills-vs-routines) |
| Passwords in chat | If you already shared a password or code in the chat, the Bot uses it instead of refusing to continue | Convenient, but the docs still say not to send passwords in ordinary chat |
| Memory and deletion | What a personal Bot saves to memory in one chat is remembered in all your chats with it, and only you can change it; deleting a Bot permanently erases its conversations, memory, routines and attachments and removes its Slack app | Deleting a Bot erases what it held; the note does not mention files it saved to the shared /workspace |
| Shared Bots | Page owners can share with the whole organization or another team; admins can limit who shares Pages with everyone, turn on link previews and upload a team icon; owners and managers can let collaborators create routines | More admin control; Enterprise admins can also permanently delete a member's Grok Bot data |
| Smaller additions | A keyboard shortcuts sheet (⌘/); > starts a block quote; drag to reorder attachments; the Bot opens links before sending them and leaves out broken ones; the first email a Bot sends to someone new includes a one-click unsubscribe link; browser sign-in waits up to 20 minutes | Quality-of-life; the link check means fewer dead links in replies |

Sources: https://x.ai/changelog/bot#v0.75.2, https://cursor.com/help/grok-bot/pages, https://docs.x.ai/grok-bot/files-and-results

## 0.71.2 (October 14): notifications and bigger attachments

The October 14 entry covers 0.71.0 to 0.71.2. Its notification and attachment changes need Grok Bot 0.70.2 or later.

| Area | What the changelog says | What it means for you |
| --- | --- | --- |
| Notifications | While you use Grok Bot on a Mac or Windows PC, Bot replies and questions notify you there instead of your phone | Fewer duplicate pings while you are at your desk |
| Attachments | Files up to 250 MB and videos up to 1 GB; up to 20 attachments per message instead of 6, with a 200 MB total | The docs.x.ai files page still listed the older six-attachment limit when we checked on October 25 |
| Skills | Bots can use up to 200 skills from your installed plugins instead of 24 | Large plugin bundles no longer get cut short |
| Tagged email addresses | Bots can send from a tagged form of their address, like name+shop@, and a routine on that tag runs only for its mail | Give each sign-up or vendor its own tag and its own routine |
| Forms and checkout | Forms can arrive with known fields filled in; at checkout, Bots use card details or photos you send in chat and ask only for what is missing in a Secure Form | Sending a card photo in chat is now a supported path, so think before you do it |
| Computer | Grok Bot opens while the Bot's computer is starting; clicking the asleep preview wakes it in place; when its disk runs low the Bot names the biggest files and deletes them only if you agree | Less waiting, and no silent clean-ups |
| Team admins | Admins can turn off Messaging between Bots under Bot capabilities; Enterprise admins can recreate, terminate or delete members' computers from Manage Bot Computers or the Admin API | See [our Shared Bots guide](https://www.grokbotwiki.com/guides/grok-bot-team-bots) |
| Fixes | Connector calls wait up to two minutes instead of one; a routine that needs to sign in asks you in chat at that step instead of stopping quietly; Stop also ends background subagents and expires their pending approval cards | Fewer silent failures in unattended work |

Sources: https://x.ai/changelog/bot#v0.71.2, https://docs.x.ai/grok-bot/files-and-results

## 0.69.0 to 0.70.2 (October 11): email, X search and in-chat apps

The changelog's October 11 entry, titled Bot email addresses, X search, and in-chat apps, covers five versions at once (0.69.0, 0.69.1, 0.70.0, 0.70.1 and 0.70.2) and does not say which change landed in which version, so the rows below are grouped by topic. The descriptions paraphrase the changelog; the right-hand column is our reading of what each means in practice.

| Area | What the changelog says | What it means for you |
| --- | --- | --- |
| Bot email address | Bots can claim their own email address and receive mail there; mail sent from it waits for your approval on a draft card | A Bot can sign up for things or collect receipts without touching your own inbox. Cursor's help says the address is at mail.grokbot.com, one per account, and permanent |
| X search | Bots can search X and read posts and profiles without you connecting an X account | Research on public X works out of the box. The docs say it is read-only; your DMs, bookmarks and home timeline still need the X plugin |
| In-chat apps | Connectors that come with an app, such as Figma, Notion and Canva, can show it as an interactive card in the chat | You can work with some connected apps without leaving the conversation |
| Payments | Bots can pay with X Money or Stripe Link | Keep purchases behind an Ask first rule; the notes do not describe limits or a separate approval for these payments |
| Templates | Bots can find a Bot template that fits what you describe and link it in chat | A way back to templates from inside the app, after they moved to the web in 0.67.0. Check a template before adding it |
| New plugins | Adding Glean asks for your Glean MCP URL and connects after you sign in to Glean in the browser; QuickBooks Online is available to connect | Have your company's Glean MCP URL ready before you add it |
| Pages | Canvases and documents are both labeled Page; you can rename a page from its title and search it with Cmd/Ctrl+F; shared pages get a title bar with Download (a PDF), Try Grok Bot for visitors and Share for the owner | One name for what Bots make for you, and an easy PDF copy of a shared page |
| Shared Bots | Teammates can approve a Shared Bot's Auto-review requests, including Always allow, from their own DM with it | Approvals no longer have to wait for the owner. Cursor's Team Bots help, checked October 14, still says a Shared Bot asks only in its owner's chat |
| Computer view | Full-screen computer view opens in Watching until you press Take control; an asleep computer shows a Wake button on the Computer tab; Computer settings separate Your computer from the Bot's computer | Opening the screen no longer risks a stray click on the Bot's work |
| Routines | After you save a routine, the Bot sums up what it does and who receives the result, and each run delivers there | Read that summary: it is the quickest check that the routine will report where you expect |
| Smaller additions | On a Mac, View → View Unread shows only Bots with unread messages; Bots can save a web page as PDF and send MP3, M4A or WAV audio; Bots acknowledge your message before longer work; selecting text shows an Add to chat pill; typing # no longer opens the pull request picker | Mostly quality-of-life; the acknowledgement makes it clearer that a Bot has started |

Sources: https://x.ai/changelog/bot, https://cursor.com/help/grok-bot/agent-email, https://docs.x.ai/grok-bot/computer-and-apps, https://cursor.com/help/grok-bot/shared-bots

## Two new approval checks, and what they don't cover

The October 11 entry lists two safety changes under Improved. Before an action it cannot undo, such as sending, posting, buying or deleting, a Bot now checks your own messages for your approval. And after a bank or brokerage connector returns data, the Bot asks before sharing that data anywhere else.

Both are welcome, but neither replaces the controls you set. The notes describe a Bot checking the conversation, not a new setting, so keep Ask first rules on sending, purchasing, deleting and publishing, especially now that Bots can pay with X Money or Stripe Link. The notes also do not mention the October 5 forum report of a Secure Form password appearing in a page snapshot, and the thread still had no Cursor update since October 5 when we checked on October 25, so we still advise typing passwords on the Bot's screen yourself. The approval model changed again in 0.75.5; see that section above. Our [permission boundaries guide](https://www.grokbotwiki.com/guides/permission-boundaries) has the worksheet.

Sources: https://x.ai/changelog/bot, https://forum.cursor.com/t/grok-bot-browser-snapshot-shows-a-password-filled-by-the-secure-form-requestuserform-in-plain-text/173748

## Fixes in 0.69.0 to 0.70.2 worth knowing

Connectors: the changelog says connector calls fail less often, with fixes for wrongly shaped arguments, Notion links and Slack channel names. A rate-limited connector now makes the Bot wait for the retry delay instead of looping, and Slack, Gmail and Outlook drafts retry through temporary rate limits and say if they still could not send. Gmail drafts use your default send-as address and your own signature. Giving a Bot a connector link installs the matching catalog plugin when there is one, and plugins installed from chat or the web are ready on the Bot's computer. Bots no longer sign you out of a connector while repairing it.

The computer and the app: opening a file while the computer is asleep wakes it, while switching chats or focusing the window no longer does; publishing, sharing, deleting a Bot and adding one from a template work while the computer is asleep or unreachable. Files and images from the Bot's computer arrive ahead of question cards, search finds message text and attachment names in all chats, all-day calendar events stay on the right date, pinned Bots sync between desktop and phone, and a crash loop now offers reload or quit. On Linux the app stays responsive and can quit while a notification is showing. If a model is unavailable in your region, the turn stops and explains, and Bots fall back to Grok. Usage & Billing now names your plan and labels the meter's percentage as used.

Sources: https://x.ai/changelog/bot

## Outside the changelog: a subscription, case studies, partners and a rename

By October 28 the official documentation had renamed Team Bots. docs.x.ai now has a Shared Bots page in place of its Team Bots page, every other docs page says shared Bot, and Cursor's Team Bots help address redirects to a Shared Bots page; the changelog entry of October 26 still says Team Bot, so expect both names for a while. The same day's docs added a Vault and secure sign-in page, and SpaceXSI's X Subscription docs added a referral program for Grok Bot, which our [plan guide](https://www.grokbotwiki.com/guides/grok-bot-which-plan) covers. On October 27 SpaceXSI published a second case study, this time from its own sales team: three Shared Bots, Account Intel Bot for prospecting and Salesforce updates, Quote Bot for proposals and order forms, and Deal Bot for non-standard terms, each acting with the user's own permissions, with rate limits on bulk changes, human review for customer-facing messages, and a preview before anything changes in Salesforce. It is SpaceXSI's account of its own setup, not a result we measured; our [Shared Bots guide](https://www.grokbotwiki.com/guides/grok-bot-team-bots) covers the same controls.

On October 12 SpaceXSI announced The X Subscription, one plan bringing together Grok, Grok Bot, Cursor and X Premium; our [plan and pricing guide](https://www.grokbotwiki.com/guides/grok-bot-which-plan) covers what it means for access. Around the same time, docs.x.ai's computer and apps page started describing searching and reading public X without an X account.

On October 20 SpaceXSI described how its own support team uses two Grok Bot teammates. IncidentWatch reviews the previous 15 minutes of tickets every five minutes and alerts the on-call support engineer to a spike that is not a known incident. IncidentSweep handles the follow-up: an engineer says which tickets to consider and the exact message, the Bot sets aside tickets it cannot confidently connect, shows the batch and message for approval, then sends in small batches and stops on failure. SpaceXSI says it cleared 204 tickets in about 10 minutes on September 18 with an engineer approving the batch. That is SpaceXSI's account of its own setup, not a result we measured, but the pattern of showing the batch, getting one approval and adding nothing afterwards is a good template for any bulk action. On October 22 SpaceXSI also announced a Partner Network for companies that deploy the Grok platform or build plugins and integrations for it.

Sources: https://docs.x.ai/grok-bot/shared-bots, https://docs.x.ai/grok-bot/vault, https://docs.x.ai/x-subscription/referral-program, https://x.ai/news/grok-bot-sales, https://docs.x.ai/grok-bot/computer-and-apps, https://x.ai/news/x-subscription, https://x.ai/news/incident-sweep, https://x.ai/news/partnernetworkannouncement

## October 7 to 11: three features in the docs, and outages

Between the 0.68.1 release and the October 11 entry, the help pages picked up three features. Bots can now have their own email address at mail.grokbot.com: one per account, it cannot be renamed or deleted, and on a team an admin has to turn it on first. A seat on a self-serve Grok Business plan now includes Grok Bot, through Sign in with Grok rather than linking a subscription. And tagging @bot under a post on X hands that post to your main Bot, which is not yet available to X accounts based in the EU, UK, Australia, Iceland, Liechtenstein or Norway.

The week also brought outages rather than releases. On October 8 a model capacity limit and errors in one region made Bots fail to reply for parts of the day, and routines were held back or marked Failed; missed runs are not replayed. Our [status guide](https://www.grokbotwiki.com/guides/is-grok-bot-down) lists each incident with its times, and the [routines guide](https://www.grokbotwiki.com/guides/grok-bot-routines-not-running) covers what to do about the missed runs. The maker also changed its branding from SpaceXAI to SpaceXSI; the product name is unchanged.

Sources: https://x.ai/changelog/bot, https://cursor.com/help/grok-bot/agent-email, https://cursor.com/help/grok-bot/supergrok, https://docs.x.ai/grok-bot/tag-on-x, https://status.x.ai/history

## Connect Apps replaces Marketplace in the app

The in-app Marketplace changed in three steps. On September 26 (0.60.0) its sidebar button became Connect apps. On September 29 (0.63.0) it started focusing on plugins: Featured Bots and Bot search results no longer appear, and the search box reads Search plugins. On October 2 (0.67.0) the changelog says Marketplace is now Connect Apps, with category chips under the search, Recommended for you first, and Bot templates on the web.

In practice: install and authenticate plugins from Connect Apps, and find Bot templates on the [web Marketplace](https://x.ai/bot/marketplace) or through a share link. Adding a plugin that needs a sign-in, such as Gmail, now starts that sign-in right away (0.63.0), and since 0.68.0 the command palette also finds plugins. Our [plugins, connectors and MCP guide](https://www.grokbotwiki.com/guides/grok-bot-plugins-mcp) explains how the pieces fit.

Sources: https://x.ai/changelog/bot

## The app now updates itself

Version 0.65.0 turned Automatic Updates on by default: Grok Bot restarts to apply an update while you are away, and you can turn that off in Settings → Updates. Version 0.66.0 made update downloads resume after your computer sleeps, and on a Mac a copy running from a disk image or the Downloads folder now offers Move to Applications. Since 0.67.0, Stop in Settings stops every running chat so a pending update can go ahead.

This is the desktop app. Grok Bot's cloud computer has its own Update control in Settings → Updates, and the troubleshooting advice in our [not-responding guide](https://www.grokbotwiki.com/guides/grok-bot-not-responding) still applies to it.

Sources: https://x.ai/changelog/bot

## A primary Bot that offers to help

Version 0.66.0 introduces proactivity for your primary Bot, the one marked with a star: it will now spot work it can take off your plate and offer to handle it. The note says it needs Grok Bot 0.59.0 or later. Version 0.68.0 adds that Shared Bots no longer appear in the primary Bot picker and cannot be a primary Bot.

An offer is not an action; check what it proposes the same way you would check any new task, especially anything that sends, buys or deletes. Our guide to [permission boundaries](https://www.grokbotwiki.com/guides/permission-boundaries) has a short worksheet for that.

Sources: https://x.ai/changelog/bot

## Email: send-as, formatting and fewer Gmail failures

Version 0.68.0 lets email drafts go out from a verified Gmail send-as address, with a From picker when you have more than one, and Gmail draft cards now include your signature. Version 0.68.1 lets Bots send formatted emails from a draft card, search your Gmail Spam folder and move a message back to the inbox, and says Gmail actions fail less often: send and reply no longer report a missing tool, and Bots wait out Google's rate limits.

Version 0.64.0 added a switch on email and Slack draft cards, Disable drafts for this Bot, after which that Bot sends messages directly. Leave drafts on for anything you have not watched the Bot do correctly several times; you can ask the Bot to turn drafts back on. Our [Gmail and Google Workspace guide](https://www.grokbotwiki.com/guides/grok-bot-gmail-google-workspace) covers setup and the known issues.

Sources: https://x.ai/changelog/bot

## Shared Bots: managers, Slack approvals and voice

Shared Bots arrived in 0.61.0 on September 26, and SpaceXSI announced them on September 28 as a public beta on Teams and Enterprise plans. The October releases fill in gaps. In Slack threads, a Shared Bot that needs your approval posts a Review an action card only you can answer (0.63.0). The creator of a published Shared Bot can add Managers who can change its profile, skills, plugins, secrets and Slack app (0.64.0). Teammates can start a voice chat with a Shared Bot (0.65.0). A Shared Bot 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 (0.68.1).

Our [Shared Bots guide](https://www.grokbotwiki.com/guides/grok-bot-team-bots) covers setup, Slack and admin controls.

Sources: https://x.ai/changelog/bot, https://x.ai/news/team-bots

## Reliability fixes worth knowing about

Several fixes change what you see when something goes wrong. Since 0.63.0, using up your plan's included usage shows the usage limit notice instead of Bot failed to respond, and Settings → Usage & Billing shows your included usage and when it resets. Since 0.66.0, a Bot that hangs on an unresponsive command or computer stops itself with a note, and your next message picks up where it left off. In 0.68.1, Stop or a new message ends a Bot stuck on an unresponsive step within about 30 seconds, and the Bot's browser recovers from a crashed tab and gives up on a stuck page after 25 seconds.

Version 0.68.1 also gives the Bot's computer a 1920 × 1200 screen, up from 1280 × 800, and says Secure Forms fill into the page the Bot has open. Neither its notes nor any release through 0.75.5 mention the October 5 forum report of a password filled by the Secure Form appearing in a page snapshot, so we still advise typing passwords on the screen yourself.

Sources: https://x.ai/changelog/bot, https://forum.cursor.com/t/grok-bot-browser-snapshot-shows-a-password-filled-by-the-secure-form-requestuserform-in-plain-text/173748

## Earlier in September: Projects, Grok 4.7 and Shared Bots

Three September releases set up much of the above. Version 0.57.0 (September 18) lets a Bot start a Project when you ask for one: a Cloud Agent that plans the work and runs its own agents. On September 21 SpaceXSI announced Grok 4.7, saying it was trained to natively understand the Grok Bot harness; the announcement lists availability in Cursor and Grok Build and does not say Grok Bot switched to it. Version 0.61.0 (September 26) introduced Shared Bots, with SpaceXSI's announcement two days later.

Sources: https://x.ai/changelog/bot, https://x.ai/news/grok-4-7, https://x.ai/news/team-bots

## Quick answers

### What is the latest Grok Bot version?

0.78.1, in the changelog entry of October 27, 2026, which also covers 0.78.0. The entry before it, dated October 26, is 0.77.0 and covers 0.76.0; October 24 is 0.75.8 and covers 0.75.6 and 0.75.7; October 23 is 0.75.5; October 22 is 0.75.2, which rolls up 0.72.0 to 0.75.1; October 14 is 0.71.2. Several recent features, such as the Permissions screen, Import Memory, Vault, email forwarding and the Auto-review rule cards, need Grok Bot 0.75.2 or later, and the 1Password change needs 0.68.0 or later.

### What is Vault in Grok Bot?

A place in Settings → Vault, added in 0.75.5 (October 23), where you save logins, cards and contact info so your Bots can sign in and check out for you. Cursor's help says a Bot never sees a saved password, card number or security code, but everything in Vault is available to every Bot on your account, and there is no setting that makes a Bot ask before it uses a saved card. Our [safety guide](https://www.grokbotwiki.com/guides/is-grok-bot-safe) covers the trade-off.

### What are Grok Bot Pages?

Reports, memos, dashboards and trackers a Bot builds for you, which the 0.75.2 changelog entry (October 22) says you edit together or have the Bot keep up to date. A new Page is private until you share it. See [our Pages guide](https://www.grokbotwiki.com/guides/grok-bot-pages).

### Where did Bot templates go in the Grok Bot app?

Out of the app. Version 0.63.0 (September 29) narrowed the in-app Marketplace to plugins, so Featured Bots and Bot search results stopped appearing there. Version 0.67.0 (October 2) renamed it Connect Apps and moved Bot templates to the web, where the [Marketplace at x.ai/bot/marketplace](https://x.ai/bot/marketplace) still lists them. Our [Marketplace and templates guide](https://www.grokbotwiki.com/guides/grok-bot-marketplace-templates) covers the add step.

### What is a primary Bot?

The Bot marked with a star in your sidebar. The 0.66.0 changelog (October 2) says your primary Bot will now spot work it can take off your plate and offer to handle it. Since 0.68.0, Shared Bots cannot be a primary Bot. The changelog does not say how a primary Bot is chosen, so check the star in your own sidebar.

### How do I turn off automatic updates?

In Settings → Updates. Version 0.65.0 (September 30) turned Automatic Updates on by default, so Grok Bot restarts to apply an update while you are away. Turning it off means you install updates yourself from the same screen.

### Does Grok Bot use Grok 4.7?

SpaceXSI has not said so. Its September 21 announcement says Grok 4.7 was trained to natively understand the Grok Bot harness, and lists it as available in Cursor and Grok Build. A Cursor staff member wrote the same day that Grok Bot does not have a model picker and Cursor does not publish which model it is serving; the docs say the serving mix can change.

### Is the Secure Form password problem fixed?

Not confirmed when we checked on October 25. Version 0.71.2 (October 14) says Secure Forms fill fields on more websites, including embedded frames, and 0.75.5 lets a Secure Form save a login to Vault, but none of the notes from 0.68.1 to 0.75.5 mention the October 5 report of a password appearing in a page snapshot, and the forum thread has had no Cursor update since October 5. Until Cursor confirms a fix, type passwords on the Bot's screen yourself; see [our shared-computer guide](https://www.grokbotwiki.com/guides/grok-bot-shared-computer).

### Can Grok Bot have its own email address now?

Yes. Since the October 11 changelog entry (0.69.0 to 0.70.2) Bots can claim an address at mail.grokbot.com; Cursor's help says it is one per account and cannot be renamed or deleted. October brought more: 0.71.2 lets a Bot send from a tagged form such as name+shop@, 0.75.2 lets routines read the Bot's inboxes, and 0.75.5 adds forwarding with the original formatting, images and attachments. Since 0.75.5, an email you ask for in chat goes out once Auto-review allows it, while mail from a routine still waits as a draft. See [our Gmail guide](https://www.grokbotwiki.com/guides/grok-bot-gmail-google-workspace).

## Sources

- [The X Subscription docs: referral program](https://docs.x.ai/x-subscription/referral-program)
- [Grok Bot changelog (x.ai/changelog/bot)](https://x.ai/changelog/bot)
- [Grok Bot changelog: 0.78.1, shopping cards and subscription templates (October 27)](https://x.ai/changelog/bot#v0.78.1)
- [Grok Bot changelog: 0.77.0, Permissions, Vault payments and question cards (October 26)](https://x.ai/changelog/bot#v0.77.0)
- [Grok Bot docs: Vault and secure sign-in](https://docs.x.ai/grok-bot/vault)
- [Grok Bot docs: Shared Bots (the docs' new name for Team Bots)](https://docs.x.ai/grok-bot/shared-bots)
- [SpaceXSI: Your next sales teammate should be a Grok Bot (October 27, 2026)](https://x.ai/news/grok-bot-sales)
- [Grok Bot changelog: 0.75.8, Auto-review rule cards and smarter connectors (October 24)](https://x.ai/changelog/bot#v0.75.8)
- [Grok Bot changelog: 0.75.5, Vault, email forwarding and fewer approval cards (October 23)](https://x.ai/changelog/bot#v0.75.5)
- [Grok Bot changelog: 0.75.2, Pages, new chat cards and video creation (October 22)](https://x.ai/changelog/bot#v0.75.2)
- [Grok Bot changelog: 0.71.2, smarter notifications and larger file attachments (October 14)](https://x.ai/changelog/bot#v0.71.2)
- [Cursor help: Pages](https://cursor.com/help/grok-bot/pages)
- [Cursor help: store secrets securely (Vault)](https://cursor.com/help/grok-bot/secrets)
- [Cursor help: routines (run limits)](https://cursor.com/help/grok-bot/routines)
- [Grok Bot docs: files and results (Pages)](https://docs.x.ai/grok-bot/files-and-results)
- [SpaceXSI: Using Grok Bot to detect and respond to incidents (October 20, 2026)](https://x.ai/news/incident-sweep)
- [SpaceXSI: Introducing the SpaceX Super Intelligence Partner Network (October 22, 2026)](https://x.ai/news/partnernetworkannouncement)
- [Grok Bot changelog RSS feed](https://x.ai/changelog/bot/rss.xml)
- [Cursor help: agent email for Grok Bot](https://cursor.com/help/grok-bot/agent-email)
- [Cursor help: Grok Bot with SuperGrok and Grok Business](https://cursor.com/help/grok-bot/supergrok)
- [Grok Bot docs: tag @bot on X](https://docs.x.ai/grok-bot/tag-on-x)
- [Grok Bot docs: search and read X (computer and apps)](https://docs.x.ai/grok-bot/computer-and-apps)
- [Cursor help: Shared Bots (approvals)](https://cursor.com/help/grok-bot/shared-bots)
- [SpaceXSI: Introducing The X Subscription (October 12, 2026)](https://x.ai/news/x-subscription)
- [Cursor status history](https://status.x.ai/history)
- [SpaceXSI: Team Bots (September 28, 2026)](https://x.ai/news/team-bots)
- [SpaceXSI: Introducing Grok 4.7 (September 21, 2026)](https://x.ai/news/grok-4-7)
- [Forum: share your thoughts on Grok 4.7 (staff reply on Grok Bot's model, September 21)](https://forum.cursor.com/t/share-your-thoughts-on-grok-4-7/172527)
- [Forum: password filled by the Secure Form shown in a page snapshot (staff reply, October 5)](https://forum.cursor.com/t/grok-bot-browser-snapshot-shows-a-password-filled-by-the-secure-form-requestuserform-in-plain-text/173748)

---

# Grok Bot glossary: Bots, routines, skills, plugins and more

> Plain-English definitions of Grok Bot terms: Bot, primary Bot, Shared Bot, computer, routine, skill, plugin, agent email, @bot, Auto Review, usage and more.

- Canonical page: https://www.grokbotwiki.com/guides/grok-bot-glossary
- Sources checked: 2026-10-29
- Evidence: Definitions paraphrased from the official docs, Cursor help and changelog, checked October 11, 2026; changelog entry 0.78.1 read October 29; changelog entry 0.77.0 and docs.x.ai's Shared Bots and Vault pages read October 28; changelog entry 0.75.8 read October 27; docs, Cursor help (email, secrets, routines, plans) and The X Subscription docs rechecked October 25, 2026 with the changelog through 0.75.5 · terms the docs do not define are marked. Suggested workflows have not been independently tested.
- Publisher: Grok Bot Wiki, an independent guide not affiliated with SpaceXSI, xAI or X.

## How to use this glossary

Grok Bot's vocabulary is small but slippery: the same thing can be a plugin or a connector, Marketplace became Connect Apps, and some new words, such as primary Bot, appear in the changelog before the docs. Each definition below paraphrases the official docs or Cursor's help as of October 25, 2026; where a term is only in the changelog, we say so.

Sources: https://docs.x.ai/grok-bot/computer-and-apps, https://x.ai/changelog/bot

## Bots

The things you create and talk to. Every Bot on an account shares one computer, so the roles below organize work; they are not security boundaries.

| Term | What it means |
| --- | --- |
| Bot | A durable AI teammate with a name, a job, its own conversation and working context that develops over time |
| Primary Bot | The Bot marked with a star in your sidebar; since 0.66.0 it can offer to take work off your plate. Changelog term, not yet in the docs |
| Helper Bot | A Bot that one of your Bots created to help with its work (Cursor's help) |
| Shared Bot (formerly Team Bot) | One Bot your whole team talks to, each person in a private chat; set up and shared by its owner. The official docs renamed it Shared Bot by October 28, 2026, while the changelog of October 26 still says Team Bot. See [Shared Bots](https://www.grokbotwiki.com/guides/grok-bot-team-bots) |
| Manager | A teammate the owner of a shared Bot lets change its setup (instructions, skills, memory, apps, secrets, Slack app); deleting stays with the owner. A Collaborator can only chat with it |
| Import Memory | Since 0.77.0 (October 26), a Settings option that brings your preferences and context from another AI assistant into your primary Bot; needs Grok Bot 0.75.2 or later (changelog) |
| Group chat | A conversation with two to six Bots working toward one shared outcome, with visible handoffs |
| Duplicate | A copy of a Bot inside your account with its profile, settings, skills, routines and avatar, but not its conversation history or learned memory |
| Template | A shareable recipe for a Bot: its identity, description, skills and routines, opened from a link or the web Marketplace. Never includes your computer, logins or history |

Sources: https://docs.x.ai/grok-bot/bots, https://docs.x.ai/grok-bot/shared-bots, https://docs.x.ai/grok-bot/chat-and-collaboration, https://cursor.com/help/grok-bot/how-to, https://x.ai/changelog/bot

## The computer

Where Bots do their work. Our [shared-computer guide](https://www.grokbotwiki.com/guides/grok-bot-shared-computer) covers what this means for logins and context.

| Term | What it means |
| --- | --- |
| Computer (Agent Computer) | The persistent cloud computer your Bots work on, with a browser, command line, files and connected tools. One per user, shared by all of that user's Bots |
| /workspace | The shared folder on the computer where Bots keep durable project files; every Bot on the account can read it |
| Take over (Open the screen) | Controlling the Bot's computer yourself, for example to type a password, complete two-factor sign-in or a CAPTCHA, then handing control back |
| Watching, Take control | Since the October 11 changelog entry (0.69.0 to 0.70.2), full-screen computer view opens in Watching, where you only look, until you press Take control. Changelog terms |
| Wake | Waking the Bot's computer when it is asleep. Since 0.71.2 (October 14) you click the Computer is asleep preview to wake it in place, replacing the separate Wake button; opening a file or a voice call from your phone also wakes it, and switching chats does not (changelog) |
| Recover, Update, Reset | Computer recovery controls, in that order. Recover and Update keep durable files and logins; Reset restores the last saved snapshot and can lose recent work |
| Execution on Local Computer | The setting that lets Bots run commands on the computer in front of you: Ask every time (default), Always allow or Never allow |

Sources: https://docs.x.ai/grok-bot/computer-and-apps, https://docs.x.ai/grok-bot/security-faq, https://docs.x.ai/grok-bot/approvals-security-and-privacy, https://x.ai/changelog/bot

## Work and automation

How a one-off task becomes repeatable work.

| Term | What it means |
| --- | --- |
| Skill | A reusable set of instructions for how to do a task. Private skills are one library shared by all your Bots; type / to use one. Since 0.71.2 a Bot can use up to 200 skills from your installed plugins, up from 24 |
| Teach a task | Recording up to ten minutes of your own computer work so the Bot can draft a skill from it; not available on mobile |
| Routine | An instruction telling one Bot when to run a workflow, on a schedule or after an event. A Bot can own up to 50. Since 0.75.5 your routines can run up to 300 times an hour in total and each up to 200 times an hour |
| Test run | Running a routine now to check it. It performs real work, so use safe inputs |
| Event trigger | A routine that starts from something happening, such as a Slack message, a GitHub notification, a webhook call or mail arriving at your Bots' email address |
| Page | A styled report, memo, dashboard or tracker a Bot builds for you, which you can edit together or have the Bot keep up to date, including from a routine. Canvases and documents have been labeled Page since the October 11 changelog entry, and Pages became a headline feature in 0.75.2 (October 22). You can rename one from its title, and a shared Page has Download (PDF) and Share. Self-serve users can share a Page publicly; the dashboard's Pages section lists the ones you shared, where you can unshare or delete them |
| Library, Pinned | The Library lists your past Pages, files and links. Since 0.75.2 you can pin items to a Pinned section that stays at the top and syncs across your devices |
| Video creation | Since 0.75.2, Bots can create videos from a description or from an image you share (changelog) |
| X search | Searching and reading what is public on X (posts, profiles, mentions, trends) without connecting an X account. Read-only; DMs, bookmarks and your home timeline need the X plugin |
| @bot on X | Tagging @bot in an X post to hand that post to your main Bot as a task; @bot replies on X only with a confirmation. Not yet available to X accounts based in the EU, the UK, Australia and a few other countries |
| Project | A Cloud Agent that plans the work and runs its own agents, which a Bot can start when you ask (changelog 0.57.0) |
| Cloud Agent | Cursor's coding agent, running on separate computers; Bots can hand coding tasks to one, billed to your Cursor plan |

Sources: https://docs.x.ai/grok-bot/skills-routines-and-automations, https://cursor.com/help/grok-bot/how-to, https://x.ai/changelog/bot, https://docs.x.ai/grok-bot/teams-and-enterprises, https://cursor.com/help/grok-bot/agent-email, https://docs.x.ai/grok-bot/tag-on-x, https://docs.x.ai/grok-bot/computer-and-apps, https://docs.x.ai/grok-bot/files-and-results, https://cursor.com/help/grok-bot/routines

## Apps, sign-ins and secrets

How Bots reach your other tools. See [plugins, connectors and MCP](https://www.grokbotwiki.com/guides/grok-bot-plugins-mcp) for the full picture.

| Term | What it means |
| --- | --- |
| Plugin (connector) | A structured connection to a service such as Gmail, Slack or Notion. Installed once, available to every Bot on the account; its tokens stay on Cursor's backend |
| Connect Apps | Where you find and install plugins; called Marketplace until 0.67.0 (October 2). Open it from the sidebar or with Cmd/Ctrl+Shift+M. Bot templates moved to the web Marketplace at x.ai/bot/marketplace |
| Agent email (Bot email address, Email plugin) | An address at mail.grokbot.com that your Bots use to receive, search, send and, since 0.75.5, forward mail. One per account, shared by all your Bots, and permanent: it cannot be renamed or deleted. Email you ask for in chat goes out once Auto-review allows it; email from a routine or any other turn waits on a draft card until you press Send. Since 0.71.2 a Bot can also send from a tagged form such as name+shop@. On a Cursor team, an admin turns it on first |
| Custom MCP server | A Model Context Protocol server you add yourself by asking a Bot in chat; it must be reachable over public HTTPS |
| Secret request | A secure card for entering a key or token; the value is masked, kept out of the transcript and not shown to the model |
| Secure Form | The in-chat form a Bot shows when a web page needs you to type something, which it fills into the page. In October a password filled this way appeared in a page snapshot, with no fix confirmed by October 14; see [Is Grok Bot safe?](https://www.grokbotwiki.com/guides/is-grok-bot-safe) |
| 1Password | An integration, connected from the app on a Mac since 0.53.0, that lets a Bot sign in with your saved logins, asking first unless you turn on Auto fill. Since 0.77.0 (October 26) it connects without a shared vault: you approve each login in 1Password, which fills it without the Bot seeing it |
| Vault | Since 0.75.5 (October 23), Settings → Vault on desktop and the phone stores logins, cards and contact info so a Bot can sign in or check out without seeing a saved password, card number or security code. Needs Grok Bot 0.75.2 or later, covers every Bot on your account, and is not supported on shared Bots. Since 0.77.0 it also has a Payments tab with Payment accounts and a Default payment method, and each entry has a Hints field; since 0.78.1 (October 27) Shop Pay connects from that Payments tab too |
| Shop Pay | A checkout option since 0.75.2: Bots pay through Shop checkout where a store accepts it, or with a one-time Shop card elsewhere (changelog) |

Sources: https://x.ai/changelog/bot#v0.78.1, https://docs.x.ai/grok-bot/computer-and-apps, https://docs.x.ai/grok-bot/security, https://docs.x.ai/grok-bot/approvals-security-and-privacy, https://docs.x.ai/grok-bot/chat-and-collaboration, https://cursor.com/help/grok-bot/connect-apps, https://cursor.com/help/grok-bot/secrets, https://cursor.com/help/grok-bot/agent-email, https://x.ai/changelog/bot

## Approvals and safety

What stops a Bot before it acts. Our [permission boundaries guide](https://www.grokbotwiki.com/guides/permission-boundaries) turns these into a worksheet.

| Term | What it means |
| --- | --- |
| Approval card | A card in the chat showing a proposed action, with Allow once, Always allow (which can save a rule) and Deny. Since 0.75.2, Auto-review cards describe the action in one sentence, name the app with its logo and flag irreversible or sensitive changes; since 0.75.5, after you deny one the Bot does not try that action again until you send another message |
| Auto Review | An independent review model that checks risky actions, such as shell commands, plugin calls and computer use, before they run. Since 0.75.8 it takes a second look before showing an approval card, so fewer safe actions need one |
| Ask first rule | A rule that always stops matching actions for you. If it and an Allow automatically rule both match, Ask first wins |
| Custom Rules | What Settings calls your saved approval rules since 0.68.0. Since 0.75.8, a Bot can offer to add, change or remove one of them on a card in the chat that you confirm |
| Permissions | Since 0.77.0 (October 26), the Settings section that lists your Auto-review rules under Always Ask and Allow without Asking, each with an Add Rule button; approval cards now stay open for 30 minutes instead of 10 |
| Draft card | An editable email or Slack message a Bot prepares for you to send or discard; can be switched off per Bot since 0.64.0. Since 0.75.5, sends you ask for in chat go out once Auto-review allows them, while sends on routine and other turns still wait as drafts |
| Privacy Mode | Cursor's data setting under which customer data is not used for training. Legacy Privacy Mode, which stores nothing, does not work with Grok Bot |

Sources: https://docs.x.ai/grok-bot/approvals-security-and-privacy, https://docs.x.ai/grok-bot/security, https://docs.x.ai/grok-bot/faq, https://x.ai/changelog/bot, https://cursor.com/help/grok-bot/agent-email

## Usage and plans

How Grok Bot is paid for. Since October 12, 2026 new customers buy The X Subscription; existing Cursor and SuperGrok plans continue. Prices are in our [plan and pricing guide](https://www.grokbotwiki.com/guides/grok-bot-which-plan).

| Term | What it means |
| --- | --- |
| The X Subscription | SpaceXSI's single plan for Grok, Grok Bot, Cursor and X Premium benefits, launched October 12, 2026. Grok Bot is included on Premium, Super and Ultra, and on Teams and Enterprise, not on Free or Plus |
| Legacy plan | Cursor's name for the plans it sold before The X Subscription, such as Pro, Pro+, Ultra and Teams Standard and Premium seats. They keep working unless you switch |
| Shared weekly pool | On The X Subscription, one weekly allowance per paid seat that covers Grok, Grok Bot and Cursor use together |
| Top-up and Additional Usage | On The X Subscription, prepaid credit that pays for use beyond the weekly pool and for third-party models in Cursor. Auto Top-up is off unless you turn it on |
| Monthly additional usage limit | On The X Subscription, the spending cap on Additional Usage in a calendar month; SpaceXSI's docs call it the hard stop |
| Unify (switch) | Combining existing Cursor, Grok and X accounts under The X Subscription. Optional and permanent; old web subscriptions are refunded pro rata |
| Weekly usage | On the existing plans, the included Grok Bot allowance, measured in agent steps and tokens, which resets weekly |
| On-demand usage | On the existing Cursor plans, extra usage after weekly usage runs out, billed through Cursor, only if you enable it |
| On-demand monthly limit | The cap on on-demand usage, the same as Monthly Limit under Spending on cursor.com. A run in progress can finish past it |
| Usage-credit trial | Cursor's free trial: a usage credit with a 7-day window that never becomes a paid plan |
| SuperGrok link | Connecting an individual SuperGrok or X Premium+ subscription to grant Grok Bot usage to your Cursor account. Permanent, and it does not stack with a Cursor plan; SuperGrok and X Premium+ are the same tier as Pro |
| Grok Business seat | A seat on a self-serve Grok Business plan, which includes Grok Bot. You use it by choosing Sign in with Grok, not by linking. Since 0.75.5, if a seat does not cover Grok Bot yet, the usage limit message says to ask your Grok Business admin to connect your team |

Sources: https://docs.x.ai/x-subscription/overview, https://docs.x.ai/x-subscription/usage-limits, https://docs.x.ai/x-subscription/spending-caps, https://cursor.com/help/grok-bot/plans, https://cursor.com/help/grok-bot/supergrok, https://x.ai/bot, https://cursor.com/docs/account/pricing/legacy-cursor-plans, https://x.ai/changelog/bot

## Quick answers

### What is the difference between a skill and a routine?

A skill is a reusable set of instructions for how to do a task; a routine tells one Bot when to run a workflow, on a schedule or after an event. Save the method as a skill first, then add a routine when the task should run on its own. See [skills vs routines](https://www.grokbotwiki.com/guides/skills-vs-routines).

### Are a plugin and a connector the same thing?

Yes, in practice. The docs say connectors are installed as plugins, and the app calls them plugins. They live in Connect Apps, which was called Marketplace before version 0.67.0 (October 2).

### What is a primary Bot?

The Bot marked with a star in your sidebar. The 0.66.0 changelog (October 2) says it will now spot work it can take off your plate and offer to handle it. The docs do not define the term yet, and since 0.68.0 a Shared Bot cannot be a primary Bot.

## Sources

- [Grok Bot docs: Vault and secure sign-in](https://docs.x.ai/grok-bot/vault)
- [Grok Bot changelog: 0.78.1 (October 27)](https://x.ai/changelog/bot#v0.78.1)
- [Grok Bot changelog: 0.77.0 (October 26)](https://x.ai/changelog/bot#v0.77.0)
- [Create and manage Bots](https://docs.x.ai/grok-bot/bots)
- [Shared Bots (formerly Team Bots)](https://docs.x.ai/grok-bot/shared-bots)
- [Message and collaborate: group chats](https://docs.x.ai/grok-bot/chat-and-collaboration)
- [Computer and apps](https://docs.x.ai/grok-bot/computer-and-apps)
- [Skills and routines](https://docs.x.ai/grok-bot/skills-routines-and-automations)
- [Approvals, security and privacy](https://docs.x.ai/grok-bot/approvals-security-and-privacy)
- [Grok Bot security](https://docs.x.ai/grok-bot/security)
- [Grok Bot security FAQ](https://docs.x.ai/grok-bot/security-faq)
- [Grok Bot FAQ](https://docs.x.ai/grok-bot/faq)
- [Teams and enterprises: Cloud Agents](https://docs.x.ai/grok-bot/teams-and-enterprises)
- [Files and results: Pages](https://docs.x.ai/grok-bot/files-and-results)
- [Cursor help: plans and billing](https://cursor.com/help/grok-bot/plans)
- [Cursor help: connect apps](https://cursor.com/help/grok-bot/connect-apps)
- [Cursor help: routines (run limits)](https://cursor.com/help/grok-bot/routines)
- [Cursor docs: legacy Cursor plans](https://cursor.com/docs/account/pricing/legacy-cursor-plans)
- [Cursor help: how-tos (helper Bots)](https://cursor.com/help/grok-bot/how-to)
- [Cursor help: store secrets securely (Vault)](https://cursor.com/help/grok-bot/secrets)
- [Cursor help: give your Bot an email address](https://cursor.com/help/grok-bot/agent-email)
- [Cursor help: link SuperGrok or a Grok Business seat](https://cursor.com/help/grok-bot/supergrok)
- [Grok Bot product page: plans that include Grok Bot](https://x.ai/bot)
- [The X Subscription docs: what is The X Subscription?](https://docs.x.ai/x-subscription/overview)
- [The X Subscription docs: usage limits](https://docs.x.ai/x-subscription/usage-limits)
- [The X Subscription docs: spending caps](https://docs.x.ai/x-subscription/spending-caps)
- [Tag @bot on X](https://docs.x.ai/grok-bot/tag-on-x)
- [Grok Bot changelog](https://x.ai/changelog/bot)

---

# Grok Bot alternatives in 2026: OpenClaw, Hermes, Manus, more

> Eight Grok Bot alternatives compared from their own docs and pricing pages: OpenClaw, Hermes Agent, Manus, ChatGPT dots, Claude, Rakazo, MausBot, gawkbot.

- Canonical page: https://www.grokbotwiki.com/guides/grok-bot-alternatives
- Sources checked: 2026-10-29
- Evidence: Every cited product page, README, license and pricing page rechecked October 29, 2026, along with docs.x.ai's overview, FAQ and security pages, Cursor's plan and routines help, SpaceXSI's announcement posts and the Marketplace; x.ai/bot, x.ai/pricing and the Grok Bot changelog refused our automated check on October 29, so Grok Bot's Super and Ultra figures and October features rest on our October 25 and 27 reads · documentation comparison, no head-to-head run · GitHub star counts as of October 29. Suggested workflows have not been independently tested.
- Publisher: Grok Bot Wiki, an independent guide not affiliated with SpaceXSI, xAI or X.

## The short answer

Grok Bot's alternatives split into two groups. Hosted always-on agents, ChatGPT's dots, Manus and Claude, suit people who want nothing to run. Self-hosted platforms, OpenClaw, Hermes Agent, Rakazo, MausBot and gawkbot, suit people who want model choice and their own hardware. None imports Grok Bot templates; the written brief is what moves.

This is a documentation comparison, first checked on October 7, 2026 against each product's own docs, README, license and pricing page and last rechecked October 29. We have not run the same task in all of them, so there is no quality ranking. Grok Bot itself is included with The X Subscription from its $30 Premium plan; x.ai/bot now also lists Super at $100 a month with 3.5 times Premium's usage and Ultra at $200 with 12 times. Cursor's plan page says legacy Cursor Pro ($20) and linked SuperGrok plans still include it; see [our plan guide](https://www.grokbotwiki.com/guides/grok-bot-which-plan).

| Product | Made by | Where it runs | Model | Entry price (October 2026) |
| --- | --- | --- | --- | --- |
| Grok Bot | SpaceXSI, on Cursor's cloud | One cloud computer per user, shared by all your Bots | Chosen by Cursor; no model picker | The X Subscription Premium, $30 a month (Free and $8 Plus exclude Grok Bot); Super $100 (3.5x Premium usage) and Ultra $200 (12x); legacy Cursor Pro ($20) and linked SuperGrok plans continue |
| ChatGPT dots and Work | OpenAI | Dots: its own cloud computer and browser. Work: cloud, or your desktop | OpenAI models; dots run on GPT-6 Astra | Dots: ChatGPT Pro ($100, $200 or $500 a month) or Business Premium. Work: from the Free plan |
| Claude (with Cowork) | Anthropic | A temporary cloud sandbox per session; local files through Claude Desktop | Claude models | Claude Pro $20 a month, or $17 billed yearly |
| Manus | Manus AI | Hosted; a Cloud Computer for always-on work is sold separately | Manus's own agent tiers, or your own API key through Manus Flex | Free plan; Pro from $20 a month; Team from $20 a seat |
| OpenClaw | OpenClaw Foundation, MIT license | A Gateway on your Mac, Linux, Windows or a VPS | Any provider by API key, a Claude Code or Codex login, or a SuperGrok sign-in | Free software; you pay for models and hosting |
| Hermes Agent | Nous Research, MIT license | Your machine or server, sandbox backends, or hosted Hermes Cloud | Any model: Nous Portal, OpenRouter, OpenAI, your own endpoint | Free software; Nous Portal Plus $20 a month, which includes hosting for one Hermes Cloud agent; larger or extra agents billed daily, plus usage |
| Rakazo | Inbox Zero, Apache 2.0, beta | Docker, E2B, Novita, Daytona, CreateOS, Boat, Railway or local | Your own model credentials | Free software; you pay for models and compute |
| MausBot (OpenMausBot) | Milind Soni, Apache 2.0 except an enterprise folder | Your machine; per-Bot cloud desktop or local VM | Your installed claude, codex or grok CLI, or an API provider such as OpenRouter | Free locally; cloud workspaces $15 to $99 a month (Starter/Pro/Max), team plans from $169; AI usage not included beyond monthly Claude credits on paid tiers |
| gawkbot | Nex, Sustainable Use License | Your machine | Your Claude Code, Codex or Opencode CLI, Ollama, Hermes Agent or OpenClaw | Free for internal or personal use |

Sources: https://docs.x.ai/grok-bot/overview, https://docs.x.ai/grok-bot/security, https://cursor.com/help/grok-bot/plans, https://x.ai/news/x-subscription, https://x.ai/pricing, https://x.ai/bot, https://learn.chatgpt.com/docs/dots, https://learn.chatgpt.com/docs/pricing, https://support.claude.com/en/articles/14479288-claude-cowork-architecture-overview, https://claude.com/pricing, https://help.manus.im/en/articles/11711111-what-is-the-current-membership-pricing-for-manus, https://manus.im/blog/introducing-manus-flex, https://github.com/openclaw/openclaw, https://github.com/NousResearch/hermes-agent, https://portal.nousresearch.com, https://portal.nousresearch.com/cloud, https://github.com/elie222/rakazo, https://mausbot.com/pricing, https://github.com/najmuzzaman-mohammad/gawkbot

## Choose by what you want to stop doing

Most people looking for an alternative want to escape one specific constraint of Grok Bot. Match the constraint to the group that removes it, then read that product's own documentation before you move anything.

| If you want… | Look at | What you give up |
| --- | --- | --- |
| To pick or switch the model | OpenClaw, Hermes Agent, Rakazo, MausBot, gawkbot | A managed computer; you run and update the software |
| Files and logins on hardware you control | OpenClaw, Hermes Agent, MausBot or gawkbot locally | Always-on work stops when your machine sleeps, unless you run a server |
| To talk to the agent in Telegram, WhatsApp, Slack or Discord | OpenClaw or Hermes Agent | Grok Bot's own desktop and mobile apps |
| An approval click before every external write | gawkbot, or MausBot's permission broker | A young, single-maintainer or early project instead of a vendor with support |
| A hosted always-on agent from a vendor you already pay | ChatGPT dots on Pro, or Claude on Pro and Max | Grok Bot's named, long-lived Bots on one shared computer |
| Each task isolated from the others | Claude, which gives each cloud session its own temporary sandbox | Logins that persist across tasks |

Sources: https://docs.openclaw.ai/start/getting-started, https://github.com/NousResearch/hermes-agent, https://github.com/najmuzzaman-mohammad/gawkbot, https://github.com/milind-soni/OpenMausBot, https://learn.chatgpt.com/docs/dots, https://support.claude.com/en/articles/14479288-claude-cowork-architecture-overview

## Stay on Grok Bot if

You want to describe a job and have it running today without a terminal, with Bots that keep working when your laptop is closed and mobile apps that reach the same Bots. You accept that Cursor chooses the model with no picker, that all your Bots share one cloud computer and one set of logins, and that usage is a weekly allowance with paid extra usage beyond it. The docs say isolation is per user, not per Bot.

October's releases narrowed several gaps with the hosted alternatives. Since 0.75.2 (October 22) Bots can build Pages, such as reports, memos and dashboards, that you edit together or have the Bot keep up to date, create videos from a description or an image, and pay with Shop Pay. Since 0.75.5 (October 23) they can save your logins, cards and contact details to a Vault in Settings and fill them in to sign in or check out, and forward an email from their own inbox with its attachments. 0.71.2 (October 14) raised the number of skills a Bot can use from installed plugins from 24 to 200, and routines can now run up to 300 times an hour in total and 200 times each. Saved cards and checkout make the shared-computer caution above matter more, not less.

If a reliability problem is what sent you looking, check [Is Grok Bot down?](https://www.grokbotwiki.com/guides/is-grok-bot-down) first: several September and October incidents were on Cursor's side and resolved without any action from users.

Sources: https://docs.x.ai/grok-bot/overview, https://docs.x.ai/grok-bot/faq, https://docs.x.ai/grok-bot/security, https://x.ai/changelog/bot, https://cursor.com/help/grok-bot/routines

## Hosted alternatives: ChatGPT dots, Claude and Manus

OpenAI's documentation describes a dot as an always-on agent that keeps work moving across your tools; it is powered by GPT-6 Astra, lives in the cloud, and has its own computer and browser. You reach it in ChatGPT, Slack, Microsoft Teams or a call. Access is on the Pro 100, 200 and 500 plans outside the EEA, UK and Switzerland, and rolling out on Business Premium and Enterprise, where it is off by default until an administrator turns it on. Before an action affects your accounts, a review decides whether it can proceed, needs your approval, or must be handed to you. Chatting with a dot does not count toward ChatGPT usage limits, but tasks it starts in Work or Codex do. ChatGPT agent itself is retired in favor of ChatGPT Work; our [three-way comparison](https://www.grokbotwiki.com/guides/grok-bot-vs-chatgpt-vs-claude) covers Work and Claude in more depth. In an October 21 comparison on Composio's blog, which promotes a Composio plugin for Grok Bot, the author Harsh concludes that dots suit people who want one assistant that follows their ChatGPT work, while Grok Bot suits teams that want several specialist Bots that hand work to each other; that is a community report, not our test.

Anthropic merged Cowork into Claude on September 16, rolling out to Pro and Max first, with Team and Free plans to follow. Cloud sessions run on Anthropic's servers, each in its own sandbox that is destroyed when the session ends, and scheduled tasks keep running with your computer off. Claude Pro is $20 a month, or $17 billed yearly.

Manus is a hosted agent that executes tasks and automates workflows. Its help center lists a free plan with 300 daily refresh credits and two scheduled automations, and Pro from $20 a month with 20 concurrent tasks; it says the pricing page is authoritative. Always-on work uses Manus Cloud Computer, a dedicated, persistent cloud machine with its own Basic, Standard and Advanced tiers. Manus 2.0 launched on September 28 with automations that can start from a new email, a Slack message or a Notion update, not only a schedule. Since September 29, Manus Flex lets you run the agent on your own API key from OpenRouter, Fireworks or Modal; the provider bills inference, and the rest of a task still uses Manus credits. Manus says it resumed independent operations on September 1, 2026.

Sources: https://learn.chatgpt.com/docs/dots, https://learn.chatgpt.com/docs/get-started-with-work, https://composio.dev/content/chatgpt-dots-vs-grok-bots, https://claude.com/blog/cowork-is-now-claude, https://support.claude.com/en/articles/14479288-claude-cowork-architecture-overview, https://claude.com/pricing, https://help.manus.im/en/articles/11711111-what-is-the-current-membership-pricing-for-manus, https://manus.im/blog/manus-cloud-computer, https://manus.im/blog/introducing-manus-2-0, https://manus.im/blog/introducing-manus-flex, https://manus.im/blog/manus-resumes-independent-operations

## Self-hosted platforms: OpenClaw and Hermes Agent

OpenClaw is an open-source assistant that runs on your own computer and meets you in the chat apps you already use, including Discord, iMessage, Microsoft Teams, Signal, Slack, Telegram, WhatsApp and 20-plus more, and it has native apps for macOS, iOS, Android, Windows and Linux. It is MIT-licensed, stewarded by the OpenClaw Foundation, and its README says it has no paid tier or hosted service. Models are swappable plugins; setup needs a Claude Code or Codex login or a provider API key. Its docs say a workspace is the default working directory, not a hard sandbox, and sandboxing is off by default. Optional Cloud Workers move a session's coding work onto a disposable remote machine. It had about 393,000 GitHub stars on October 29. Our [Grok Bot vs OpenClaw guide](https://www.grokbotwiki.com/guides/grok-bot-vs-openclaw) goes deeper.

Hermes Agent is Nous Research's MIT-licensed, self-improving agent. It runs on your machine, a server or one of several sandbox backends, works with any model, and talks to you through Telegram, Discord, Slack, WhatsApp, Signal and a command line from one gateway. It has a built-in scheduler and six built-in terminal backends (local, Docker, SSH, Modal, Daytona and Vercel Sandbox), plus plugin backends. Its default approval mode uses a second model to assess risk, auto-denies clearly dangerous commands and escalates uncertain ones to you, and timeouts fail closed. Nous Research's portal lists a free tier, Plus at $20, Super at $100 and Ultra at $200 a month, and lets you connect an eligible ChatGPT account for inference instead. Every paid Nous Portal plan now includes hosting for one always-on Hermes Cloud agent (up to 4 GB of memory on Plus and Super, 8 GB on Ultra); larger sizes and extra agents are billed daily from Nous credit, with inference and tools on top. It had about 258,000 stars on October 29.

Sources: https://github.com/openclaw/openclaw, https://docs.openclaw.ai/start/getting-started, https://docs.openclaw.ai/gateway/sandboxing, https://x.ai/news/grok-openclaw, https://github.com/NousResearch/hermes-agent, https://hermes-agent.nousresearch.com/docs/user-guide/security, https://portal.nousresearch.com, https://portal.nousresearch.com/cloud, https://docs.openclaw.ai/gateway/cloud-workers, https://x.ai/news/grok-hermes

## Open-source look-alikes: Rakazo, MausBot and gawkbot

Rakazo describes itself as an open-source Grok Bot alternative and copies the shape closely: persistent Bots with memory, routines, Bot-to-Bot delegation, and browser, terminal, file and desktop access, through web, desktop and mobile apps. The differences are bring your own model, choose your own sandbox (Docker, E2B, Novita, Daytona, CreateOS, Boat, Railway or local), and run the whole stack yourself. Tools come through Composio, Pipedream, Treg, remote MCP and OpenAPI, and voice through your own ElevenLabs, OpenAI, Cartesia or Fish Audio key. It is Apache 2.0, in beta, from the company behind Inbox Zero; its site says hosted Rakazo Cloud is in beta.

MausBot, formerly OpenMausBot, is a chat app where each Bot drives a command-line agent you already have, claude, codex or grok, with per-Bot model choice; its README also points to setup for OpenRouter, Fireworks AI, DeepSeek, Cline or your own OpenAI- or Anthropic-compatible provider. Each Bot can use a cloud Linux desktop, a local VM or your own computer, with 500-plus apps through Composio, and a permission broker turns risky actions into decisions you make. Its README now also documents installing a full multi-Bot team from BotMRR, a site of outcome-driven team listings, or from any Markdown file, with a review screen before anything is created, and an "Auto" room mode that routes an un-mentioned message to the best Bot. A new Triggers section of the README documents schedules (once, on selected weekdays, or every 5 to 1,440 minutes) and webhooks that start a Bot, plus app events such as a new Gmail or Slack message, shown with run history in a sidebar Triggers page. It also documents voice calls through ElevenLabs, Fish Audio or Grok (xAI) keys, built-in Mac voices, or a local Chatterbox server, though calls themselves stay macOS-only for now. Install with npx openmausbot (Node 24 or later) or a desktop build. The local app is free and Apache 2.0 outside an enterprise folder; its pricing page now lists a $0 Free tier for trying it locally plus cloud workspaces at $15 (Starter, was $29), $49 (Pro) and $99 (Max) a month that keep scheduled tasks running with your laptop off, plus team plans at $169 a month for up to five people, $599 for up to 20 and $299 self-hosted. Pro and Max now include a monthly Claude credit ($10 and $20) on top of the one-time $5 Claude credit in the individual trials. Its README says API keys are stored as plaintext in a private config file.

gawkbot runs always-on Bots on your machine on a CLI you already pay for and holds every send, commit, purchase and delete for your approval; reads are free. Each Bot gets its own routines, self-written tools and data tables, and workspace state lives under ~/.wuphf/. Install the signed Mac app from gawk.bot or build from source; an iPhone companion is built with Xcode. Its Sustainable Use License limits use to internal business or non-commercial personal purposes, and it is a young project, first committed in March 2026; its README marks the packaged routine runner as still to come.

Sources: https://github.com/elie222/rakazo, https://rakazo.com/grok-bot-alternative/, https://github.com/milind-soni/OpenMausBot, https://mausbot.com/pricing, https://github.com/najmuzzaman-mohammad/gawkbot, https://raw.githubusercontent.com/najmuzzaman-mohammad/gawkbot/main/LICENSE

## What you take on when you self-host

Running any of the self-hosted options means keeping the process and its sandbox healthy, managing model keys and their spend, upgrading quickly moving codebases, and watching an approval queue so work does not stall. A laptop that sleeps stops an agent that runs on it. In exchange you can read every action, switch models per task, and keep files and browser sessions on infrastructure you control.

Grok Bot's trade is the reverse: setup takes minutes and mobile is built in, but every Bot on your account shares one cloud computer and set of logins, Cursor chooses the model, and usage above the weekly allowance is paid through top-ups on The X Subscription, or billed on demand on legacy Cursor plans, up to a monthly limit that does not stop a run already in progress. Our [shared-computer guide](https://www.grokbotwiki.com/guides/grok-bot-shared-computer) and [weekly usage guide](https://www.grokbotwiki.com/guides/grok-bot-weekly-usage-limit) cover both sides of that.

Sources: https://docs.x.ai/grok-bot/faq, https://cursor.com/help/grok-bot/plans, https://docs.openclaw.ai/start/getting-started

## Moving work between them

Nothing here imports a Grok Bot template, and Grok Bot does not import theirs. The official Marketplace lists Import Bot, a third-party template that says it brings setups from Claude Cowork, Codex, ChatGPT, OpenClaw and Hermes into Grok Bot; it is a community-made Bot, not a built-in importer, and we have not tested it. Move the brief instead: the outcome, sources, steps and acceptance checks. Then rebuild tools and permissions in the destination.

To compare two candidates, give each the same frozen document and brief, score the results against an answer key you wrote first, and record setup, run and review time. The [afternoon test in our OpenClaw comparison](https://www.grokbotwiki.com/guides/grok-bot-vs-openclaw) has the full protocol and a copyable brief.

Sources: https://x.ai/bot/marketplace

## Changes to this page

October 29, 2026: rechecked every source we could fetch. x.ai/bot, x.ai/pricing and the Grok Bot changelog refused our automated check, so the Super and Ultra figures and the 0.71.2 to 0.75.5 features were not rechecked today. Hermes Agent's README now lists six built-in terminal backends plus plugin backends (was seven); Nous Portal's paid plans now include hosting for one Hermes Cloud agent, and the $0.51-a-day Standard price no longer appears; Rakazo's README adds Novita as a sandbox provider and its site now says Rakazo Cloud is in beta; dots are rolling out on Enterprise as well as Business Premium; on The X Subscription extra usage is paid through top-ups. Removed two details the cited pages no longer support (Manus's former Meta ownership and the "action engine" phrase, and Cloud Workers running in your own cloud account) and softened gawkbot's single-maintainer note, since its repository shows a second major contributor. Star counts updated to October 29.

October 25, 2026: rechecked Grok Bot against x.ai/bot, the changelog and Cursor's plan and routines pages. x.ai/bot now shows The X Subscription tiers (Premium $30, Super $100 with 3.5x Premium usage, Ultra $200 with 12x); added Super and Ultra to the table. Added Pages, video creation, Shop Pay, the Vault, email forwarding, the 200-skill plugin limit and the 300-runs-an-hour routine limit from 0.71.2, 0.75.2 and 0.75.5. Rechecked the cited OpenAI, Anthropic, Manus, OpenClaw, Rakazo and MausBot pages: MausBot's README now also documents API providers such as OpenRouter (added to the table and prose); Manus's Cloud Computer post describes its own tiers rather than a separate sale, so that wording was corrected; the rest matched. Added one attributed community comparison of dots and Grok Bot from Composio.

October 22, 2026: rechecked Rakazo's and MausBot's READMEs and MausBot's pricing page directly. Rakazo's README now names Boat where its sandbox-provider list previously named Box (Docker, E2B, Daytona, CreateOS, Boat, Railway or local); updated the "Where it runs" table row and prose. MausBot's README adds a Triggers section documenting schedules, webhooks and app-event triggers with a sidebar Triggers page and run history; added one sentence. MausBot's pricing page now lists a $0 Free tier and an entry paid tier renamed Starter at $15 a month (previously $29), plus a monthly Claude credit ($10 Pro, $20 Max) on top of the existing one-time $5 trial credit; Pro ($49), Max ($99) and the team/business tiers are unchanged. Updated the table row and prose; OpenClaw's getting-started page was also rechecked (Node 24.16+/26.1+ and the channel list are unchanged).

October 15, 2026: rechecked Rakazo's and MausBot's READMEs and MausBot's pricing page. Rakazo's README now lists Railway alongside Docker, E2B, Daytona, CreateOS and Box as an optional remote sandbox provider; added to the "Where it runs" table row and prose. MausBot's README now names BotMRR as a source of outcome-driven team templates and documents a voice/calling feature (ElevenLabs, Fish Audio, Grok/xAI keys, built-in Mac voices, local Chatterbox; calls stay macOS-only); added one sentence each. MausBot's pricing page was rechecked directly and still matches this page's cloud-workspace and team figures exactly, aside from noting the existing $5 Claude trial credit. OpenClaw's getting-started page was also rechecked; no change from the October 11 facts.

October 14, 2026: updated Grok Bot's entry price for The X Subscription, which SpaceXSI launched October 12: Grok Bot is included from the $30 Premium plan, not on Free or the $8 Plus plan, while existing Cursor and SuperGrok plans continue. Other products were not rechecked.

October 11, 2026: rechecked every source. Hermes Cloud's Standard size is now $0.51 a day running (was $0.56), and Nous Portal lists Super and Ultra tiers and a ChatGPT sign-in option. Manus added Manus Flex for your own API key and, in 2.0, event-triggered automations. MausBot added team plans from $169 a month. gawkbot's README now installs through a Mac app rather than npx. OpenClaw's README lists native apps, and its docs add optional Cloud Workers. Rakazo's site says its hosted cloud is not generally available. Cursor's plan page lists X Premium+ as a subscription you can link. Star counts updated.

October 8, 2026: rechecked every repository and README. MausBot's README now documents installing a full team of Bots from one Markdown file and an "Auto" room mode that routes unmentioned messages; added one sentence on that. Rakazo's tool-source list, OpenClaw's Node requirement and channel list, and MausBot's $29/$49/$99 cloud pricing were rechecked and found unchanged from this page's prior facts.

October 7, 2026: new page. It replaces our separate Grok Bot vs Rakazo, vs OpenMausBot and vs gawkbot comparisons, whose addresses now redirect here, and keeps their facts after rechecking each README. Added OpenClaw, Hermes Agent, Manus, ChatGPT dots and Claude, and MausBot's new cloud pricing.

## Quick answers

### What is the best Grok Bot alternative?

It depends on what you want to stop doing. If you want an always-on agent without running anything, look at ChatGPT's dots (on ChatGPT Pro), Manus or Claude. If you want to choose the model and keep data on your own hardware, look at OpenClaw or Hermes Agent. If you want Grok Bot's named-Bots-in-a-chat-app design on your own machine, look at Rakazo, MausBot or gawkbot. We have not tested any of them head to head.

### Is there a free Grok Bot alternative?

The software is free for OpenClaw and Hermes Agent (MIT), Rakazo (Apache 2.0), MausBot's local app (Apache 2.0 outside its enterprise folder) and gawkbot (free for internal or personal use under its Sustainable Use License). In every case you still pay for the model, through API keys or a subscription you already have, and for any machine that has to stay on.

### Can I use Grok models in one of these?

Yes, in some. SpaceXSI announced on May 19, 2026 that you can sign in with a SuperGrok or X Premium subscription inside OpenClaw, and on May 15 that you can connect a Grok account to Hermes Agent. MausBot can drive the grok command-line tool. That is Grok the model, not Grok Bot the product.

### Can I import my Grok Bot templates into an alternative?

No. None of these imports Grok Bot templates or skills, and Grok Bot does not import theirs. The official Marketplace lists Import Bot, a third-party template that says it brings setups from other agents into Grok Bot; we have not tested it. What reliably transfers is the written brief: the outcome, sources, steps and acceptance checks.

### Is gawkbot open source?

Not in the usual sense. Its README calls it an open-source Grok Bot, but its LICENSE file is the Sustainable Use License, which limits use to internal business or non-commercial personal purposes and is not OSI-approved. Read it before building a paid or resold service on gawkbot.

## Sources

- [Grok Bot overview](https://docs.x.ai/grok-bot/overview)
- [Grok Bot FAQ](https://docs.x.ai/grok-bot/faq)
- [Grok Bot security: models and data](https://docs.x.ai/grok-bot/security)
- [Cursor plans and billing for Grok Bot](https://cursor.com/help/grok-bot/plans)
- [SpaceXSI: Introducing The X Subscription (October 12, 2026)](https://x.ai/news/x-subscription)
- [x.ai pricing: The X Subscription plans](https://x.ai/pricing)
- [Grok Bot product page and plans](https://x.ai/bot)
- [Grok Bot changelog (0.71.2, 0.75.2 and 0.75.5)](https://x.ai/changelog/bot)
- [Cursor help: Grok Bot routines](https://cursor.com/help/grok-bot/routines)
- [OpenClaw repository and README](https://github.com/openclaw/openclaw)
- [OpenClaw getting started](https://docs.openclaw.ai/start/getting-started)
- [OpenClaw sandboxing](https://docs.openclaw.ai/gateway/sandboxing)
- [SpaceXSI: Use Grok in OpenClaw (May 19, 2026)](https://x.ai/news/grok-openclaw)
- [OpenClaw Cloud Workers](https://docs.openclaw.ai/gateway/cloud-workers)
- [Hermes Agent repository and README (Nous Research)](https://github.com/NousResearch/hermes-agent)
- [Hermes Agent security documentation](https://hermes-agent.nousresearch.com/docs/user-guide/security)
- [Nous Portal plans](https://portal.nousresearch.com)
- [Hermes Cloud pricing](https://portal.nousresearch.com/cloud)
- [SpaceXSI: Connect Grok to Hermes Agent (May 15, 2026)](https://x.ai/news/grok-hermes)
- [Manus: Introducing Manus 2.0 (September 28, 2026)](https://manus.im/blog/introducing-manus-2-0)
- [Manus help: current membership pricing](https://help.manus.im/en/articles/11711111-what-is-the-current-membership-pricing-for-manus)
- [Manus: Manus Cloud Computer](https://manus.im/blog/manus-cloud-computer)
- [Manus: Introducing Manus Flex (September 29, 2026)](https://manus.im/blog/introducing-manus-flex)
- [Manus: resumes independent operations (September 1, 2026)](https://manus.im/blog/manus-resumes-independent-operations)
- [OpenAI docs: Meet dots](https://learn.chatgpt.com/docs/dots)
- [OpenAI docs: ChatGPT Work](https://learn.chatgpt.com/docs/get-started-with-work)
- [OpenAI docs: ChatGPT pricing for Work](https://learn.chatgpt.com/docs/pricing)
- [Community report: Composio, ChatGPT Dots vs Grok Bot (October 21, 2026)](https://composio.dev/content/chatgpt-dots-vs-grok-bots)
- [Anthropic: Claude Cowork and chat are now one Claude (September 16, 2026)](https://claude.com/blog/cowork-is-now-claude)
- [Claude Help: Claude Cowork architecture overview](https://support.claude.com/en/articles/14479288-claude-cowork-architecture-overview)
- [Claude pricing](https://claude.com/pricing)
- [Rakazo repository and README](https://github.com/elie222/rakazo)
- [Rakazo: Grok Bot alternative page](https://rakazo.com/grok-bot-alternative/)
- [MausBot (OpenMausBot) repository and README](https://github.com/milind-soni/OpenMausBot)
- [MausBot pricing](https://mausbot.com/pricing)
- [gawkbot repository and README](https://github.com/najmuzzaman-mohammad/gawkbot)
- [gawkbot LICENSE (Sustainable Use License)](https://raw.githubusercontent.com/najmuzzaman-mohammad/gawkbot/main/LICENSE)
- [Grok Bot Marketplace (Import Bot listing)](https://x.ai/bot/marketplace)

---

# Grok Bot vs OpenClaw: which one should you actually run?

> A managed cloud teammate or a self-hosted agent platform: the verdict by situation, the real cost lines, the isolation caveat, and an afternoon test.

- Canonical page: https://www.grokbotwiki.com/guides/grok-bot-vs-openclaw
- Sources checked: 2026-10-29
- Evidence: Grok Bot docs (overview, FAQ, Bots and security), Cursor's plan help, OpenClaw's README and cited docs, the Marketplace, SpaceXSI's announcement posts and the linked community reports rechecked October 29, 2026; x.ai/bot, x.ai/pricing and the Grok Bot changelog refused our automated check on October 29, so prices beyond The X Subscription post and changelog-dated features rest on our October 25 read · community head-to-heads linked, not reproduced. Suggested workflows have not been independently tested.
- Publisher: Grok Bot Wiki, an independent guide not affiliated with SpaceXSI, xAI or X.

## The verdict, by situation

Both products give you named, persistent agents that use a browser, files, and a terminal to finish work. The difference is who operates the computer they run on. Grok Bot runs each account's Bots on a hosted cloud computer you never manage. OpenClaw runs a Gateway you install and keep alive, on a machine you provide, with a model you bring.

Our recommendation, based on the documentation and on the community head-to-heads linked below: pick Grok Bot if you want to describe a job and have it running today, and you are comfortable with your logins living on a hosted machine. Pick OpenClaw if you need model choice, local data, chat-channel delivery, or a setup you can inspect and modify. If you are unsure, run the afternoon test at the end of this guide before committing to either.

If you are also weighing ChatGPT Work or Claude, our three-way guide, [Grok Bot vs ChatGPT agent vs Claude Cowork](https://www.grokbotwiki.com/guides/grok-bot-vs-chatgpt-vs-claude), compares them from each vendor's current documentation, and [Grok Bot alternatives](https://www.grokbotwiki.com/guides/grok-bot-alternatives) covers Hermes Agent, Manus and the open-source look-alikes.

|  | Grok Bot | OpenClaw |
| --- | --- | --- |
| Where it runs | Hosted cloud computer per account, managed by Cursor | Your Mac, Linux box, Windows, or a VPS you maintain |
| Setup | Install app, sign in, name a Bot, give it a task | Run the installer (it provisions a supported Node runtime if needed; the docs list Node 24.16+ or 26.1+), finish onboarding, then install the Gateway as a background service |
| Model | Chosen by Cursor, no model picker; the serving mix can change | Any provider via API key, an existing Claude Code or Codex login, or a SuperGrok sign-in |
| Price | Bundled with The X Subscription from $30/month (Premium; Super $100 with 3.5x Premium usage, Ultra $200 with 12x), or legacy Cursor plans from $20 and linked SuperGrok from $30; weekly allowance; optional paid extra usage | Software free and open source; you pay model usage and hosting |
| Talks to you through | Its own desktop and mobile apps, plus X Chat, @bot on X, and Slack for shared Bots | Discord, Slack, Telegram, WhatsApp, Signal, iMessage, Teams and 20+ more, plus native desktop and mobile apps |
| Agent isolation | One shared computer, files, and browser logins per account | Per-agent workspaces and auth profiles; sandboxing is a setting, not a default |
| Reusable setups | Bot templates on the web Marketplace or by share link, added with one click | ClawHub registry of skills and plugins, installed by CLI, with scan summaries; curate carefully after the ClawHavoc malware campaign |
| Who fixes it when it breaks | Cursor support and status; you wait | You, with openclaw doctor, the docs and community |
| Best for | Operators who want results without owning infrastructure | Builders who want control, model choice, and channels |

Sources: https://docs.x.ai/grok-bot/overview, https://cursor.com/help/grok-bot/plans, https://x.ai/pricing, https://x.ai/bot, https://github.com/openclaw/openclaw, https://docs.openclaw.ai/start/getting-started, https://docs.openclaw.ai/concepts/multi-agent, https://docs.openclaw.ai/clawhub, https://x.ai/news/grok-openclaw

## Pick Grok Bot if

You want to hand off a recurring job this week and you do not want to learn a framework. Grok Bot's first run is install, sign in, name a Bot, describe the job. Skills can be taught by demonstration, recording up to ten minutes of your own browser work, and routines schedule them. Nothing here requires a terminal.

You are fine with Cursor choosing the model, with no picker and a serving mix that can change over time, and with usage measured against a weekly allowance. Access comes with The X Subscription's Premium, Super or Ultra plans or team seats, or with an existing Cursor Pro, Pro+, Ultra or Teams plan or a linked SuperGrok or X Premium+ subscription. You accept that all your Bots share one cloud computer and one set of logins, and you will keep sensitive accounts off it. You want mobile access to the same Bots without running a server.

You want more built in rather than assembled. October's releases added Pages (reports, memos and dashboards you edit with the Bot or have it keep up to date) and video creation in 0.75.2, a Vault in Settings where Bots save logins, cards and contact details to sign in or check out, plus email forwarding from a Bot's own inbox, in 0.75.5, and Shop Pay at checkout. Bots can use up to 200 skills from installed plugins (up from 24 in 0.71.2), and routines can run up to 300 times an hour in total and 200 times each. On OpenClaw, equivalents come from the skills and plugins you choose and maintain.

Sources: https://docs.x.ai/grok-bot/overview, https://docs.x.ai/grok-bot/faq, https://docs.x.ai/grok-bot/security, https://cursor.com/help/grok-bot/plans, https://x.ai/news/x-subscription, https://x.ai/pricing, https://x.ai/changelog/bot

## Pick OpenClaw if

You want to choose or switch models, including Grok through your own xAI key or a SuperGrok sign-in. You want your files and browser sessions on hardware you control. You want the agent to reach you inside Slack, Telegram, WhatsApp, or another channel, or in OpenClaw's own desktop and mobile apps. You are willing to keep a Gateway process alive and update it. The README says the same Gateway can run as a personal assistant on a laptop or as a shared team deployment.

You want to read what a skill does before installing it. ClawHub is open to anyone with a GitHub account old enough to pass its upload gate. By mid-February 2026 ClawHub held more than 10,700 skills, and in the ClawHavoc campaign researchers at Koi and others found hundreds of malicious ones, including typosquats of ClawHub's own tools. ClawHub now shows a scan summary on each listing and can hold or block releases that fail its checks. Inspection is still your job: it costs time, and it is also the control Grok Bot does not offer.

Sources: https://github.com/openclaw/openclaw, https://docs.openclaw.ai/start/getting-started, https://docs.openclaw.ai/clawhub, https://blog.polyswarm.io/the-clawhavoc-campaign, https://x.ai/news/grok-openclaw

## The cost lines people leave out

Grok Bot's plan price is a floor. The weekly allowance is unpublished; on The X Subscription it is also shared with your Grok and Cursor use and extra usage is paid from prepaid top-ups, and on the existing Cursor plans on-demand billing counts against a monthly limit that does not stop a run already in progress, and forum users report a week of allowance consumed in a day by a multi-Bot setup. [Our weekly usage guide](https://www.grokbotwiki.com/guides/grok-bot-weekly-usage-limit) walks through the meter. The upside is that compute, browser, and model are all inside that one bill.

OpenClaw's zero software cost hides three lines: model usage at provider rates, a machine that stays on (a laptop lid closing stops your agent unless you use a server), and your own hours keeping it configured. For always-on heavy use those lines are often lower than Grok Bot's on-demand spend. For a few bounded tasks a week, the hours dominate.

Record setup time once and review time on every run. An inexpensive run that needs extensive repair costs more than a pricier complete result.

Sources: https://docs.x.ai/grok-bot/faq, https://cursor.com/help/grok-bot/plans, https://x.ai/pricing, https://docs.openclaw.ai/start/getting-started

## The isolation caveat in both products

Grok Bot's account shares one computer, including files and browser logins, across every Bot you create. Separate Bot names and conversations do not create separate access boundaries. OpenClaw documents per-agent workspaces, state, and authentication profiles, but says plainly that a workspace is a working directory, not a hard sandbox, and that absolute paths can reach other host locations unless sandboxing is on. Sandboxing is off by default, and its docs add that even sandboxing is not a perfect security boundary.

Grok Bot's new Vault raises the stakes. The 0.75.5 changelog says Bots can save your logins, cards and contact information and fill them in to sign in or check out, and x.ai/bot still says every Bot shares one computer's files, browser and logins. The changelog does not say whether a Vault entry is limited to one Bot, so treat a saved card like any other login on that shared computer.

In either product, inspect the actual access configuration before assigning work that must stay apart. A different agent name is not evidence of isolation.

Sources: https://docs.x.ai/grok-bot/overview, https://x.ai/bot, https://x.ai/changelog/bot, https://docs.openclaw.ai/concepts/multi-agent, https://docs.openclaw.ai/gateway/sandboxing

## What the community head-to-heads found

Three widely read comparisons reach compatible conclusions. MindStudio's three-way test found Grok Bot wins on setup and shared memory across agents while OpenClaw wins on flexibility for people willing to carry the technical overhead. On Lenny's Newsletter's How I AI, Claire Vo describes replacing every OpenClaw agent she ran with Grok Bot. AJ Green calls Grok Bot OpenClaw without the rough edges, which is praise for polish and a warning about control.

These are attributed community reports, not our reproduced results. They share a limitation: each author tested their own workflow. Use them to calibrate expectations and then run your own comparison on your own task.

Sources: https://www.mindstudio.ai/blog/grok-bot-vs-openclaw-chatgpt, https://www.lennysnewsletter.com/p/grok-bot-vs-openclaw-how-i-replaced, https://ajsai.substack.com/p/grok-bot-is-openclaw-without-the

## Reusable setups: share links versus a registry

Grok Bot distributes setups as templates that package a Bot's profile, skills, routines, and plugins for one-click adding, shared as a public or team-only link, and through the official Marketplace at x.ai/bot/marketplace. Since 0.67.0 (October 2) the in-app Marketplace is called Connect apps; its Bot templates entry opens the template gallery on x.ai. The copy does not include the creator's computer, sign-ins, or history. ClawHub is OpenClaw's registry for skills and plugins with search, install, update, and publish commands.

These do not interoperate natively. An OpenClaw skill does not import into Grok Bot and a Bot template does not become a ClawHub package. The Marketplace does list a community-made Import Bot that describes bringing setups over from OpenClaw and other agents; it is a third-party Bot, not a built-in importer, and we have not tested it. What reliably transfers is the brief: the outcome, sources, steps, and acceptance checks. Move that, then rebuild tools and permissions in the destination.

[Our Marketplace and templates guide](https://www.grokbotwiki.com/guides/grok-bot-marketplace-templates) covers what a Grok Bot template copies, how to vet one before adding it, and how to share your own.

Sources: https://docs.x.ai/grok-bot/bots, https://x.ai/bot/marketplace, https://x.ai/changelog/bot, https://docs.openclaw.ai/clawhub

## Run the afternoon test

Use the same frozen document in both products. It controls for changing web results and exposes extraction mistakes without any integrations. This is an original evaluation template; we have not run it as a published head-to-head.

1. Choose meeting notes with five known commitments, one ambiguous statement, and one missing deadline. Write the answer key first.
2. Give each product the same file and brief. Record product version, model when visible, date, and permissions granted.
3. Score completeness, source accuracy, invented owners or dates, and required corrections against the key.
4. Record setup time, execution time, human review time, and visible usage. Leave unavailable measurements blank.
5. Repeat with a second document. Add live tools only after the basic task is useful in one of them.

Editorial template (replace placeholders and review access before running):

```text
From the attached meeting notes, extract explicit commitments into a table: action, owner, deadline, source passage, and uncertainty. Mark absent details as unspecified. List ambiguous statements separately. Preserve the source file, use no external tools, and do not send messages or create tasks elsewhere. Finish with anything you could not read. Return a draft for my review.
```

## Changes to this page

October 29, 2026: rechecked every source we could fetch; x.ai/bot, x.ai/pricing and the Grok Bot changelog refused our automated check, so the Super and Ultra figures and changelog-dated features were not rechecked today. The FAQ now says you can also reach your Bots in X Chat, by tagging @bot on X, and through a shared Bot in Slack, so the channels row was updated. The installer note now says it provisions a supported Node runtime. Corrected two attributions: the 10,700-skill figure is ClawHub's size in mid-February, not a Koi count, and the Lenny's Newsletter piece is Claire Vo's How I AI episode. Connect apps now opens the template gallery through its Bot templates entry.

October 25, 2026: added Super ($100, 3.5x Premium usage) and Ultra ($200, 12x) from x.ai/bot to the price row, and Grok Bot's October additions (Pages, video creation, the Vault, Shop Pay, email forwarding, 200 plugin skills, routine limits of 300 runs an hour) to the Grok Bot case and isolation caveat. Rechecked OpenClaw's README and its getting-started, sandboxing, multi-agent and ClawHub docs: Node 24.16+ or 26.1+, the installer provisioning Node, the channel list, sandboxing off by default and ClawHub's upload gate and scan summaries all match this page, so the OpenClaw side is unchanged.

October 14, 2026: updated Grok Bot's price lines for The X Subscription, launched October 12, which includes Grok Bot from its $30 Premium plan; existing Cursor and SuperGrok plans continue. OpenClaw was not rechecked.

October 11, 2026: rechecked OpenClaw's README and docs and Cursor's plan pages. OpenClaw's installer now provisions Node 24.16 or later itself, the README lists native apps and 20-plus channels, and ClawHub now shows security scan summaries; the setup, channels and registry rows were updated. Replaced an unsourced ClawHub skill count with Koi's dated February figure. Added the SuperGrok sign-in, X Premium+ access to Grok Bot, and the move of Bot templates out of the app.

## Quick answers

### Is Grok Bot a fork of OpenClaw?

No. Grok Bot is a closed, hosted product from SpaceXSI (formerly xAI) that runs on Cursor's cloud infrastructure. OpenClaw is an open-source, self-hosted agent platform. They compete on the same job, running persistent agents that use your tools, but share no code.

### Can I use Grok inside OpenClaw?

Yes. SpaceXSI announced on May 19, 2026 that you can sign in with a SuperGrok or X Premium subscription inside OpenClaw, or use Grok models through an API key. That is a different thing from Grok Bot, the product. Searches for 'Grok OpenClaw' return both, which is a common source of confusion.

### Which is cheaper?

OpenClaw's software is free, but you pay for model access through your own API keys or CLI logins plus the machine or server it runs on and your own maintenance time. Grok Bot bundles compute and a weekly model allowance into a subscription: The X Subscription from $30 a month (Premium), or an existing Cursor or SuperGrok plan from $20, with extra usage billed only if you allow it. For light, bounded use Grok Bot is usually cheaper in time; for heavy always-on use OpenClaw is usually cheaper in money.

### Which is safer for handling my logins?

Neither is safe by default. Grok Bot signs into your apps with your real credentials on one shared cloud computer for the whole account. OpenClaw runs on hardware you control but its workspaces are working directories, not hard sandboxes, unless you configure sandboxing. In both, separate agent names are not separate security boundaries.

## Sources

- [Grok Bot architecture](https://docs.x.ai/grok-bot/overview)
- [Grok Bot access and billing](https://docs.x.ai/grok-bot/faq)
- [Creating and sharing Bots](https://docs.x.ai/grok-bot/bots)
- [Grok Bot security: models and data](https://docs.x.ai/grok-bot/security)
- [Cursor plans and billing](https://cursor.com/help/grok-bot/plans)
- [SpaceXSI: Introducing The X Subscription (October 12, 2026)](https://x.ai/news/x-subscription)
- [x.ai pricing: The X Subscription plans](https://x.ai/pricing)
- [Grok Bot product page and plans](https://x.ai/bot)
- [Grok Bot Marketplace](https://x.ai/bot/marketplace)
- [OpenClaw getting started](https://docs.openclaw.ai/start/getting-started)
- [OpenClaw multi-agent routing](https://docs.openclaw.ai/concepts/multi-agent)
- [ClawHub registry documentation](https://docs.openclaw.ai/clawhub)
- [OpenClaw repository and README](https://github.com/openclaw/openclaw)
- [OpenClaw sandboxing](https://docs.openclaw.ai/gateway/sandboxing)
- [PolySwarm: the ClawHavoc campaign (February 27, 2026)](https://blog.polyswarm.io/the-clawhavoc-campaign)
- [Grok Bot changelog (Connect Apps in 0.67.0; Pages, Vault and routine limits in 0.75.2 and 0.75.5)](https://x.ai/changelog/bot)
- [SpaceXSI: Use Grok in OpenClaw (May 19, 2026)](https://x.ai/news/grok-openclaw)
- [Community report: MindStudio three-way comparison](https://www.mindstudio.ai/blog/grok-bot-vs-openclaw-chatgpt)
- [Community report: Lenny's Newsletter, replacing an agent stack](https://www.lennysnewsletter.com/p/grok-bot-vs-openclaw-how-i-replaced)
- [Community report: AJ Green, OpenClaw without the rough edges](https://ajsai.substack.com/p/grok-bot-is-openclaw-without-the)

---

# Grok Bot vs ChatGPT agent vs Claude Cowork: which to pick

> ChatGPT agent is now ChatGPT Work and Cowork is now part of Claude. How the three compare on where work runs, schedules, apps and price, and who fits each.

- Canonical page: https://www.grokbotwiki.com/guides/grok-bot-vs-chatgpt-vs-claude
- Sources checked: 2026-10-29
- Evidence: Grok Bot docs, Cursor's plan, pricing and routines pages, OpenAI's learn.chatgpt.com docs and Anthropic's help center, blog and pricing rechecked October 29, 2026; x.ai/bot, x.ai/pricing, the Grok Bot changelog, chatgpt.com/pricing and OpenAI's help center refused our automated check on October 29, so claims from those pages rest on our October 25 read · documentation comparison, no head-to-head run. Suggested workflows have not been independently tested.
- Publisher: Grok Bot Wiki, an independent guide not affiliated with SpaceXSI, xAI or X.

## The verdict

Pick Grok Bot if you want a small team of named, long-lived Bots that keep logins and files on one always-on cloud computer and run on schedules. Pick ChatGPT Work if you already pay for ChatGPT and want finished documents, spreadsheets and presentations, a model picker, and tasks triggered by Gmail, Slack or GitHub. Pick Claude if you already pay for Claude and want one conversation that decides when to run a task, with each cloud task in its own temporary sandbox.

Two of the names people search for have changed. OpenAI's help center says ChatGPT agent is no longer available and points to ChatGPT Work. Anthropic announced on September 16, 2026 that Claude Cowork and chat are merging into one Claude, rolling out to Pro and Max first; its help center now adds Team (in beta) and Enterprise where an organization has turned on Chat and Cowork unified. This page compares the current products.

It is a documentation comparison. We have not run the same task in all three, and none of the vendors publishes usage allowances in comparable units, so there is no quality or cost-per-task ranking here. OpenAI's documentation now also describes dots, an always-on agent with its own cloud computer on the Pro 100, 200 and 500 plans outside the EEA, UK and Switzerland, and rolling out on Business Premium and Enterprise (off by default there until an administrator turns it on); [Grok Bot alternatives](https://www.grokbotwiki.com/guides/grok-bot-alternatives) covers it alongside Manus, Hermes Agent and OpenClaw.

|  | Grok Bot | ChatGPT Work | Claude (Cowork) |
| --- | --- | --- | --- |
| What it is | Named Bots with jobs and memory that you message like teammates | An agent in ChatGPT for longer, multi-step work and finished deliverables | Cowork's task abilities inside any Claude conversation (Pro and Max, rolling out) |
| Where work runs | One persistent cloud computer per user, with browser, files and terminal, shared by all your Bots | In the cloud on web and mobile; locally in the desktop app with your permission | A temporary cloud sandbox per session, removed when it ends; local files and browser through Claude Desktop |
| Keeps going with the laptop closed | Yes | Cloud Work chats run in the cloud | Yes, for cloud tasks |
| Finished output | Pages: reports, memos and dashboards you edit together or have the Bot keep up to date; images and videos | Reviewable outputs such as a brief, deck, analysis, recurring update or file | Documents, spreadsheets with working formulas and presentations; Claude Docs (beta) for living documents |
| Recurring work | Routines on a schedule or after an event such as a Slack message, GitHub notification or email to the Bot's inbox; up to 300 runs an hour in total | Scheduled tasks: once, repeating, or triggered by new Gmail, Slack channel messages or GitHub pull request activity | Scheduled tasks on all paid plans: hourly, daily, weekly, weekdays or manual |
| Model | Chosen by Cursor, no picker | Model picker: GPT-6 Astra, GPT-6.1 Sol and Luna, depending on plan | Optional model choice when you set up a scheduled task |
| Apps | macOS, Windows, Linux; iPhone, iPad, Android | Web, iOS, Android and the ChatGPT desktop app | Desktop on macOS, Windows and Linux (beta) on all paid plans; web and mobile on Pro, Max and Team (beta on Team); Chrome side panel on all paid plans |
| Reusing a setup | Bot templates shared by public or team-only link, plus the official Marketplace | Share a scheduled Work task; the recipient schedules their own copy | Skills, and plugins that bundle skills and connectors for a role |
| Entry price with the agent | The X Subscription Premium, $30 (not Free or $8 Plus); Super $100 and Ultra $200 (x.ai/bot: 3.5x and 12x Premium usage; cursor.com/pricing: 15x and 50x Plus, against Premium's 4x); legacy Cursor Pro ($20) and linked SuperGrok plans continue | Work on every plan; Free and Go ($8) list GPT-6 Luna in the desktop app; Plus $20; Pro at $100, $200 or $500 | Claude Pro $20 a month ($17 billed annually); Max from $100; Team Standard $25 a seat monthly ($20 billed annually) |

Sources: https://docs.x.ai/grok-bot/overview, https://docs.x.ai/grok-bot/faq, https://docs.x.ai/grok-bot/skills-routines-and-automations, https://docs.x.ai/grok-bot/teams-and-enterprises, https://help.openai.com/en/articles/11752874-chatgpt-agent, https://help.openai.com/en/articles/20001275-chatgpt-work-and-codex, https://chatgpt.com/pricing, https://claude.com/blog/cowork-is-now-claude, https://support.claude.com/en/articles/16761823-claude-cowork-and-chat-are-one-claude, https://support.claude.com/en/articles/13345190-get-started-with-claude-cowork, https://support.claude.com/en/articles/14479288-claude-cowork-architecture-overview, https://support.claude.com/en/articles/13854387-schedule-recurring-tasks-in-claude-cowork, https://claude.com/pricing, https://learn.chatgpt.com/docs/get-started-with-work, https://learn.chatgpt.com/docs/pricing, https://learn.chatgpt.com/docs/dots, https://cursor.com/pricing, https://cursor.com/help/grok-bot/plans, https://cursor.com/help/grok-bot/routines, https://x.ai/bot, https://x.ai/changelog/bot, https://x.ai/news/x-subscription, https://x.ai/pricing

## Pick Grok Bot if you want standing teammates

Grok Bot is built around Bots you keep: each has a name, a job, its own conversation and memory, and Bots run in parallel, message each other and share context in group chats. They all work on one persistent cloud computer, so a login you complete once is available to every Bot, and work continues when your laptop is closed.

That shared computer is also the caution. The docs say Bots on an account are not a security boundary: any Bot can use a session another Bot signed into, while isolation between users is strict. Access comes with The X Subscription from its Premium plan, or with an existing Cursor plan or linked SuperGrok or X Premium+ subscription, with a weekly allowance and optional paid extra usage, and Cursor chooses the model. [Our plan guide](https://www.grokbotwiki.com/guides/grok-bot-which-plan) covers which subscription to use.

October's releases moved Grok Bot closer to the other two on finished output. Since 0.75.2 (October 22) Bots can build Pages, such as reports, memos and dashboards, that you edit together or have the Bot keep up to date, and create videos from a description or an image. Since 0.75.5 (October 23) they can save your logins, cards and contact details to a Vault in Settings to sign in or check out, pay with Shop Pay, and forward an email from their own inbox with its attachments. Bots can now use up to 200 skills from installed plugins, and routines can run up to 300 times an hour in total. A saved card sits on the same shared computer as everything else, so decide which Bot should ever check out before you save one.

Sources: https://docs.x.ai/grok-bot/overview, https://docs.x.ai/grok-bot/faq, https://docs.x.ai/grok-bot/teams-and-enterprises, https://cursor.com/help/grok-bot/plans, https://x.ai/pricing, https://x.ai/bot, https://x.ai/changelog/bot, https://cursor.com/help/grok-bot/routines

## Pick ChatGPT Work if you want finished deliverables

OpenAI describes Work as an agent for longer, multi-step work: it can research a topic, analyze information, or create a document, spreadsheet, presentation, report or Site. You pick the model, GPT-6 Astra for the most demanding work, GPT-6.1 Sol for complex work at lower cost, or Luna for simpler tasks; Work follows the same usage structure as Codex, and Codex sits beside it in the desktop app for software work. Event-triggered tasks can start from a new Gmail message, a Slack channel message or GitHub pull request activity, on Plus and higher plans.

Work can run in the cloud, which suits scheduled research because your computer need not be awake, or in the desktop app, where it can use local files, apps and the browser with your permission. With sync turned on, a new task can continue across desktop, mobile and web and still reach approved local resources through a connected computer; if that computer is unavailable, an eligible task continues in a cloud container without access to it. If you used ChatGPT agent before, its help article now says it is no longer available and points to Work.

Sources: https://help.openai.com/en/articles/20001275-chatgpt-work-and-codex, https://learn.chatgpt.com/docs/get-started-with-work, https://help.openai.com/en/articles/11752874-chatgpt-agent, https://chatgpt.com/pricing

## Pick Claude if you want one conversation that decides

In the new Claude experience you ask in any conversation and Claude decides whether a request needs a quick answer or a task, which it can run in the cloud and hand back as documents, spreadsheets or presentations. Anthropic's architecture overview says each cloud session gets its own sandbox, created when the session starts and destroyed when it ends, that it cannot reach private network addresses, and that connector tokens never enter it. Tasks that use files or apps on your computer need Claude Desktop open. Scheduled tasks keep their cadence while your computer is asleep, unless a task needs local files or apps, in which case it runs only locally.

Anthropic says Cowork is on Claude Desktop for macOS, Windows and Linux (beta) on all paid plans (Pro, Max, Team and Enterprise), on web and mobile for Pro, Max and Team (in beta on Team), and for Enterprise when an owner enables it; the Chrome side panel is on all paid plans. The merged experience is rolling out gradually to Pro and Max, and is available on Team (in beta) and Enterprise where Chat and Cowork unified is turned on; accounts that move over cannot switch back to separate Chat and Cowork options.

Sources: https://support.claude.com/en/articles/16761823-claude-cowork-and-chat-are-one-claude, https://support.claude.com/en/articles/14479288-claude-cowork-architecture-overview, https://support.claude.com/en/articles/13345190-get-started-with-claude-cowork, https://support.claude.com/en/articles/13854387-schedule-recurring-tasks-in-claude-cowork, https://claude.com/blog/cowork-is-now-claude

## Test them on the same task

If you are choosing between two of these, give each the same frozen document and the same brief, score the results against an answer key you wrote first, and record setup time, run time, review time and the usage each run consumed. Keep logins and connectors out of the first run so you compare the agents, not your integrations. [Our OpenClaw comparison](https://www.grokbotwiki.com/guides/grok-bot-vs-openclaw) has the full protocol and a copyable brief.

## Changes to this page

October 29, 2026: rechecked every source we could fetch. x.ai/bot, x.ai/pricing, the Grok Bot changelog, chatgpt.com/pricing and OpenAI's help center refused our automated check, so those claims were not rechecked today. Added cursor.com/pricing's usage multiples (4x, 15x and 50x Plus) next to the x.ai/bot figures we read earlier; Anthropic's September 16 post now carries an October 23 update saying the merged Claude is generally available for Enterprise; OpenAI's dots page now lists Enterprise as rolling out, off by default. The other cited Grok Bot, Cursor, OpenAI and Anthropic pages matched.

October 25, 2026: x.ai/bot now shows The X Subscription plans, so Super ($100, 3.5x Premium usage) and Ultra ($200, 12x) were added. Added a finished-output row (Grok Bot Pages and video creation from 0.75.2), the 300-runs-an-hour routine limit and inbox-triggered routines, and the Vault, Shop Pay and email forwarding from 0.75.5. Rechecked Anthropic's help center, blog and pricing: Cowork desktop now includes Linux (beta), the Chrome side panel is on all paid plans, Team gets the merged Claude in beta and Enterprise where Chat and Cowork unified is on, and Team Standard is $25 a seat monthly or $20 billed annually; those rows and the FAQ were updated. OpenAI's pricing docs now say Work is on every plan; the price cell was reworded. OpenAI's help center again refused our automated check, so the ChatGPT agent retirement and event-trigger details still rest on our September 23 reading.

October 14, 2026: updated Grok Bot's entry price for The X Subscription, launched October 12, which includes Grok Bot from its $30 Premium plan; existing Cursor and SuperGrok plans continue. OpenAI and Anthropic pages were not rechecked.

October 11, 2026: rechecked every vendor page we could reach. OpenAI's ChatGPT Work docs now name GPT-6 Astra, GPT-6.1 Sol and Luna in the picker and describe Work Cloud sync, and its pricing docs list Go at $8 and a $500 Pro tier; Claude's help center now lists web and mobile Cowork for Team and a Chrome side panel rolling out to Pro; Anthropic says Team and Free plans follow Pro and Max into the merged Claude. Cursor's plan page lists X Premium+ as a linkable subscription. OpenAI's help center and chatgpt.com/pricing refused our automated check, so the ChatGPT agent retirement and event-trigger details rest on our September 23 reading of those pages.

## Quick answers

### Is ChatGPT agent still available?

No. OpenAI's help article for ChatGPT agent now says it is no longer available and points to ChatGPT Work for longer, multi-step tasks and finished deliverables, and to the cloud browser for supported browser workflows.

### Is Claude Cowork gone?

It is being folded into Claude. Anthropic announced on September 16, 2026 that Cowork and chat are merging into one Claude, rolling out to Pro and Max plans over several weeks, with Team and Free plans to follow, and promised Enterprise admins at least 30 days' notice before anything changes; an October 23 update to that post says the unified experience is now generally available for Claude Enterprise. Its help center now says the merged experience is rolling out to Pro and Max, and is available on Team plans (in beta) and Enterprise plans where the Chat and Cowork unified setting is turned on; it does not mention Free. In the new experience there is no Cowork mode to pick: you ask in any conversation.

### Which of the three is cheapest?

By entry price, Grok Bot now comes with The X Subscription's Premium plan at $30 a month (legacy Cursor Pro subscribers at $20 keep it), with Super at $100 and Ultra at $200 for 3.5 and 12 times Premium's usage according to x.ai/bot (cursor.com/pricing puts the three tiers at 4, 15 and 50 times Plus usage), and Claude Pro is $20 billed monthly. OpenAI's pricing docs say Work is included on every plan, with Free and Go ($8 a month) listing GPT-6 Luna at standard speed in the desktop app, and Plus at $20. None of the three publishes its allowance in comparable units, so there is no honest cost-per-task comparison; run the same task in each and read the usage meter.

### Can I bring my ChatGPT or Cowork setup into Grok Bot?

There is no official importer in the Grok Bot docs. The official Marketplace lists Import Bot, a third-party template by Shub Gaur that says it brings setups from Claude Cowork, Codex, ChatGPT, OpenClaw and Hermes into Grok Bot. We have not tested it. Moving the written brief by hand always works.

### Which one is the most secure?

They draw the boundary in different places. Grok Bot gives each user one dedicated cloud computer, isolated from other users, that all of that user's Bots share, so Bots are not a boundary from each other. Claude runs each cloud session in its own temporary sandbox that never holds connector tokens. ChatGPT Work relies on approvals for important actions plus workspace permission controls. In all three, the permissions you grant matter more than the product.

## Sources

- [Grok Bot overview](https://docs.x.ai/grok-bot/overview)
- [Grok Bot FAQ](https://docs.x.ai/grok-bot/faq)
- [Grok Bot skills and routines](https://docs.x.ai/grok-bot/skills-routines-and-automations)
- [Grok Bot teams and enterprises: architecture](https://docs.x.ai/grok-bot/teams-and-enterprises)
- [Cursor plans and billing for Grok Bot](https://cursor.com/help/grok-bot/plans)
- [Cursor pricing (now showing The X Subscription plans)](https://cursor.com/pricing)
- [Grok Bot product page (now shows The X Subscription plans)](https://x.ai/bot)
- [Grok Bot changelog (0.71.2, 0.75.2 and 0.75.5)](https://x.ai/changelog/bot)
- [Cursor help: Grok Bot routines](https://cursor.com/help/grok-bot/routines)
- [SpaceXSI: Introducing The X Subscription (October 12, 2026)](https://x.ai/news/x-subscription)
- [x.ai pricing: The X Subscription plans](https://x.ai/pricing)
- [Grok Bot Marketplace (Import Bot listing)](https://x.ai/bot/marketplace)
- [OpenAI Help: ChatGPT agent (no longer available)](https://help.openai.com/en/articles/11752874-chatgpt-agent)
- [OpenAI Help: ChatGPT Work and Codex](https://help.openai.com/en/articles/20001275-chatgpt-work-and-codex)
- [ChatGPT pricing](https://chatgpt.com/pricing)
- [OpenAI docs: Get started with ChatGPT Work](https://learn.chatgpt.com/docs/get-started-with-work)
- [OpenAI docs: ChatGPT pricing for Work](https://learn.chatgpt.com/docs/pricing)
- [OpenAI docs: Meet dots](https://learn.chatgpt.com/docs/dots)
- [Anthropic: Claude Cowork and chat are now one Claude (September 16, 2026)](https://claude.com/blog/cowork-is-now-claude)
- [Claude Help: Claude Cowork and chat are one Claude](https://support.claude.com/en/articles/16761823-claude-cowork-and-chat-are-one-claude)
- [Claude Help: Get started with Claude Cowork](https://support.claude.com/en/articles/13345190-get-started-with-claude-cowork)
- [Claude Help: Claude Cowork architecture overview](https://support.claude.com/en/articles/14479288-claude-cowork-architecture-overview)
- [Claude Help: Schedule recurring tasks in Claude Cowork](https://support.claude.com/en/articles/13854387-schedule-recurring-tasks-in-claude-cowork)
- [Claude pricing](https://claude.com/pricing)

---

# Grok Bot Marketplace and templates: find, add, share a Bot

> Bot templates moved out of the app in October. Where to find them now, what a template copies, how to vet one, and how to share your own Bot.

- Canonical page: https://www.grokbotwiki.com/guides/grok-bot-marketplace-templates
- Sources checked: 2026-10-28
- Evidence: Changelog entry 0.77.0 (October 26) read October 28, 2026; changelog entries 0.75.2 and 0.75.5 checked October 25, 2026; docs and earlier changelog entries checked October 14; Cursor staff forum replies checked October 11; web Marketplace, template guide and third-party bot terms checked October 7 · no template added or tested by us. Suggested workflows have not been independently tested.
- Publisher: Grok Bot Wiki, an independent guide not affiliated with SpaceXSI, xAI or X.

## What the Grok Bot Marketplace is

The Grok Bot Marketplace at x.ai/bot/marketplace is SpaceXSI's official catalog of Bot templates: ready-made Bots you can add to your own account. A template is a recipe, not a clone: it carries a Bot's identity, instructions, skills and routines, and some plugins and memories, but never the creator's computer, logins or conversation history. Anyone can also share a template by link, publicly or with their team only.

When we checked on October 7, 2026, the page had a Featured row (dr eggbot by Lauren Tan, Overheard by Lenny Rachitsky, Tradbot by Claire Vo and Projects Manager by Eric Zakariasson), a From Grok Bot Team row, and rows for Engineering, Sales, Marketing, Design, Personal, Recruiting & People, Product and Operations. Each card names its creator and has an Add button. Examples include Haggle Bot by Daniel Gartshein, which inventories SaaS spend and drafts vendor counters for review, and Recruiting Coordinator by Tommy Hansen. The page showed no prices, and none of the pages we checked explain how Bots are chosen for it.

Templates are no longer in the app. Version 0.63.0 (September 29) made the in-app Marketplace focus on plugins, so Featured Bots and Bot search results stopped appearing there, and 0.67.0 (October 2) renamed it Connect Apps, with Bot templates on the web. Use the web Marketplace, a share link, or a community directory to find a Bot; use Connect Apps for plugins, as our [plugins guide](https://www.grokbotwiki.com/guides/grok-bot-plugins-mcp) explains. You can also ask: the changelog entry of October 11 (0.69.0 to 0.70.2) says Bots can find a Bot template that fits what you describe and link it in chat. The link leads to the same preview and add step, so check it the same way.

Sources: https://x.ai/bot/marketplace, https://x.ai/bot/guides/templates-for-grok-bot, https://docs.x.ai/grok-bot/bots, https://x.ai/changelog/bot

## What a template copies, and what it leaves out

The docs describe what a viewer sees: a public link shows the Bot's shared configuration, including its identity, description, skills and routines. xAI's September 8 template guide, by Matt Palmer, adds that a template packages the Bot's instructions, relevant memories, skills and specific plugins, excludes personal or internal memories by default, and does not carry MCP servers, custom code or scripts. For complex setups, the guide suggests having the Bot write setup instructions into the template.

One known gap: a forum report from August 29 says a template's preview lists skills that never arrive on import. A Cursor staff member confirmed it on August 31 and said again on October 9 that it is still tracked. The preview text cannot be selected, so staff now suggest taking screenshots of each skill in the preview, sending them to the new Bot and asking it to create a skill with exactly that content, then reading the result. On October 10 the original reporter said imports had briefly worked in early September, that 30 template skills were missing across nine of their Bots, and that a fresh test brought over the routine but none of seven skills.

Check what actually arrived. A Bot's skills are listed in Connect Apps (formerly Marketplace) under Yours → Private skills, where you can open and edit them on desktop. Its instructions are harder: staff said on October 5 and 9 that the redesigned desktop details pane no longer shows a Bot's instructions, so ask the new Bot to describe its job and rules in chat. Version 0.75.2 (October 22) redesigned the pane again, as one column with a profile you click to edit above Media, Computer and Routines tabs; the changelog does not say whether instructions are back.

Duplicate is different. It copies a Bot inside your own account, with its profile, settings, enabled skills, routines and avatar, but not its conversation history, learned memory or chat attachments.

| Part of the Bot | In a shared template? |
| --- | --- |
| Name, description and avatar | Yes |
| Skills | Yes; xAI's guide says personal or private skills are left out |
| Routines (schedules and triggers) | Yes |
| Memories | Relevant ones, per xAI's guide; personal or internal memories are excluded by default |
| First-party plugins | Listed, but the new owner reinstalls and authenticates them |
| MCP servers, custom code and scripts | No |
| The creator's computer, files and logins | No |
| Conversation history | No |

Sources: https://docs.x.ai/grok-bot/bots, https://x.ai/bot/guides/templates-for-grok-bot, https://forum.cursor.com/t/grok-bot-templates-preview-shows-skills-but-the-export-ships-skills-skills-are-never-delivered/169911, https://forum.cursor.com/t/grok-bot-macos-unable-to-see-or-edit-bot-instructions-or-skills-on-desktop/173803, https://x.ai/changelog/bot#v0.75.2

## Add a template to your account

Adding a shared Bot accepts SpaceXSI's third-party bot terms. They say third-party Bots are created by other users, that SpaceXSI does not verify, endorse or guarantee their functionality or safety, and that a Bot may read, write and send data through the accounts you connect. The copy runs on your shared computer and uses your own plan's Grok Bot usage.

1. Open the template link or a Marketplace card. The preview opens on x.ai.
2. Choose Add to Grok Bot. You need the Grok Bot app installed to finish.
3. In the app, review the context and integrations the template includes, then choose Add Bot.
4. Reinstall and authenticate the plugins it lists, and set up anything a template cannot carry, such as MCP servers or API keys.
5. Compare its skills under Connect Apps → Yours → Private skills with the preview; recreate any that are missing.
6. Before turning on its routines, give it one bounded task and read what it did.

Sources: https://docs.x.ai/grok-bot/bots, https://x.ai/bot/guides/templates-for-grok-bot, https://x.ai/legal/bot-sharing-terms, https://cursor.com/help/grok-bot/plans, https://forum.cursor.com/t/grok-bot-macos-unable-to-see-or-edit-bot-instructions-or-skills-on-desktop/173803

## Check a template before you add it

xAI's own guide says to evaluate templates the way you would evaluate skills or software, and to make sure everything in a template is exactly what you expect before installing it. This checklist is our editorial version of that advice; [Is Grok Bot safe?](https://www.grokbotwiki.com/guides/is-grok-bot-safe) explains why a new Bot can reach everything your other Bots can.

- [ ] Read the description and View details: every skill, routine and integration should fit the job it claims.
- [ ] Look hard at routines. A routine runs on its own, and even a test run can take real external actions.
- [ ] Remember what it will reach. Every Bot on your account shares one computer, its files and its logins, so a new Bot can use sessions your other Bots signed into.
- [ ] Prefer templates that stop before sending, publishing, purchasing or deleting, and add your own Ask first rules for those actions.
- [ ] Be wary of a template that asks for keys or passwords in chat. Secrets belong in a secure secret request or a computer takeover, not a message; since 0.75.2 a Bot uses a password or code you already shared in chat instead of refusing.
- [ ] Remember Vault. Cursor's help says everything saved in Settings → Vault, logins, cards and contact info, is available to every Bot on your account, so a template you add can sign in and pay with them too. Remove saved cards first if a new Bot should not be able to buy anything.

Sources: https://x.ai/bot/guides/templates-for-grok-bot, https://docs.x.ai/grok-bot/troubleshooting, https://docs.x.ai/grok-bot/faq, https://docs.x.ai/grok-bot/approvals-security-and-privacy, https://x.ai/changelog/bot#v0.75.2, https://cursor.com/help/grok-bot/secrets

## Share your own Bot as a template

A public link can be opened by anyone who has it. A Team-only link opens only for members of your team. Enterprise accounts default to Team-only; other accounts default to a public link. Team admins can turn off Public template sharing from the Cursor dashboard, and Cursor then enforces team-only sharing on its servers, including for templates that are already public; since 0.77.0 (October 26) admins can also choose between public, team-only and no template publishing at all. The same entry adds two official templates, Order Concierge, which tracks orders, refunds and returns, and Deal Watcher, which watches prices and coupons, both described as never buying without your OK.

The third-party bot terms make you responsible for what you share and tell you to review the configuration for API keys, internal URLs, customer data and personal information first. They also say people who add your Bot may not redistribute it or its configuration without your permission. If publishing a public template on a personal plan fails with A team must be selected to share a team template, Cursor staff said in September that leftover team memberships cause it and that support can remove them. The reporter said on October 10 that support had instead closed the ticket as a product issue and the error remained, so this may need a product fix rather than a support request. Since 0.75.2 (October 22), when publishing a Bot template is refused the app shows the reason, which should at least make the cause visible. And since 0.75.5 (October 23), after an account merge you keep managing the Bots you created and can share them with your team.

To share a Bot with your own team as a live, shared teammate rather than a copy, publish it as a Shared Bot (formerly Team Bot) instead; see [our Shared Bots guide](https://www.grokbotwiki.com/guides/grok-bot-team-bots).

1. Remove API keys, internal URLs, customer data and anything you would not put in a public document from the Bot's description, skills and routines.
2. Open the Share menu and choose Create template. The Bot builds the template; xAI's guide shows the same action as Share as Template in the Bot's settings.
3. Choose View template details and check exactly what was packaged.
4. Pick who can open it: Public link or Team-only.
5. Choose Copy link and send it. After you change the Bot, use Update template.

Sources: https://docs.x.ai/grok-bot/bots, https://docs.x.ai/grok-bot/faq, https://docs.x.ai/grok-bot/teams-and-enterprises, https://x.ai/legal/bot-sharing-terms, https://x.ai/bot/guides/templates-for-grok-bot, https://forum.cursor.com/t/grok-bot-public-template-publish-fails-with-a-team-must-be-selected-to-share-a-team-template-on-personal-ultra/170926, https://x.ai/changelog/bot#v0.75.2, https://x.ai/changelog/bot#v0.75.5

## The official Marketplace and community directories

The Marketplace is run by SpaceXSI and shows a selection. A Bot asked to find a template links one in chat (since October 11); the changelog does not say whether it searches only the Marketplace. Many more Bots are shared as plain public links on x.ai and posted on X, GitHub and blogs. Community directories, including [the Bot directory on this site](https://www.grokbotwiki.com/bots), collect those public links so you can search them; [our picks by task](https://www.grokbotwiki.com/bots/best) start from published criteria. Ours re-checks every link daily, shows what the share page itself says, credits the creator, and sends you to x.ai for the add step. It does not copy any Bot's configuration, and a listing is not a test result or an endorsement.

Whichever route you use, the add happens on x.ai and in the app under the same third-party bot terms. A directory listing does not make a template safer than a Marketplace card, or the reverse. Both deserve the same check.

Sources: https://x.ai/bot/marketplace, https://x.ai/legal/bot-sharing-terms

## Quick answers

### Where is the official Grok Bot Marketplace?

At x.ai/bot/marketplace. It lists Bot templates by category with the creator's name and an Add button. Inside the app, Marketplace stopped showing Featured Bots and Bot search results in 0.63.0 (September 29) and was renamed Connect Apps in 0.67.0 (October 2); it now lists plugins, and the changelog says Bot templates are on the web.

### Is a Grok Bot template the same as a share link?

Yes. Sharing a Bot creates a template and gives you a link to it; the link opens a preview on x.ai where others can add a copy. Marketplace cards and links posted elsewhere lead to the same kind of preview and the same add step.

### Does adding a template give the creator access to my account?

The docs say adding a shared Bot creates a copy on your account and does not give you the creator's computer, logins or history; they describe no link back from your copy to the creator's account. Your copy runs on your own shared computer with the accounts you connect, which is why the third-party bot terms say it may read, write and send data through them.

### Can my team stop members from publishing public templates?

Yes. Team admins control Public template sharing on the Grok Bot page of the Cursor dashboard. When it is off, sharing stays team-only, and Cursor enforces this on its servers, including for templates that are already public. Enterprise teams start with it off; other teams start with it allowed. The 0.77.0 changelog (October 26) adds a third option: admins choose whether members can publish Bot templates publicly, only to the team, or not at all.

### What is Import Bot?

A Marketplace template by Shub Gaur. Its description says it brings your setup from Claude Cowork, Codex, ChatGPT, OpenClaw and Hermes into Grok Bot, changes nothing in the old tools, and scrubs secrets before saving. That is the creator's description; we have not tested it, and it falls under the same third-party bot terms as any other template.

## Sources

- [Grok Bot Marketplace](https://x.ai/bot/marketplace)
- [Grok Bot changelog: 0.77.0, Order Concierge and Deal Watcher templates, admin publishing options (October 26)](https://x.ai/changelog/bot#v0.77.0)
- [xAI: Templates for Grok Bot (September 8, 2026)](https://x.ai/bot/guides/templates-for-grok-bot)
- [Create and manage Bots: Share a Bot](https://docs.x.ai/grok-bot/bots)
- [Grok Bot FAQ](https://docs.x.ai/grok-bot/faq)
- [Teams and enterprises: public template sharing](https://docs.x.ai/grok-bot/teams-and-enterprises)
- [Settings: plugins live in Marketplace](https://docs.x.ai/grok-bot/settings-and-notifications)
- [Approvals, security and privacy](https://docs.x.ai/grok-bot/approvals-security-and-privacy)
- [Official troubleshooting](https://docs.x.ai/grok-bot/troubleshooting)
- [SpaceXSI third-party bot terms](https://x.ai/legal/bot-sharing-terms)
- [Cursor plans and billing for Grok Bot](https://cursor.com/help/grok-bot/plans)
- [Grok Bot changelog (Marketplace changes in 0.63.0 and 0.67.0; template search in 0.69 to 0.70.2)](https://x.ai/changelog/bot)
- [Grok Bot changelog: 0.75.2 (refusal reasons, one-column Bot details pane, October 22)](https://x.ai/changelog/bot#v0.75.2)
- [Grok Bot changelog: 0.75.5 (managing and sharing Bots after an account merge, October 23)](https://x.ai/changelog/bot#v0.75.5)
- [Cursor help: store secrets securely (Vault covers every Bot)](https://cursor.com/help/grok-bot/secrets)
- [Forum: template skills not delivered on import (staff replies, August 31 and October 9)](https://forum.cursor.com/t/grok-bot-templates-preview-shows-skills-but-the-export-ships-skills-skills-are-never-delivered/169911)
- [Forum: public template publish fails, a team must be selected (staff replies, September 8 and 11)](https://forum.cursor.com/t/grok-bot-public-template-publish-fails-with-a-team-must-be-selected-to-share-a-team-template-on-personal-ultra/170926)
- [Forum: desktop details pane no longer shows instructions; skills under Private skills (staff replies, October 5 and 9)](https://forum.cursor.com/t/grok-bot-macos-unable-to-see-or-edit-bot-instructions-or-skills-on-desktop/173803)

---

# Grok Bot skills vs routines: what to save and when

> Separate the method from the schedule, then turn one successful task into a workflow you can review and repeat.

- Canonical page: https://www.grokbotwiki.com/guides/skills-vs-routines
- Sources checked: 2026-10-29
- Evidence: Official skills and routines docs, Cursor's routines and agent email help, and changelog entries 0.71.2, 0.75.2 and 0.75.5 checked October 25, 2026; how-to help and earlier changelog entries checked October 14 · workflow design and prompts are editorial templates, not tested skills · approval expiry rechecked in Cursor's how-to help and the official approvals docs October 29, 2026. Suggested workflows have not been independently tested.
- Publisher: Grok Bot Wiki, an independent guide not affiliated with SpaceXSI, xAI or X.

## The documented distinction

A skill records how to do work: the steps, decision rules, expected output and what needs approval. A routine tells one Bot when to run a workflow, on a schedule or after an event. Save the skill first; add a routine only when the method works without extra explanation.

The workflow design and prompts below are editorial examples, not tested packaged skills. If a routine you already set up is not firing, see [routines not running](https://www.grokbotwiki.com/guides/grok-bot-routines-not-running).

Sources: https://docs.x.ai/grok-bot/skills-routines-and-automations

## Where each one lives

Skills and routines are scoped differently, which matters when you reorganize Bots. The rows below paraphrase the official docs and Cursor's help as of October 25, 2026.

|  | Skill | Routine |
| --- | --- | --- |
| What it holds | How to do a task: steps, rules, output format, approval points | When one Bot runs a workflow: a schedule or an event trigger |
| Scope | One private library shared by all your Bots; a Bot can also use up to 200 skills from installed plugins (0.71.2) | Owned by a single Bot; deleting that Bot deletes its routines |
| How to create | Ask a Bot to save a finished task as a skill, or use Teach a task to record up to ten minutes of your own screen work | Ask the owning Bot in chat; edit it from the Bot's Routines list. On a Shared Bot (formerly Team Bot), owners and managers can let collaborators create routines (0.75.2) |
| Starts from | Your request; type / in the desktop composer to reference one | A schedule, or events such as Slack messages, GitHub, Linear, Sentry and PagerDuty events, email to the Bot's address (including a tagged address such as name+shop@) and webhook calls |
| Limits | A demonstration records only what is on screen, not microphone audio | Up to 50 routines per Bot, 20 most recent run records each, schedules at least five minutes apart; since 0.75.5, up to 300 runs an hour across all your routines and 200 per routine |
| Testing | Run it on a second, safe input | Test performs real work and spends usage |

Sources: https://docs.x.ai/grok-bot/skills-routines-and-automations, https://cursor.com/help/grok-bot/routines, https://x.ai/changelog/bot#v0.71.2, https://x.ai/changelog/bot#v0.75.2, https://x.ai/changelog/bot#v0.75.5

## Decide which part you actually need

Use a skill when you repeatedly explain the same method: how to classify a customer question, structure a research brief, or reconcile a weekly export. Use a routine when a known trigger should start an already-understood job. If the method changes every run, saving a schedule will not make it predictable.

For example, a competitor-update skill could define which product pages to inspect, what counts as a meaningful change, and how to cite it. Its routine could request that comparison each Monday in your time zone. These are separate decisions: the same method might also be useful on demand before a meeting.

1. Complete one task manually with the Bot and inspect the result.
2. Extract the reusable rules, including what a correct empty result looks like.
3. Run the method on a different input. Include a missing source or ambiguous case.
4. Save the revised method, then decide whether the task is frequent enough to schedule.
5. Review the proposed schedule, owner, inputs, and next occurrence before relying on unattended output. Since the October 11 changelog entry (0.69.0 to 0.70.2), the Bot sums up what a routine does and who receives the result after you save it, and each run delivers there; if that summary is not what you meant, correct it before the first run.

## Save a method with an acceptance test

Use this after a task has worked. Attach or reference the accepted example so the Bot can distinguish a formatting preference from a substantive rule.

Editorial template (replace placeholders and review access before running):

```text
Draft a reusable skill from the [accepted task/result]. Include its purpose, required inputs, method, output structure, and acceptance checks. Identify which decisions were specific to this example and turn them into explicit inputs. Define behavior for empty, missing, stale, and contradictory sources. The output must remain a draft for human review; external changes need separate authorization. Show me the proposed skill and a second example to test it against before we schedule anything.
```

## Make a schedule earn its place

Our suggested release gate is three varied examples that produce useful output without extra explanation. This is a practical editorial threshold, not a statistical reliability guarantee. Keep the accepted outputs so a future change can be compared against them.

Specify the reporting window separately from the run time. A Monday morning run might cover the previous calendar week, the last seven complete days, or changes since the last successful run. Choosing explicitly prevents gaps and double counting. For a worked example, the [morning brief recipe](https://www.grokbotwiki.com/workflows/morning-brief) pairs a skill with a weekday routine.

Three timing details catch people out. A new routine does not run when you create it; it waits for its next scheduled time, so a daily 8:00 routine created at 8:05 first runs the next morning. Schedules follow the Timezone setting under Bot in Settings, which auto-detects from the computer you are on unless you pick one. And every run, including a test, uses your weekly allowance: Cursor's help warns that frequent schedules and Slack triggers on busy channels spend it quickly.

- [ ] The method is useful without a schedule.
- [ ] The owner and time zone are explicit, When to run shows the schedule you meant, and the Bot's summary after saving names the right recipient.
- [ ] A failed input produces a visible failure, not a recycled report.
- [ ] A repeated run has a defined outcome and cannot accidentally duplicate a write.
- [ ] Event triggers are narrow: a mention or phrase in one channel, not every message in all of Slack.

Sources: https://docs.x.ai/grok-bot/skills-routines-and-automations, https://cursor.com/help/grok-bot/routines, https://x.ai/changelog/bot

## Plan for approvals nobody is watching

A routine runs while you are away, so its approval cards can go unanswered. Cursor's help and the official docs, checked October 29, say approvals raised by routines, triggers or other Bots expire after about 30 minutes and the action does not run. Turn on notifications for Bots that own routines, or decide in advance which narrow actions may go through without you.

Since 0.68.0 your saved approval rules appear under Custom Rules in Settings; Always allow on an approval card adds one there. Keep sending, purchasing, deleting and publishing behind Ask first rules, which win when both kinds of rule match, and leave the routine's email and Slack draft cards on: 0.64.0 lets you disable drafts per Bot, after which that Bot sends directly. If a run hangs, Stop ends a stuck Bot within about 30 seconds since 0.68.1. Stop is not undo: the same release notes say a Send cut off by Stop still goes out. Our [permission boundaries guide](https://www.grokbotwiki.com/guides/permission-boundaries) turns this into a worksheet.

One distinction got sharper on October 23. Version 0.75.5 lets emails and Slack messages you ask for in chat go out once Auto-review allows them, but sends on routine and other turns still wait as drafts. Cursor's agent email help says the same for the Bot's own address: a routine can read mail, summarize it and draft a reply, and anything it wants to send waits until you press Send, with no option for unattended sending. A routine that is meant to deliver something should post its result to the chat or a Slack channel, not rely on sending an email by itself.

Sources: https://cursor.com/help/grok-bot/how-to, https://x.ai/changelog/bot, https://x.ai/changelog/bot#v0.75.5, https://cursor.com/help/grok-bot/agent-email

## October changes to how routines run

Three October releases changed what a routine does when something goes wrong, which is most of what unattended work is about. The rows paraphrase the changelog and Cursor's routines help as of October 25, 2026.

| Change | What the source says | What to do |
| --- | --- | --- |
| Hourly run limits (0.75.5) | Your routines can run up to 300 times an hour in total, up from 100, and each routine up to 200 times. Cursor's help says a run past either limit fails with Automation run rate limit exceeded and is not retried, and that a limit shared by all Grok Bot routines can cause the same error even below yours, a known issue | Narrow busy triggers; rerun a failed run yourself with Test, or resend the webhook call |
| Sign-in during a run (0.71.2) | When a routine needs to sign in to a site, it asks you in chat at that step instead of quietly stopping | Turn on notifications for Bots that own routines so the request does not sit unanswered |
| Signed-out connectors (0.75.2) | When a routine hits a signed-out connector, the chat shows that connector's Reconnect card, at most once a day | Reconnect promptly; runs before you do will not have that connector |
| Reading inboxes (0.75.2) | Routines can read the Bot's inboxes; since 0.71.2, a routine on a tagged address such as name+shop@ runs only for that tag's mail | Give each mail-driven job its own tag rather than one routine reading everything |
| Webhooks (0.75.2) | A webhook routine's menu shows its URL and key, and the key stays hidden until you reveal it. Cursor's help: senders include it as Authorization: Bearer <key>, and a 200 response means a run started, not that it finished | Treat the key like a password; check the chat for the result |
| Delivery and pausing (0.75.2) | A routine's result still reaches you if you send a message before the Bot finishes handing it off; pausing and resuming keeps your last choice, even from two devices | Nothing to change |

Sources: https://x.ai/changelog/bot#v0.71.2, https://x.ai/changelog/bot#v0.75.2, https://x.ai/changelog/bot#v0.75.5, https://cursor.com/help/grok-bot/routines

## Sources

- [Official skills and routines guide](https://docs.x.ai/grok-bot/skills-routines-and-automations)
- [Cursor help: Grok Bot routines (hourly run limits, webhooks)](https://cursor.com/help/grok-bot/routines)
- [Cursor help: give your Bot an email address (email routines)](https://cursor.com/help/grok-bot/agent-email)
- [Cursor help: how-tos (approval expiry)](https://cursor.com/help/grok-bot/how-to)
- [Grok Bot changelog](https://x.ai/changelog/bot)
- [Grok Bot changelog: 0.71.2 (routine sign-in asks in chat, 200 plugin skills, October 14)](https://x.ai/changelog/bot#v0.71.2)
- [Grok Bot changelog: 0.75.2 (routines read inboxes, Reconnect card, webhook key, October 22)](https://x.ai/changelog/bot#v0.75.2)
- [Grok Bot changelog: 0.75.5 (300 runs an hour, routine sends wait as drafts, October 23)](https://x.ai/changelog/bot#v0.75.5)

---

# Grok Bot connectors or browser: choose the right route

> When to use a Connect Apps plugin and when to let a Bot use the browser: map the action, test access with a small read, and know what each route shares.

- Canonical page: https://www.grokbotwiki.com/guides/connectors-vs-browser
- Sources checked: 2026-10-25
- Evidence: Cursor's plugin and secrets (Vault) help and changelog entries 0.71.2, 0.75.2 and 0.75.5 checked October 25, 2026; official computer and apps docs and how-to help checked October 11 · comparison procedure is an editorial method; no connector tested by us. Suggested workflows have not been independently tested.
- Publisher: Grok Bot Wiki, an independent guide not affiliated with SpaceXSI, xAI or X.

## What is documented

Use a plugin when one exists for the job, and the browser when it does not. The docs say a connector is usually more reliable than clicking through a website, and the browser suits services with no connector or visual work a connector does not expose. Both routes are account-wide: an installed plugin and a browser sign-in are available to every Bot on your account.

Plugins are installed from Connect Apps, the in-app section that replaced Marketplace in 0.67.0, or from a Connect card in chat; on desktop you attach one to a request by typing @. The comparison procedure below is our editorial method. We have not verified any particular connector's current action coverage. For custom MCP servers and the known issues, see [Grok Bot plugins, connectors and MCP](https://www.grokbotwiki.com/guides/grok-bot-plugins-mcp).

Sources: https://docs.x.ai/grok-bot/computer-and-apps, https://cursor.com/help/grok-bot/connect-apps

## How the two routes differ

The rows below paraphrase the docs and Cursor's help as of October 25, 2026.

|  | Plugin (connector) | Browser on the Bot's computer |
| --- | --- | --- |
| Best for | Structured reads and writes the plugin exposes, such as searching mail or posting to Slack | Services without a plugin, visual checks, screens a plugin does not cover |
| Sign-in | Authorize or Authenticate in your own browser; tokens stay on Cursor's servers | Take over the Bot's screen and type the password or code yourself; since 0.75.5 the Bot can also use a login saved in Vault, then a connected password manager, then ask with a Secure Form |
| Who can use it | Every Bot on your account; a teammate's Shared Bot (formerly Team Bot) asks first | Every Bot on your account, because sessions persist on the shared computer |
| What it can do | Only what the authorized account can already do; it cannot raise access or change sharing | Whatever that signed-in account can do on the site |
| When it breaks | Shows Needs auth or Disconnected; choose Authenticate or Reconnect | The site expires the session or asks to verify again; the Bot should pause and ask you |

Sources: https://docs.x.ai/grok-bot/computer-and-apps, https://docs.x.ai/grok-bot/security, https://cursor.com/help/grok-bot/connect-apps, https://cursor.com/help/grok-bot/how-to, https://cursor.com/help/grok-bot/secrets

## October changes that nudge you toward connectors

Several October releases make the connector route easier to pick. Since 0.75.2 (October 22), naming a service makes the Bot show that connector's connect card in its first reply, and a connector that signs you out or rejects a sign-in says why and how to fix it. Since 0.75.5 (October 23), when the Bot hands you its computer to sign in to a site that has a connector, it also offers that connector's connect card. Connector calls also got more patient in 0.71.2 (October 14): they wait up to two minutes instead of timing out after one, longer while the connector reports progress.

The browser route changed too. Vault, added in 0.75.5, lets a Bot sign in with a login you saved in Settings → Vault; Cursor's help says the Bot never sees the saved password, but every Bot on your account can use every saved login, so a Vault login widens the shared browser in the same way a manual sign-in does. With Route traffic through this computer on, Settings now shows how many sites were blocked because they resolve to a private or VPN address. If a site has a connector, prefer it: the sign-in stays a token on Cursor's backend rather than a session on the shared computer.

Sources: https://x.ai/changelog/bot#v0.71.2, https://x.ai/changelog/bot#v0.75.2, https://x.ai/changelog/bot#v0.75.5, https://cursor.com/help/grok-bot/secrets, https://docs.x.ai/grok-bot/security

## Choose by action, not by app name

A connector for a service may expose search but not the export, filter, or historical records your task needs. Write the operation first: retrieve this account's open tickets, including their latest replies and timestamps. Then check whether the available tool can perform that operation under the account you intend to use.

A browser may be the practical choice for checking layout, reviewing a chart, or handling an unsupported screen. It also adds page state to the problem: selected account, filters, open dialogs, and pagination can change the result. Record these details in the task rather than assuming the default screen is correct.

1. Name one required read operation and the fields the result must contain.
2. Check the available connection's documented or displayed actions and requested access.
3. Authorize only the account and scope needed for the pilot.
4. Run a small read and compare it with the same records in the source application.
5. If browser work is necessary, specify the account, filters, date range, and a stopping point before any write.

## Probe access without expanding the task

Successful authentication is only the beginning. The useful test is whether the intended records and fields can actually be read.

Editorial template (replace placeholders and review access before running):

```text
For [service/account], establish whether you can read [specific records and fields] using the available connector. Read only [small sample]. Return the source links or IDs, applied filters, retrieval time, and missing fields. Do not create, edit, send, or delete anything. If the connector cannot perform this operation, explain the exact gap and propose the smallest browser-based check. Ask me to complete any required sign-in securely.
```

## Leave a short access note

Keep a note beside the workflow containing the connection used, permitted action, account, successful sample, and last test date. This turns a future 'it stopped working' report into a narrower question: did access expire, did action coverage change, or did the source move?

Do not broaden privileges merely to make an inconvenient task pass. First determine which missing action or record caused the failure. The note should describe access, never contain passwords or secret values. Directory Bots that work through a specific app are grouped on [our works-with pages](https://www.grokbotwiki.com/bots/works-with); check what each asks to connect.

- [ ] The sample matches the source application.
- [ ] All required fields are present, or omissions are explicit.
- [ ] The method handles more than the first page of results when completeness matters.
- [ ] The workflow has a clear sign-in or missing-access stopping point.

## When a connection is not ready

Added does not mean signed in. Cursor's help says a plugin showing Needs auth or Disconnected needs Authenticate (Authorize on mobile), and that an unfinished sign-in page can be retried with Reconnect on the plugin or Reopen on the chat card. Gmail connects one mailbox at a time, so disconnect the current one before authorizing another; some plugins, such as Notion, support several accounts.

Two blocks come from outside Grok Bot. If a Google Workspace admin has not marked Grok as trusted, Google sign-in can be refused until they do. If your Cursor team admin has turned a plugin off, it shows Disabled by team admin. Work apps behind Okta or other single sign-on are signed in on the Bot's computer through a takeover, which makes them browser sessions every Bot can reach. Cursor's help also lists a known Zoom authorization error from the desktop app, with no workaround yet.

Sources: https://cursor.com/help/grok-bot/connect-apps, https://cursor.com/help/grok-bot/how-to

## Sources

- [Official computer and apps guide](https://docs.x.ai/grok-bot/computer-and-apps)
- [Cursor help: connect plugins](https://cursor.com/help/grok-bot/connect-apps)
- [Cursor help: store secrets securely (Vault sign-in order)](https://cursor.com/help/grok-bot/secrets)
- [Grok Bot changelog: 0.71.2 (two-minute connector calls, October 14)](https://x.ai/changelog/bot#v0.71.2)
- [Grok Bot changelog: 0.75.2 (connect card on first reply, sign-out reasons, October 22)](https://x.ai/changelog/bot#v0.75.2)
- [Grok Bot changelog: 0.75.5 (Vault, connect card during sign-in handoff, October 23)](https://x.ai/changelog/bot#v0.75.5)
- [Grok Bot security: plugin tokens](https://docs.x.ai/grok-bot/security)
- [Cursor help: how-tos (reconnect a plugin, single sign-on)](https://cursor.com/help/grok-bot/how-to)

---

# Grok Bot plugins, connectors and MCP: setup and known issues

> How Grok Bot plugins work after the Connect Apps change: install and authorize, where tokens live, adding a custom MCP server, and open OAuth issues.

- Canonical page: https://www.grokbotwiki.com/guides/grok-bot-plugins-mcp
- Sources checked: 2026-10-29
- Evidence: Changelog entry 0.78.1 (October 27) and Cursor's connect apps help read October 29, 2026; entry 0.77.0 (October 26) read October 28, 2026; entry 0.75.8 read October 27; changelog entries 0.71.2, 0.75.2 and 0.75.5, Cursor's connect apps help (its connect plugins address now redirects there) and docs.x.ai checked October 25, 2026; earlier entries checked October 14 · forum known issues rechecked October 25 where noted, otherwise as of October 11 · Cursor staff forum replies attributed, not reproduced · no connector tested by us. Suggested workflows have not been independently tested.
- Publisher: Grok Bot Wiki, an independent guide not affiliated with SpaceXSI, xAI or X.

## The short answer

Plugins, also called connectors, let a Bot use services like Gmail, Slack, Notion or Linear through a structured connection instead of clicking through a website. Install one from Connect Apps (formerly Marketplace) in the sidebar, finish the sign-in in your browser, and every Bot on your account can use it. A custom MCP server must be reachable over public HTTPS.

This page follows the official docs, Cursor's help pages and the changelog through 0.75.5 (October 23), checked October 25, 2026, plus Cursor staff replies on the forum, which we attribute and have not reproduced. We have not tested any connector.

| Route | Use it when | Keep in mind |
| --- | --- | --- |
| A plugin from Connect Apps | The service is in the catalog | Account-wide; tokens stay on Cursor's backend; Added is not the same as signed in |
| A custom remote MCP server | You run or trust an HTTPS MCP endpoint | Must be publicly reachable; OAuth only, no secret headers; redirect issues are open |
| A command (stdio) MCP server on the Bot's computer | A server ships as a package you can run with npx or uvx | Runs on the cloud computer, not your laptop; keep credentials out of its command and arguments |
| The Bot's browser | There is no plugin, or the work is visual | Uses your signed-in session on the shared computer; see our [connectors or browser guide](https://www.grokbotwiki.com/guides/connectors-vs-browser) |
| A secret for a script | An API has no plugin sign-in | Use a secure secret request; never paste a key into chat |
| The Email plugin | A Bot needs its own inbox, for sign-ups, receipts or mail-triggered routines | Gives your Bots a new mail.grokbot.com address rather than connecting one you have; one per account, permanent |

Sources: https://docs.x.ai/grok-bot/computer-and-apps, https://docs.x.ai/grok-bot/security, https://cursor.com/help/grok-bot/connect-apps, https://cursor.com/help/grok-bot/agent-email, https://forum.cursor.com/t/grokbot-custom-connectors/169965

## Plugins, connectors, Marketplace, Connect Apps: the names

The docs use connector and plugin for the same thing: connectors are installed as plugins. Where you install them has moved. The changelog shows the sidebar's Marketplace button became Connect apps in 0.60.0 (September 26), Marketplace stopped listing Bots and searched only plugins in 0.63.0 (September 29), and Marketplace became Connect Apps, with category chips and Recommended for you first, in 0.67.0 (October 2). Bot templates moved to the web; see our [Marketplace and templates guide](https://www.grokbotwiki.com/guides/grok-bot-marketplace-templates).

The documentation is catching up. By October 11, Cursor's help pages and the docs.x.ai page on connecting apps (updated October 9) said Connect apps, while the docs.x.ai settings and skills pages still said Marketplace. A Cursor staff member's October 5 directions cover both: Marketplace (or Connect apps) at the bottom of the sidebar, or Cmd+Shift+M; the docs' shortcut list also gives Cmd/Ctrl+Shift+W. Since 0.75.2, Connect Apps shows each plugin's own logo and waits longer for your plugins instead of showing Couldn't refresh, and built-in plugins no longer offer an Uninstall that failed.

GitHub is a special case; staff said on September 28 that it is now built into Grok Bot through your connected Cursor GitHub account, replacing the old marketplace plugin. The October releases extended it. Since 0.71.2, when GitHub cannot see a repository the Bot stops retrying and links the GitHub page where you grant access, and when GitHub is not connected it offers a single Connect GitHub action. Since 0.75.2 the GitHub connector can list your repositories, compare commits, list a pull request's commits and read branch and issue comments, and pull requests, issues and repositories mentioned in replies are links.

Sources: https://x.ai/changelog/bot, https://x.ai/changelog/bot#v0.71.2, https://x.ai/changelog/bot#v0.75.2, https://docs.x.ai/grok-bot/computer-and-apps, https://docs.x.ai/grok-bot/settings-and-notifications, https://docs.x.ai/grok-bot/chat-and-collaboration, https://cursor.com/help/grok-bot/connect-apps, https://forum.cursor.com/t/grok-bot-delisted-github-plugin-48677658-cant-be-uninstalled-or-reconfigured-and-shows-connected-with-0-tools-after-a-401/172955

## Install and authorize a plugin

These steps combine the official docs and Cursor's help. On mobile, Cursor's help says to tap your avatar at the top left and choose Connect apps.

1. Open Connect Apps in the sidebar, or follow a Connect card in chat.
2. Find the plugin and add it. Since 0.63.0, a plugin that needs a sign-in, such as Gmail, starts that sign-in right away. Since 0.75.8 (October 24), a plugin a Bot installs while it is working is usable in that same task: the Bot can use the plugin's skills right away.
3. Finish the provider's sign-in in your browser within about 10 minutes. If sign-in does not finish, choose Reconnect on the plugin, or Reopen on the in-chat card, to bring the sign-in page back; if the card says it failed, choose Retry.
4. Confirm the plugin appears under Installed and is authorized. Added only means installed; choose Authenticate (Authorize on the phone) if it shows Needs auth or Disconnected.
5. In chat, type @ to attach the connector to a task. To review or switch off individual tools, open Your plugins → Manage plugins and skills.

- [ ] Shortcut: the October 11 changelog entry (0.69.0 to 0.70.2) says giving a Bot a connector link installs the matching catalog plugin when there is one, and plugins installed from chat or the web are ready on the Bot's computer.
- [ ] Glean asks for your Glean MCP URL when you add it, then connects after you sign in to Glean in the browser; ask your Glean admin for the URL first.
- [ ] QuickBooks Online is now available to connect, according to the same entry.
- [ ] Connectors that come with an app, such as Figma, Notion and Canva, can show it as an interactive card in the chat.
- [ ] Since 0.75.2 (October 22), naming a service makes the Bot show that connector's connect card in its first reply, and a connector that signs you out or rejects a sign-in says why, such as a restricted Google account, and how to fix it.
- [ ] Setting up a plugin with your own OAuth client now lists the callback URLs to register (0.75.2); register exactly those with the provider before you sign in.
- [ ] Zoho CRM can be connected, and you choose your account's regional data center before you sign in (0.75.2).
- [ ] Plugins with several servers, such as Salesforce, show each server as its own row since 0.75.5 (October 23), so sign in to every row, not just the first.
- [ ] Since 0.75.5, when the Bot hands you its computer to sign in to a site that has a connector, it also offers that connector's connect card. The docs say a connector's token stays on Cursor's backend, while a browser sign-in lives on the shared computer.

Sources: https://docs.x.ai/grok-bot/computer-and-apps, https://docs.x.ai/grok-bot/settings-and-notifications, https://cursor.com/help/grok-bot/connect-apps, https://cursor.com/help/grok-bot/how-to, https://x.ai/changelog/bot, https://x.ai/changelog/bot#v0.75.2, https://x.ai/changelog/bot#v0.75.5

## Where tokens live, and who can use a plugin

The docs say OAuth tokens stay on Cursor's connector backend, Bots invoke tools without receiving them, and tokens are never stored on the Bot's computer. That makes a plugin sturdier than a browser login, which depends on cookies on the shared computer. A plugin can do only what the connected account can already do; it cannot raise your access or change sharing. The Slack plugin, for example, posts as the Slack user you connected and only where that user can post.

Installed plugins are account-wide: every Bot on your account can use every connected account. Cursor's help says some plugins, such as Notion, can add a second account, while Gmail connects one mailbox at a time. On a Cursor team, the team's connector policy decides which plugins members can use, a blocked one shows Disabled by team admin, and the MCP allowlist is Enterprise only. Blocking a plugin does not block that service's website. Shared Bots treat plugins differently again; see [our Shared Bots guide](https://www.grokbotwiki.com/guides/grok-bot-team-bots).

Some reading needs no plugin at all. The docs say Bots can search and read what is public on X without connecting an account; add the X plugin only for your DMs, bookmarks, home timeline or who liked your posts. One exception to removing a plugin: since 0.75.5, asking a Bot about your X account connects X through your linked X account even if you removed the X plugin, and connecting X also connects X Money.

Plugin skills have a higher ceiling: since 0.71.2 (October 14) a Bot can use up to 200 skills from your installed plugins instead of 24. And since 0.75.2, turning a Bot's tool on or off applies the state you saw, so an outdated list cannot turn a blocked tool back on.

Sources: https://docs.x.ai/grok-bot/teams-and-enterprises, https://docs.x.ai/grok-bot/security, https://docs.x.ai/grok-bot/computer-and-apps, https://cursor.com/help/grok-bot/connect-apps, https://cursor.com/help/grok-bot/how-to, https://x.ai/changelog/bot#v0.71.2, https://x.ai/changelog/bot#v0.75.2, https://x.ai/changelog/bot#v0.75.5

## Add a custom MCP server

There is no settings form for this. A Cursor staff member said on August 30 that you tell the Bot in chat to add the MCP server, and that it must be a public HTTPS URL using streamable HTTP or SSE. OAuth discovery runs from Cursor's infrastructure, so another staff answer on August 12 said the endpoint must be reachable over HTTPS from the open internet; a server behind your VPN or on localhost will not work. Staff also said on September 17 that connectors authenticate only through OAuth, with no safe way to enter a secret header.

Servers on your own laptop are not attached. Staff said on August 13 that Grok Bot does not attach MCP servers that run on your own machine, whether over stdio or on localhost. A command-style server can instead run on the Bot's cloud computer: a staff reply on September 8 suggested registering servers as npx or uvx commands or keeping wrapper scripts on the computer, and on September 28 staff explained re-pointing a custom stdio server by adding it again under the same name. The Shared Bots docs warn that teammates can read a command server's command and arguments, so never put a credential in either.

Editorial template (replace placeholders and review access before running):

```text
Add a custom MCP server named [name] at [https URL] using [streamable HTTP or SSE]. Do not paste any key or token into this chat; if the server needs one, start its OAuth sign-in or ask me for a secure secret. When it is connected, list the tools it exposes and run one read-only call on [harmless test input]. Do not call any tool that creates, changes or deletes data.
```

Sources: https://forum.cursor.com/t/grokbot-custom-connectors/169965, https://forum.cursor.com/t/grok-bot-custom-remote-mcp-oauth-never-starts-fetch-failed-same-url-works-in-cursor-ide/168188, https://forum.cursor.com/t/grok-bot-custom-mcp-oauth-fails-before-sign-in-redirect-uri-not-allowed/171877, https://forum.cursor.com/t/does-grok-bot-support-local-mcp-e-g-workflowy/168182, https://forum.cursor.com/t/grok-bot-stdio-mcp-keeps-spawn-path-into-deleted-agent-secrets/170901, https://forum.cursor.com/t/grok-bot-edit-a-custom-stdio-mcp-servers-command-args-env-in-place-without-losing-its-instructions/172953, https://docs.x.ai/grok-bot/shared-bots

## Known issues as of October 28

These are the open or recently fixed plugin problems with a Cursor staff reply or a help-page entry. On October 25 we rechecked the custom MCP OAuth, MCP-Protocol-Version, outbound-traffic and Vercel threads and Cursor's help page; the other forum rows are as of October 11. None of the changelog entries through 0.78.1 (October 27) name the open issues below as fixed, although 0.77.0 says a custom MCP server that uses a private certificate authority now works once you approve that authority, and that a connector whose server refuses registration shows Error instead of a sign-in that cannot work.

| Symptom | What Cursor said | Status |
| --- | --- | --- |
| A connector sign-in started from a connect card fails if you take more than a few minutes, or a connect card appears for an error that is not a sign-in | 0.77.0 (October 26): connector sign-ins can finish up to an hour after you start them; connect cards appear only when a connector says you need to sign in, keep waiting while your newest sign-in page is open, and a refused sign-in sends you back with the reason | Fixed (October 26) |
| Google apps ask you to reconnect when Google is only throttling requests, or a Google account without Gmail keeps disconnecting | 0.77.0: Google apps stay connected and the Bot says to try again later; an account without Gmail stays connected and the Bot asks for one that has Gmail | Fixed (October 26) |
| Connector buttons read differently in different places, so it is unclear whether a plugin is signed in | 0.77.0: buttons say Connect everywhere, a signed-out connector shows Not connected, Your plugins offers Reconnect for one that stopped working, and plugins show Connecting… then Connected during sign-in | Changed (October 26) |
| Background work keeps calling a connector that signed you out | 0.77.0: it stops and tells you to reconnect the connector; when background work needs one of your apps, the Bot asks with an allow card in the app, or Allow once and Skip in Slack | Fixed (October 26) |
| App cards, plugin rows and connector errors show an internal ID instead of the app's name | 0.78.1 (October 27): they show the connector's name; when a connector needs a permission its connection cannot request, the Bot says reconnecting will not help; when a plugin is not available, the Bot says so instead of listing the whole catalog | Fixed (October 27) |
| A connect card says the sign-in did not finish while you are still signing in, or signing in to a Google account that is already connected produces several reconnect cards | 0.78.1: after 10 minutes the card asks Still signing in?; a Google account that is already connected is reused, with one reconnect card; Google Calendar asks you to reconnect only when signing in again can grant the missing permission; connector tools stay listed while a tool list reloads | Fixed (October 27) |
| Remove from Slack leaves Slack connected, or a Slack connect link opened while signed in to another account keeps failing | 0.78.1: Remove from Slack disconnects Slack; the link works once you sign in as the right account and connect again | Fixed (October 27) |
| The Tailscale plugin installs on an account that cannot use it | 0.78.1: it shows Not available yet on those accounts | Changed (October 27) |
| Custom MCP OAuth fails before sign-in: redirect_uri not allowed (for example behind Cloudflare Access) | Registration sends a cursor:// callback that https-only providers reject. For Cloudflare Access, staff confirmed on October 19 that adding cursor://anysphere.cursor-mcp/oauth/callback to the application's allowed redirect URIs through the Access Applications API works. Providers that accept only https or loopback callbacks, such as Home Assistant, still fail, and on October 21 staff traced a separate Home Assistant failure to an oversized header on Cursor's client metadata document, with no workaround yet | Workaround for Cloudflare Access; open for other providers (October 21) |
| A custom remote MCP server connects and lists tools, then later calls fail with an empty HTTP 400 | When Grok Bot reuses an MCP session it leaves out the MCP-Protocol-Version header, which strict servers reject; staff confirmed it and flagged a fix. Reconnecting does not help; a server that accepts requests without the header works | Open (October 8) |
| A command (stdio) MCP server or script on the Bot's computer cannot reach a database, mail, SSH or other non-HTTPS port | Since about October 1 some Bot computers allow outbound connections only over HTTPS on port 443; staff said on October 2 it is not intended, is tracked and needs no reset; HTTPS endpoints and cloning over HTTPS still work | Open; users still reporting it October 22 |
| Zoom authorization fails with error 4700 (Invalid redirect) | Cursor's help calls it a known issue with no workaround | Open (help page, October 25) |
| SharePoint admin consent fails with AADSTS50011 (redirect URI mismatch) on Application-level permissions | Cursor's help calls it a known issue; the workaround is to connect with Delegated permissions from the dashboard's Integrations page | Open, with workaround (help page, October 25) |
| A connector's new tools or fields, for example on X, are missing until you reconnect it | 0.75.8 (October 24): Bots can use them without you reconnecting it | Fixed (October 24) |
| A connector whose sign-in expired still shows Connected in the app while the Bot says it is signed out | 0.75.8 (October 24), on Grok Bot 0.71.2 or later: the app shows Authenticate instead, matching what the Bot says | Fixed (October 24) |
| Images a connector returns as files come through garbled, as do other binary files | 0.75.8 (October 24): images reach the Bot as images and other binary files are no longer read as text | Fixed (October 24) |
| Connector calls time out after one minute | 0.71.2 (October 14): calls now wait up to two minutes, longer while the connector reports progress | Fixed (October 14) |
| A plugin with several servers, such as Salesforce, shows only one, so you cannot sign in to the rest | 0.75.5 (October 23): each server shows as its own row | Fixed (October 23) |
| Vercel plugin: redirect URL is invalid | Broken since about September 16; staff said the team had identified the cause | No fix confirmed in the thread (September 21) |
| Plugin shows connected but the Bot reports MCP server not found | A server-side change left background tasks without connectors; a fix rolled out | Fixed (September 28) |
| An old GitHub plugin cannot be removed and shows 0 tools | GitHub is now built in through your Cursor GitHub account; staff removed leftovers on request | Workaround (September 28 to October 7) |
| A rate-limited connector makes the Bot loop, or calls fail on a Notion link or Slack channel name | Changelog entry of October 11 (0.69.0 to 0.70.2): Bots now wait for the retry delay, and connector calls fail less often, including fixes for wrongly shaped arguments, Notion links and Slack channel names | Fixed (October 11) |
| A Bot signs you out of a connector while repairing it | Same entry: Bots no longer do this, and a connector account you signed out of stays signed out | Fixed (October 11) |
| Connecting fails because another app is using the sign-in port | Changelog 0.67.0: connecting an app now finishes anyway, and a failed sign-in page explains why | Fixed (October 2) |

Sources: https://x.ai/changelog/bot#v0.78.1, https://forum.cursor.com/t/grok-bot-custom-mcp-oauth-fails-before-sign-in-redirect-uri-not-allowed/171877, https://cursor.com/help/grok-bot/connect-apps, https://forum.cursor.com/t/grok-bot-zoom-plugin-oauth-hardcodes-http-localhost-8787-callback-zoom-rejects-hostname-localhost-error-4700/169991, https://forum.cursor.com/t/grok-bot-vercel-plugin-649-oauth-fails-with-app-configuration-error-redirect-url-is-invalid/168499, https://forum.cursor.com/t/grok-bot-inkbox-mcp-shows-connected-with-51-tools-but-agent-gets-mcp-server-not-found/173208, https://forum.cursor.com/t/grok-bot-delisted-github-plugin-48677658-cant-be-uninstalled-or-reconfigured-and-shows-connected-with-0-tools-after-a-401/172955, https://x.ai/changelog/bot, https://x.ai/changelog/bot#v0.71.2, https://x.ai/changelog/bot#v0.75.5, https://x.ai/changelog/bot#v0.77.0, https://forum.cursor.com/t/grok-bot-remote-mcp-requests-omit-mcp-protocol-version-on-reused-sessions-causing-empty-http-400/174114, https://forum.cursor.com/t/grok-bot-computer-all-outbound-non-https-traffic-blocked-since-oct-1-mysql-ssh-imap-smtp-ftp-time-out/173504

## Plugins in templates and Shared Bots

A shared Bot template lists its first-party plugins, but each new owner reinstalls and authenticates them; xAI's template guide says templates do not carry MCP servers, custom code or scripts. On a Shared Bot, a plugin that signs in with an account uses the account of whoever is talking to the Bot, while a plugin configured with a key uses the Bot's own credential for everyone, and a custom Remote HTTPS server can use either. Since 0.71.2, plugins on a Shared Bot use team admin settings, such as the Datadog site, and since 0.75.5 Shared Bots name connectors as your plugin list does when they ask to use one or say whose they used. Since 0.77.0 (October 26), plugins a team admin would not allow show Disabled by team admin, and linked teammates on a Shared Bot use their own connectors and memory; the docs now call Team Bots Shared Bots. For Gmail and Google Workspace specifics, see [our Gmail guide](https://www.grokbotwiki.com/guides/grok-bot-gmail-google-workspace); for the security model, see [Is Grok Bot safe?](https://www.grokbotwiki.com/guides/is-grok-bot-safe).

Sources: https://x.ai/bot/guides/templates-for-grok-bot, https://docs.x.ai/grok-bot/shared-bots, https://x.ai/changelog/bot#v0.71.2, https://x.ai/changelog/bot#v0.75.5, https://x.ai/changelog/bot#v0.77.0

## Quick answers

### Where did Marketplace go in Grok Bot?

It was renamed. The changelog shows the sidebar button became Connect apps in 0.60.0 (September 26), Marketplace stopped showing Bots and focused on plugins in 0.63.0 (September 29), and Marketplace became Connect Apps in 0.67.0 (October 2). Bot templates moved to the web Marketplace at x.ai/bot/marketplace. A Cursor staff member wrote on October 5: open Marketplace (or Connect apps) at the bottom of the sidebar, or press Cmd+Shift+M; the docs also list Cmd/Ctrl+Shift+W.

### Can Grok Bot use an MCP server running on my laptop?

No. A Cursor staff member said on August 13 that Grok Bot does not attach MCP servers that run on your own machine, whether over stdio or listening on localhost, because Bots work on a cloud computer. Use a public HTTPS server, a catalog plugin, or the Bot's browser. Staff have since described running stdio servers on the Bot's own cloud computer instead.

### Does the Bot see my OAuth tokens?

No, according to the docs. OAuth tokens stay on Cursor's connector backend, Bots invoke tools without receiving them, and tokens are never stored on the Bot's computer. A plugin can do only what the connected account can already do in that service.

### Can I connect two accounts for the same service?

For some plugins. Cursor's help says Notion and some others can add a second account with Add Another Account, and the 0.77.0 changelog (October 26) says adding a second Gmail or Google Drive account now opens Google's account picker, and removing one account leaves the others in place. Every Bot on your account can use every connected account, so disconnect one a Bot should not use.

### Do Bot templates include plugins and MCP servers?

Plugins are listed, but each new owner reinstalls and authenticates them. xAI's September 8 template guide says templates do not carry MCP servers, custom code or scripts, and suggests having the Bot write setup instructions into the template for complex setups.

## Sources

- [Computer and apps: connect an app](https://docs.x.ai/grok-bot/computer-and-apps)
- [Settings: plugins and skills](https://docs.x.ai/grok-bot/settings-and-notifications)
- [Teams and enterprises: connector policy](https://docs.x.ai/grok-bot/teams-and-enterprises)
- [Grok Bot security](https://docs.x.ai/grok-bot/security)
- [Shared Bots (formerly Team Bots): plugin types](https://docs.x.ai/grok-bot/shared-bots)
- [Message and collaborate: keyboard shortcuts](https://docs.x.ai/grok-bot/chat-and-collaboration)
- [Cursor help: give your Bot an email address](https://cursor.com/help/grok-bot/agent-email)
- [Cursor help: connect plugins](https://cursor.com/help/grok-bot/connect-apps)
- [Cursor help: how-tos (reconnect a plugin, second accounts)](https://cursor.com/help/grok-bot/how-to)
- [Grok Bot changelog: 0.78.1 (connector names instead of IDs, Still signing in?, Slack disconnect, October 27)](https://x.ai/changelog/bot#v0.78.1)
- [Grok Bot changelog: 0.77.0 (Connect and Reconnect states, private CA for custom MCP, hour-long sign-ins, October 26)](https://x.ai/changelog/bot#v0.77.0)
- [Grok Bot changelog: 0.75.8 (new connector tools without a reconnect, Authenticate state, October 24)](https://x.ai/changelog/bot#v0.75.8)
- [Grok Bot changelog (Marketplace to Connect Apps, 0.60 to 0.67; connector changes in 0.69 to 0.70.2)](https://x.ai/changelog/bot)
- [Grok Bot changelog: 0.71.2 (200 plugin skills, two-minute connector calls, October 14)](https://x.ai/changelog/bot#v0.71.2)
- [Grok Bot changelog: 0.75.2 (Zoho CRM, GitHub, own OAuth client callback URLs, October 22)](https://x.ai/changelog/bot#v0.75.2)
- [Grok Bot changelog: 0.75.5 (plugins with several servers, October 23)](https://x.ai/changelog/bot#v0.75.5)
- [xAI: Templates for Grok Bot (September 8, 2026)](https://x.ai/bot/guides/templates-for-grok-bot)
- [Forum: custom connectors (staff reply, August 30)](https://forum.cursor.com/t/grokbot-custom-connectors/169965)
- [Forum: does Grok Bot support local MCP? (staff reply, August 13)](https://forum.cursor.com/t/does-grok-bot-support-local-mcp-e-g-workflowy/168182)
- [Forum: custom remote MCP OAuth never starts (staff answer, August 12)](https://forum.cursor.com/t/grok-bot-custom-remote-mcp-oauth-never-starts-fetch-failed-same-url-works-in-cursor-ide/168188)
- [Forum: custom MCP OAuth fails with redirect_uri not allowed (staff replies, September 16 to 25)](https://forum.cursor.com/t/grok-bot-custom-mcp-oauth-fails-before-sign-in-redirect-uri-not-allowed/171877)
- [Forum: stdio MCP server paths on the Bot's computer (staff reply, September 8)](https://forum.cursor.com/t/grok-bot-stdio-mcp-keeps-spawn-path-into-deleted-agent-secrets/170901)
- [Forum: edit a custom stdio MCP server in place (staff reply, September 28)](https://forum.cursor.com/t/grok-bot-edit-a-custom-stdio-mcp-servers-command-args-env-in-place-without-losing-its-instructions/172953)
- [Forum: Zoom plugin OAuth error 4700 (staff replies)](https://forum.cursor.com/t/grok-bot-zoom-plugin-oauth-hardcodes-http-localhost-8787-callback-zoom-rejects-hostname-localhost-error-4700/169991)
- [Forum: Vercel plugin OAuth redirect URL invalid (staff reply, September 21)](https://forum.cursor.com/t/grok-bot-vercel-plugin-649-oauth-fails-with-app-configuration-error-redirect-url-is-invalid/168499)
- [Forum: delisted GitHub plugin, GitHub now built in (staff reply, September 28)](https://forum.cursor.com/t/grok-bot-delisted-github-plugin-48677658-cant-be-uninstalled-or-reconfigured-and-shows-connected-with-0-tools-after-a-401/172955)
- [Forum: MCP shows connected but the Bot gets MCP server not found (staff fix, September 28)](https://forum.cursor.com/t/grok-bot-inkbox-mcp-shows-connected-with-51-tools-but-agent-gets-mcp-server-not-found/173208)
- [Forum: remote MCP requests omit MCP-Protocol-Version on reused sessions (staff reply, October 8)](https://forum.cursor.com/t/grok-bot-remote-mcp-requests-omit-mcp-protocol-version-on-reused-sessions-causing-empty-http-400/174114)
- [Forum: outbound connections other than HTTPS blocked on the Bot's computer (staff reply, October 2)](https://forum.cursor.com/t/grok-bot-computer-all-outbound-non-https-traffic-blocked-since-oct-1-mysql-ssh-imap-smtp-ftp-time-out/173504)

---

# Grok Bot Shared Bots (formerly Team Bots): setup, Slack, admins, pricing

> How Grok Bot Shared Bots, formerly Team Bots, work: share one Bot with your team, add it to Slack, who pays for each chat, what stays private, what admins control.

- Canonical page: https://www.grokbotwiki.com/guides/grok-bot-team-bots
- Sources checked: 2026-10-30
- Evidence: docs.x.ai's Manage Grok Bot computers page (Restart VMs, inactive-computer termination) read October 30, 2026; changelog entry 0.78.1 (October 27) and Cursor's Shared Bots and secrets help read October 29, 2026; docs.x.ai's new Shared Bots page, its teams page, changelog entry 0.77.0 (October 26) and SpaceXSI's October 27 sales case study read October 28, 2026; changelog entry 0.75.8 read October 27; Cursor Shared Bots, Pages and secrets help and changelog entries 0.71.2, 0.75.2 and 0.75.5 checked October 25, 2026; seat prices checked against The X Subscription docs October 14; SpaceXSI announcement checked October 7 · steps from the docs; not a recorded run by us. Suggested workflows have not been independently tested.
- Publisher: Grok Bot Wiki, an independent guide not affiliated with SpaceXSI, xAI or X.

## The short answer

A Shared Bot (formerly Team Bot; the official docs renamed it by October 28, 2026) 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 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.

|  | Personal Bot | Public template | Shared Bot |
| --- | --- | --- | --- |
| Who talks to it | Only you | Each person who adds it talks to their own copy | Everyone on your team, each in their own chat |
| Who maintains it | You | Each copy's new owner, separately | The owner and any managers, and changes reach everyone |
| Memory | Yours | Starts from what the template shares, then separate per copy | Team memory, plus private notes with each person |
| Whose usage | Yours | The person who added the copy | The teammate in each chat; the owner for posts from Slack workflows |

Sources: https://docs.x.ai/grok-bot/shared-bots, https://x.ai/news/team-bots, https://x.ai/changelog/bot, https://x.ai/changelog/bot#v0.77.0

## 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; 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](https://www.grokbotwiki.com/guides/grok-bot-which-plan) covers seats and on-demand usage.

Sources: https://cursor.com/help/grok-bot/shared-bots, https://docs.x.ai/grok-bot/shared-bots, https://cursor.com/pricing, https://cursor.com/docs/account/teams/pricing, https://cursor.com/help/grok-bot/plans, https://docs.x.ai/x-subscription/pricing, https://docs.x.ai/x-subscription/team-plans

## 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. The steps below are the flow as the docs and Cursor's help described it through October 25.

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.

Sources: https://docs.x.ai/grok-bot/shared-bots, https://cursor.com/help/grok-bot/shared-bots, https://x.ai/news/team-bots

## 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.

| Plugin type | Whose access the Bot uses | Setup for teammates |
| --- | --- | --- |
| Signs in with an account (OAuth) | The person talking to the Bot | Each teammate connects their own account the first time |
| Configured with a key or token | The Bot's own credential, the same for everyone | None |
| Custom MCP server, Remote HTTPS | The Bot's own credential, or each person's sign-in if the server uses OAuth | None, or a one-time sign-in |
| Custom MCP server, Command | Runs on the computer each conversation uses | None; a command that needs secrets works only in the owner's chat |

Sources: https://docs.x.ai/grok-bot/shared-bots

## 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. 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 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](https://www.grokbotwiki.com/guides/grok-bot-shared-computer) explains what a computer holds.

| Conversation | Computer |
| --- | --- |
| The owner's own chat | The owner's computer |
| A teammate's chat in the app, or their 1:1 Slack DM | That teammate's own computer |
| Slack channels, group DMs and threads | One shared computer for that Bot, separate from everyone else's |

Sources: https://docs.x.ai/grok-bot/shared-bots, https://cursor.com/help/grok-bot/shared-bots

## 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. 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. 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. Slack is the only chat app for Shared Bots; 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.

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.

Sources: https://docs.x.ai/grok-bot/shared-bots, https://x.ai/changelog/bot, https://x.ai/changelog/bot#v0.71.2, https://x.ai/changelog/bot#v0.75.5, https://cursor.com/help/grok-bot/shared-bots, https://forum.cursor.com/t/feature-request-for-grokbot-google-chat-connector/173404

## 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, 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 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?](https://www.grokbotwiki.com/guides/is-grok-bot-safe) for the wider security model.

Sources: https://docs.x.ai/grok-bot/shared-bots, https://docs.x.ai/grok-bot/approvals-security-and-privacy, https://cursor.com/help/grok-bot/shared-bots, https://x.ai/changelog/bot, https://x.ai/changelog/bot#v0.75.5

## 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.

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.

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.

Sources: https://docs.x.ai/grok-bot/shared-bots, https://x.ai/changelog/bot, https://x.ai/changelog/bot#v0.75.5, https://docs.x.ai/grok-bot/teams-and-enterprises, https://cursor.com/help/grok-bot/shared-bots, https://forum.cursor.com/t/grok-bot-let-admins-restrict-members-from-creating-their-own-bots/174666/8, https://cursor.com/help/grok-bot/agent-email

## 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.

| Control | What the changelog says | Where it lives, and caveats |
| --- | --- | --- |
| Messaging between Bots (0.71.2) | Team admins can turn off Messaging between Bots | Under 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 team | Cursor'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](https://www.grokbotwiki.com/guides/grok-bot-pages) |
| 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 posted | Off 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 icon | Cosmetic |
| Collaborator routines (0.75.2) | Shared Bot owners and managers can let collaborators create routines from Configure | Each 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 API | The docs now describe this under Security & Compliance as Manage Member Computers and Data |
| 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 API | The 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, asks you to type DELETE, is recorded in the Audit Log and cannot be undone |
| 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 settings | Team 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 count | No 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 |

Sources: https://x.ai/changelog/bot#v0.71.2, https://x.ai/changelog/bot#v0.75.2, https://cursor.com/help/grok-bot/pages, https://docs.x.ai/grok-bot/computers

## 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 matches Cursor's help. 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.

Sources: https://x.ai/changelog/bot#v0.71.2, https://x.ai/changelog/bot#v0.75.2, https://x.ai/changelog/bot#v0.75.5, https://x.ai/changelog/bot#v0.77.0, https://x.ai/changelog/bot#v0.78.1, https://cursor.com/help/grok-bot/secrets, https://docs.x.ai/grok-bot/shared-bots, https://x.ai/news/grok-bot-sales, https://cursor.com/help/grok-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](https://www.grokbotwiki.com/guides/grok-bot-routines-not-running) covers what to check when one does not run.

Sources: https://docs.x.ai/grok-bot/shared-bots, https://x.ai/changelog/bot, https://x.ai/changelog/bot#v0.75.2, https://x.ai/changelog/bot#v0.75.5

## Quick answers

### How much do Grok Bot Shared Bots cost?

There is no separate Shared Bots price in any official page we checked. Shared Bots are in public beta on Cursor Teams and Enterprise plans; 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 a Shared 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; 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 SpaceXSI announced them as a public beta on Teams and Enterprise plans. 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. 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.

## Sources

- [Shared Bots (formerly Team Bots)](https://docs.x.ai/grok-bot/shared-bots)
- [The X Subscription docs: pricing and team seats](https://docs.x.ai/x-subscription/pricing)
- [The X Subscription docs: team plans and seats](https://docs.x.ai/x-subscription/team-plans)
- [Teams and enterprises](https://docs.x.ai/grok-bot/teams-and-enterprises)
- [Approvals, security and privacy](https://docs.x.ai/grok-bot/approvals-security-and-privacy)
- [Cursor help: Shared Bots (formerly Team Bots)](https://cursor.com/help/grok-bot/shared-bots)
- [Cursor help: plans and billing](https://cursor.com/help/grok-bot/plans)
- [Cursor team pricing](https://cursor.com/docs/account/teams/pricing)
- [Cursor pricing (now showing The X Subscription plans)](https://cursor.com/pricing)
- [SpaceXSI: Team Bots, shared AI teammates that learn as they work (September 28, 2026)](https://x.ai/news/team-bots)
- [Grok Bot changelog (Team Bots, now Shared Bots, from 0.61.0)](https://x.ai/changelog/bot)
- [Grok Bot changelog: 0.78.1 (Only you sharing, a Team Bot's own Vault, routines ask in Slack, October 27)](https://x.ai/changelog/bot#v0.78.1)
- [Grok Bot changelog: 0.77.0 (admin-only sharing, Bot-to-Bot messages in DMs, Slack edits, October 26)](https://x.ai/changelog/bot#v0.77.0)
- [SpaceXSI: Your next sales teammate should be a Grok Bot (October 27, 2026)](https://x.ai/news/grok-bot-sales)
- [Grok Bot changelog: 0.75.8 (share list access, Slack channel reads by routines, October 24)](https://x.ai/changelog/bot#v0.75.8)
- [Grok Bot changelog: 0.71.2 (Messaging between Bots switch, Manage Bot Computers, October 14)](https://x.ai/changelog/bot#v0.71.2)
- [Grok Bot changelog: 0.75.2 (Page sharing, link previews, collaborator routines, October 22)](https://x.ai/changelog/bot#v0.75.2)
- [Grok Bot changelog: 0.75.5 (Slack thread following, whose connector, October 23)](https://x.ai/changelog/bot#v0.75.5)
- [Cursor help: Pages (sharing)](https://cursor.com/help/grok-bot/pages)
- [Cursor help: store secrets securely (Vault and Shared Bot secrets)](https://cursor.com/help/grok-bot/secrets)
- [Manage computers (Manage Member Computers and Data)](https://docs.x.ai/grok-bot/computers)
- [Cursor help: give your Bot an email address](https://cursor.com/help/grok-bot/agent-email)
- [Forum: Google Chat connector request (staff reply, September 30)](https://forum.cursor.com/t/feature-request-for-grokbot-google-chat-connector/173404)
- [Forum: admins cannot stop members creating their own Bots (staff reply, October 10)](https://forum.cursor.com/t/grok-bot-let-admins-restrict-members-from-creating-their-own-bots/174666/8)

---

# Grok Bot with Gmail and Google Workspace: setup and fixes

> Connect Gmail, Calendar, Drive and Sheets to Grok Bot: what each plugin can and can't do, drafts and send-as, Workspace admin approval, known issues.

- Canonical page: https://www.grokbotwiki.com/guides/grok-bot-gmail-google-workspace
- Sources checked: 2026-10-29
- Evidence: Changelog entry 0.78.1 (October 27) read October 29, 2026; entry 0.77.0 (October 26) and the Bot email rename forum thread read October 28, 2026; entry 0.75.8 read October 27; Cursor help (connect apps, agent email, routines), official docs and changelog entries 0.71.2, 0.75.2 and 0.75.5 checked October 25, 2026 · other forum threads rechecked October 25 where noted, otherwise as of October 11 · Cursor staff forum replies attributed, not reproduced · no mailbox connected by us. Suggested workflows have not been independently tested.
- Publisher: Grok Bot Wiki, an independent guide not affiliated with SpaceXSI, xAI or X.

## The short answer

Grok Bot works with Gmail, Google Calendar, Drive and Sheets through plugins you add from Connect Apps and authorize in your browser. Gmail can search, read, draft, send and label mail in one connected mailbox. On a company Google account, an admin may first need to mark the app named Grok as trusted. Keep drafts on until you trust a Bot's email.

This page draws on Cursor's help pages, the official docs and the changelog through 0.75.5 (October 23), checked October 25, 2026, plus Cursor staff replies on the forum, which we attribute and have not reproduced. We have not connected a mailbox ourselves.

| Plugin | Can do (Cursor's help and changelog) | Cannot do, or known gaps |
| --- | --- | --- |
| Gmail | Search and read mail, draft and send, apply labels; send from a verified send-as address (0.68.0); attach files, reply all, add a note when forwarding and set label colors (0.75.2) | One mailbox at a time; staff said in August the connector exposes received attachments' names, not contents, and the changelog does not say that changed |
| Google Calendar | Read calendars you can see, create and update events, check free time, respond to invitations; create, update or delete several events in one step (0.75.2). Since 0.75.8, scheduling uses whichever calendar you have connected, Google Calendar or Outlook Calendar, and the Bot offers to connect one only when neither is | Cannot change Google Meet settings or add a Zoom link |
| Google Drive | Search and read files the account can open; Bots can upload files (0.53.0) | Cannot change sharing; staff described truncated uploads of larger files in August |
| Google Sheets | Read and edit cells in spreadsheets the account can edit | A file shared as Viewer stays view-only |

Sources: https://cursor.com/help/grok-bot/connect-apps, https://x.ai/changelog/bot, https://x.ai/changelog/bot#v0.75.2, https://forum.cursor.com/t/grok-bot-gmail-connector-can-list-attachments-but-cannot-download-their-bytes/169261, https://forum.cursor.com/t/google-drive-connector-pdf-upload-issue/169967

## Connect Gmail and the other Google plugins

Each Google service is its own plugin, and each uses the Google account you authorize; it can do only what that account can already do. Cursor's help says Grok Bot signs in to Google as Grok, not Cursor, which matters when you look for it in Google's security settings later. Our [plugins and MCP guide](https://www.grokbotwiki.com/guides/grok-bot-plugins-mcp) covers the general install flow.

1. Open Connect Apps in the sidebar, or follow the Connect card a Bot shows in chat.
2. Add Gmail. Since 0.63.0 the Google sign-in starts right away.
3. Choose the Google account in your browser and approve access within about 10 minutes. If the sign-in does not finish, choose Reconnect on the plugin, or Reopen on the in-chat card.
4. Confirm Gmail shows under Installed and is authorized; since 0.67.0 connected Google accounts show their email address rather than default.
5. Repeat for Google Calendar, Drive or Sheets only if a task needs them.
6. Give a first read-only task, such as the brief at the end of this page, before allowing anything to be sent.

Sources: https://cursor.com/help/grok-bot/connect-apps, https://cursor.com/help/grok-bot/how-to, https://x.ai/changelog/bot

## If your Google Workspace admin has to approve it

A company Google account can stop the connection before Gmail, Calendar, Drive, Docs, Sheets or Slides finishes signing in. If Google says your admin needs to review Grok, request access if the button is offered and wait for approval before choosing Authorize again. Access blocked means Google refused the sign-in, often because Grok is not on the allowlist or third-party apps are blocked. Cursor's help says changing browsers or linking again does not clear an admin block.

That Google approval is separate from a Cursor team admin's plugin controls: a plugin marked Disabled by team admin is turned back on in Cursor, not in Google.

1. In the Google Admin console, open Security, then Access and data control, then API controls.
2. Open App access control, then Manage third-party app access.
3. Add the app named Grok; if search does not find it, use the client ID from the blocked page or the admin review email.
4. Set Grok to Trusted for the people who use Grok Bot, then ask them to choose Authorize again.

Sources: https://cursor.com/help/grok-bot/connect-apps

## Drafts, sending and send-as

When a Bot writes an email, the docs say the chat can show an editable draft: review the recipients and body, then choose Send email or Discard. Recent releases filled in the details. Since 0.62.0 a Bot sends to the recipients it names rather than a saved draft's original ones. Since 0.68.0 drafts can go out from a verified Gmail send-as address, with a From picker, and Gmail draft cards include your signature. In 0.68.1 Bots can send formatted emails with headings, bold text and lists, and a Send cut off by Stop still goes out. The October 11 entry (0.69.0 to 0.70.2) fixes Gmail drafts to use your default send-as address and your own signature, and says Gmail, Slack and Outlook drafts retry through temporary rate limits and tell you if they still could not send.

October 22 (0.75.2) brought the biggest Gmail change since launch: the built-in Gmail connection can attach files to drafts and sends, reply all, add a note when forwarding and set label colors. Emails a Bot sends through Gmail show your name and the signature saved for that address, and reply drafts stay in their thread. The same entry says Bots can create, update or delete several Google Calendar events in one step without edited events shifting to a different time, and that large Google Slides edits update the live deck.

Sending itself changed on October 23 (0.75.5). Emails and Slack messages you ask a Bot to send now go out once Auto-review allows them, while sends on routine and other turns still wait as drafts, and Auto-review no longer waves through an action your request said to stop before, such as sending a message you asked only to draft. So the words matter: write draft a reply when you want a draft. Version 0.64.0 added Disable drafts for this Bot on draft cards, after which that Bot sends directly. Keep drafts on, and add an Ask first rule for sending email, until you have watched a Bot get several emails right; an Ask first rule always stops a matching action. See [permission boundaries](https://www.grokbotwiki.com/guides/permission-boundaries).

Sources: https://docs.x.ai/grok-bot/chat-and-collaboration, https://docs.x.ai/grok-bot/approvals-security-and-privacy, https://x.ai/changelog/bot, https://x.ai/changelog/bot#v0.75.2, https://x.ai/changelog/bot#v0.75.5

## Gmail or the Bot's own address

You may not need to hand a Bot your mailbox at all. Cursor's help describes agent email, which the changelog announced on October 11: you claim one address at mail.grokbot.com, and all your Bots can use it to receive, search and send mail, collect receipts or newsletters, pick up sign-up codes with your OK, and run a routine when mail arrives. There is no inbox view; you ask a Bot what arrived. The address is permanent, one per account, and cannot be renamed or deleted, so choose the name with care. On a Cursor team an admin turns on Agent Email first.

Choosing with care is the whole lesson of a forum thread opened on October 10 that had passed 300 views by October 28 with no Cursor staff reply. Several users wrote that they claimed an address in a hurry, believing each Bot would get its own, and now have a name too specific, too personal or branded for the wrong business; two of them said support confirmed the address cannot be renamed, released, deleted or reassigned, and the thread asks for a one-time rename or a retire-and-reclaim path. Users also tested plus-addressing on October 11: mail to name+test@mail.grokbot.com did not arrive. Three days later the 0.71.2 changelog (October 14) added tagged addresses, so a Bot can send from name+shop@ and a routine on that tag runs only for its mail; the thread has not retested it, and tagged mail still shows the base name. Until Cursor offers a rename, the official position is the help page's: one permanent address per account. If the name matters, claim it only after you have decided what every Bot on the account will use it for.

Use Gmail when the work is in your existing mail, such as triaging your inbox or replying as you. Use the Bot's own address when it needs an inbox of its own, so a sign-up or newsletter never touches your personal account. If both are connected, Cursor's help says the Bot asks which account to send from when either could work. Sending follows the 0.75.5 rule: when you ask in chat, the email goes out once Auto-review allows it, with an approval card first if Auto-review needs you; email from a routine, or any turn you did not start with that request, waits as a draft until you press Send, and there is no option for unattended sending. The docs.x.ai teams page still said every outbound email waits as a draft when we checked on October 25, so the two sources disagree for now. Either way, the Bot treats instructions inside received email as information, not permission.

October added several features to the Bot's own address. Since 0.71.2 (October 14) a Bot can send from a tagged form of its address, like name+shop@, and a routine on that tag runs only for its mail, so each sign-up or vendor can get its own tag and routine. Since 0.75.2 (October 22) routines can read the Bot's inboxes, and the first email a Bot sends to someone new includes a one-click unsubscribe link. Since 0.75.5 (October 23) a Bot can forward an email from its own inbox with the original formatting, images and attachments; Cursor's help says forwarding needs Grok Bot 0.75.2 or later. Since 0.77.0 (October 26), every email a Bot sends from its own address to one other person includes a one-click unsubscribe, not only the first, and Bots no longer send to addresses that have permanently bounced.

Cursor's help lists the sending limits: up to 50 recipients per email across To, Cc and Bcc, up to 10 attachments of 10 MB each and 25 MB in total, and no executable files. Newsletters and first-contact emails go to one recipient per message, and a bounce, unsubscribe or spam report stops the Bot emailing that address. Incoming mail can carry up to 10 attachments, 10 MB each and 25 MB in total, and anything beyond that is skipped.

Sources: https://cursor.com/help/grok-bot/agent-email, https://docs.x.ai/grok-bot/teams-and-enterprises, https://x.ai/changelog/bot#v0.71.2, https://x.ai/changelog/bot#v0.75.2, https://x.ai/changelog/bot#v0.75.5, https://x.ai/changelog/bot#v0.77.0, https://forum.cursor.com/t/grok-bot-allow-renaming-or-swapping-a-claimed-bot-email-address/174277

## Known Gmail and Google issues

These come from Cursor staff replies and the changelog. Status is what the source said when we checked; some may be fixed in a version newer than the thread.

| Symptom | What Cursor said | Status |
| --- | --- | --- |
| Gmail silently signs out, for example after Google revokes access, and Bots fail until you notice | 0.77.0 (October 26): your primary Bot tells you in its chat and offers to reconnect; when Google is only throttling requests, Google apps stay connected and the Bot says to try again later | Fixed (October 26) |
| A Gmail reply does not fold into the thread for the recipient, or failed Gmail reads and sends are not retried | 0.77.0: replies quote the original so Gmail folds the thread, signature logos stay inline, and failed reads and sends retry | Fixed (October 26) |
| An Ask first or Block rule on Gmail searches or reads is bypassed when the Bot calls the tool by another name | 0.77.0: the rules hold whatever the Bot calls them | Fixed (October 26) |
| You cannot drop an email draft without sending it | 0.77.0: email draft cards have a Discard button again | Fixed (October 26) |
| A plain-text draft the Bot writes in Gmail reads badly on a phone or sends with hard line breaks, or a draft cannot attach a file from the Bot's computer | 0.78.1 (October 27): plain-text drafts open in rich text; drafts and sends can attach a file from the Bot's computer in more cases | Fixed (October 27) |
| An email from a Bot's own address fails when the mail server connection times out | 0.78.1: Bot emails retry once | Fixed (October 27) |
| Copying a reply loses headings, lists and links when you paste it into Gmail, Docs, Slack or Notion | 0.78.1: Copy keeps them, and copied selections paste as markdown | Fixed (October 27) |
| Links in sent email become google.com/url redirects | Links sent through the connector are saved with Google's redirect wrapper. On October 16 staff said it happens on every platform, that a change to keep links exactly as typed is in the works but not yet available, and that the workaround is to let the Bot write the draft and add or re-paste the links in Gmail before sending | Open; fix in progress (October 16) |
| Recipients see a broken "--null" MIME boundary | A strict recipient's mail relay re-packs Grok Bot's single-part plain-text email; staff suggested to the team that sending a proper multipart message would avoid it | Open (October 4) |
| The Bot can see an attachment's name but not its contents | The Gmail connector exposed names and metadata only; workarounds are the browser or routing the file through Drive. Since 0.75.2 it can attach files to drafts and sends, but the changelog does not say it can now read received attachments | Known gap for reading (August 24); sending attachments added October 22 |
| Gmail refuses to return a full thread | 0.71.2 (October 14): when that happens the Bot now falls back to the thread's first message, so check whether a summary covers the whole thread | Changed (October 14) |
| A Gmail reply draft lands outside its thread, or sent mail lacks your name or signature | 0.75.2 (October 22): emails sent through Gmail show your name and the signature saved for that address, and reply drafts stay in their thread | Fixed (October 22) |
| Searching the Spam folder returns nothing | Staff said in September that Spam search via the connector was not available; the 0.68.1 notes say Bots can now search Spam and move a message back to the inbox | Changed in 0.68.1 (October 7) |
| Send or reply reports a missing tool, or hits Google rate limits | 0.68.1 says send and reply no longer report a missing tool, and Bots wait out Google's rate limits; the October 11 entry adds that drafts retry through temporary rate limits and say if they still could not send | Fixed in 0.68.1 (October 7); retries added October 11 |
| A Gmail draft goes out from the wrong address or without your signature | The October 11 changelog entry (0.69.0 to 0.70.2) says Gmail drafts now use your default send-as address and your own signature | Fixed (October 11) |
| The Bot cannot fill a Google password from 1Password | Tracked, on Google's pop-up and full-page sign-in alike; take over the screen, type the password from 1Password, finish 2-step verification and hand control back. The session usually persists | Open; no ETA (October 10) |
| A script using IMAP or SMTP (for example imap.gmail.com) times out on the Bot's computer | Since about October 1 some Bot computers allow only HTTPS on port 443 out; staff said it is tracked, not to Reset or Update for it, and that the Gmail connector, which uses HTTPS, still works | Open (October 8); users still reporting it October 22 |
| Google says This app is blocked on a personal account | Staff flagged it; the reporter said an app update fixed it the next day | Solved (August 29) |

Sources: https://x.ai/changelog/bot#v0.78.1, https://forum.cursor.com/t/grok-bot-gmail-connector-user-gmail-rewrites-every-link-into-google-com-url-redirects-on-create-draft-and-send-message/173321, https://forum.cursor.com/t/grok-bot-gmail-send-emails-arrive-with-broken-null-mime-boundary/173684, https://forum.cursor.com/t/grok-bot-gmail-connector-can-list-attachments-but-cannot-download-their-bytes/169261, https://forum.cursor.com/t/grok-bot-gmail-search-threads-returns-empty-for-spam-while-list-labels-shows-threads/170832, https://x.ai/changelog/bot, https://forum.cursor.com/t/grok-bot-wont-login-to-google-account-using-1password/173423, https://forum.cursor.com/t/grok-bot-unable-to-authenticate-via-gmail-plugin/169782, https://forum.cursor.com/t/grok-bot-email-still-down-after-37-hours-ticket-t-g79658/174136, https://forum.cursor.com/t/grok-bot-computer-all-outbound-non-https-traffic-blocked-since-oct-1-mysql-ssh-imap-smtp-ftp-time-out/173504, https://x.ai/changelog/bot#v0.71.2, https://x.ai/changelog/bot#v0.75.2, https://x.ai/changelog/bot#v0.77.0

## Google Workspace on a team

On a Shared Bot (formerly Team Bot), a plugin that signs in with an account uses the account of whoever is talking to the Bot, so each teammate connects their own Google account and the Bot never lends one person's mailbox to another. In a shared conversation such as a Slack thread, it asks before using your connector. There is no Google Chat connector yet; a Cursor staff member said on September 30 that the team is looking at one, and teams were still asking for it on October 11. Agent email cannot be used in Slack threads or in chats where someone else is talking to a Bot, and a Shared Bot has no shared team address. See [our Shared Bots guide](https://www.grokbotwiki.com/guides/grok-bot-team-bots).

Sources: https://docs.x.ai/grok-bot/shared-bots, https://forum.cursor.com/t/feature-request-for-grokbot-google-chat-connector/173404, https://cursor.com/help/grok-bot/agent-email

## A safe first Gmail task

Start read-only and small: one label or one day of mail, with drafts and no changes. The same pattern underpins the [morning brief recipe](https://www.grokbotwiki.com/workflows/morning-brief), which adds the calendar. This brief is our template, not a tested routine.

Editorial template (replace placeholders and review access before running):

```text
Using the connected Gmail, read only messages in [label or inbox] received since [date and time, time zone]. Return a digest grouped into Needs me, Can wait and Noise, with sender, subject, a one-line reason and a link for each. Draft replies only for messages in Needs me and leave them as drafts. Do not send, archive, label, delete or unsubscribe from anything. If you cannot read the mailbox, say so and stop.
```

## Quick answers

### Can Grok Bot send email from my Gmail account?

Yes, once the Gmail plugin is connected. Cursor's help says Gmail can search and read mail, draft and send, and apply labels on the connected mailbox. By default a Bot shows an editable draft card that you send or discard yourself. Since 0.68.0 (October 5) drafts can go out from a verified Gmail send-as address, with a From picker when you have more than one. Since 0.75.2 (October 22) the built-in Gmail connection can attach files to drafts and sends, reply all, add a note when forwarding and set label colors, and emails show your name and the signature saved for that address. Since 0.75.5 (October 23), an email you ask a Bot to send goes out once Auto-review allows it; one from a routine still waits as a draft.

### Can Grok Bot have its own email address instead of using my Gmail?

Yes. Cursor's help says you can claim one address at mail.grokbot.com, by asking a Bot or from the Email plugin in Connect Apps, and all your Bots can receive, search and send mail from it. You get one address per account and cannot rename or delete it. Cursor's help, checked October 25, says an email you ask for in chat goes out once Auto-review allows it, while email from a routine or any turn you did not start with that request waits as a draft until you press Send. Since 0.75.5 a Bot can also forward mail from that inbox with its attachments. On a Cursor team, an admin has to turn on Agent Email first.

### Can I connect my work and personal Gmail at the same time?

No. Cursor's help says Gmail connects one mailbox at a time: to use another, disconnect the current one and authorize the other. Every Bot on your account can use the connected mailbox, so disconnect it if a Bot should not.

### Why does Google say an admin needs to review Grok?

Your company's Google Workspace has not approved the app yet. Cursor's help says Grok Bot signs in to Google as Grok, not Cursor, and an IT admin approves it in the Google Admin console under Security → Access and data control → API controls → Manage third-party app access, setting Grok to Trusted. A personal Gmail account does not need an admin.

### Can Grok Bot add a Zoom link or change Google Meet settings?

No. Cursor's help says the Google Calendar plugin can read calendars you can see, create and update events, check free time and respond to invitations, but cannot change Google Meet settings or add a Zoom link, because Google's Zoom add-on is not available to the plugin. Add the Zoom link to the event yourself.

## Sources

- [Cursor help: connect apps (Gmail, Calendar, Drive, Sheets, Google admin approval)](https://cursor.com/help/grok-bot/connect-apps)
- [Grok Bot changelog: 0.78.1 (rich-text drafts, attachments, email retries, October 27)](https://x.ai/changelog/bot#v0.78.1)
- [Grok Bot changelog: 0.77.0 (Gmail sign-out notice, second-account picker, folded replies, Discard button, October 26)](https://x.ai/changelog/bot#v0.77.0)
- [Forum: allow renaming or swapping a claimed Bot email address (330 views; support confirmed no rename)](https://forum.cursor.com/t/grok-bot-allow-renaming-or-swapping-a-claimed-bot-email-address/174277)
- [Cursor help: how-tos (reconnect a plugin)](https://cursor.com/help/grok-bot/how-to)
- [Computer and apps: connect an app](https://docs.x.ai/grok-bot/computer-and-apps)
- [Message and collaborate: drafts](https://docs.x.ai/grok-bot/chat-and-collaboration)
- [Approvals: Ask first rules](https://docs.x.ai/grok-bot/approvals-security-and-privacy)
- [Shared Bots (formerly Team Bots): whose access a plugin uses](https://docs.x.ai/grok-bot/shared-bots)
- [Grok Bot changelog (Gmail changes in 0.53 to 0.70.2)](https://x.ai/changelog/bot)
- [Grok Bot changelog: 0.71.2 (tagged Bot email addresses, October 14)](https://x.ai/changelog/bot#v0.71.2)
- [Grok Bot changelog: 0.75.2 (Gmail attachments, reply all, Calendar batch edits, routines read inboxes, October 22)](https://x.ai/changelog/bot#v0.75.2)
- [Grok Bot changelog: 0.75.8 (scheduling uses the connected calendar, October 24)](https://x.ai/changelog/bot#v0.75.8)
- [Grok Bot changelog: 0.75.5 (email forwarding, sends after Auto-review, October 23)](https://x.ai/changelog/bot#v0.75.5)
- [Teams and enterprises: Agent Email](https://docs.x.ai/grok-bot/teams-and-enterprises)
- [Forum: outbound non-HTTPS traffic blocked on the Bot's computer (users reporting through October 22)](https://forum.cursor.com/t/grok-bot-computer-all-outbound-non-https-traffic-blocked-since-oct-1-mysql-ssh-imap-smtp-ftp-time-out/173504)
- [Forum: Gmail connector rewrites links into google.com/url redirects (staff reply, September 29)](https://forum.cursor.com/t/grok-bot-gmail-connector-user-gmail-rewrites-every-link-into-google-com-url-redirects-on-create-draft-and-send-message/173321)
- [Forum: emails arrive with a broken MIME boundary (staff replies, October 3 and 4)](https://forum.cursor.com/t/grok-bot-gmail-send-emails-arrive-with-broken-null-mime-boundary/173684)
- [Forum: Gmail connector cannot download attachment contents (staff reply, August 24)](https://forum.cursor.com/t/grok-bot-gmail-connector-can-list-attachments-but-cannot-download-their-bytes/169261)
- [Forum: Drive connector PDF upload issue (staff reply, August 30)](https://forum.cursor.com/t/google-drive-connector-pdf-upload-issue/169967)
- [Forum: Gmail search returns nothing for Spam (staff replies, September 7 to 28)](https://forum.cursor.com/t/grok-bot-gmail-search-threads-returns-empty-for-spam-while-list-labels-shows-threads/170832)
- [Forum: Grok Bot will not log in to Google with 1Password (staff replies, September 30 and October 10)](https://forum.cursor.com/t/grok-bot-wont-login-to-google-account-using-1password/173423)
- [Forum: unable to authenticate the Gmail plugin (August 28, solved)](https://forum.cursor.com/t/grok-bot-unable-to-authenticate-via-gmail-plugin/169782)
- [Forum: Google Chat connector request (staff reply, September 30)](https://forum.cursor.com/t/feature-request-for-grokbot-google-chat-connector/173404)
- [Forum: IMAP and SMTP time out on the Bot's computer (staff reply, October 8)](https://forum.cursor.com/t/grok-bot-email-still-down-after-37-hours-ticket-t-g79658/174136)
- [Cursor help: give your Bot an email address](https://cursor.com/help/grok-bot/agent-email)

---

# Grok Bot with Obsidian: three ways to use your vault

> Grok Bot has no Obsidian plugin. Three workable routes to your vault (local access, a repository or a synced copy), their trade-offs, and community Bots.

- Canonical page: https://www.grokbotwiki.com/guides/grok-bot-obsidian
- Sources checked: 2026-10-25
- Evidence: Grok Bot docs, changelog entries 0.71.2 and 0.75.2, and the Mac local-access and outbound-traffic forum threads checked October 25, 2026; other forum replies as of October 11; Obsidian help checked October 7 · editorial setup options, not a recorded run by us. Suggested workflows have not been independently tested.
- Publisher: Grok Bot Wiki, an independent guide not affiliated with SpaceXSI, xAI or X.

## The short answer

Grok Bot has no Obsidian plugin, but an Obsidian vault is just a folder of Markdown files, so a Bot can work with it three ways: read it on your own computer with local access, clone it from a private Git repository, or work on a copy in its cloud workspace. Start read-only, and give the Bot one folder to write in.

Obsidian's help says it stores notes as Markdown files in a vault, a folder on your local file system. Grok Bot's Bots work on a cloud computer, so the question is only how your notes reach that computer. The routes below are our editorial options built on documented features; we have not recorded a run of them.

| Route | How notes reach the Bot | Best for | Watch out for |
| --- | --- | --- | --- |
| Local access | The desktop app lets a Bot read files on your Mac or Windows computer, with approval per command by default | Occasional reading of a vault that never leaves your laptop | Opens your own computer to Bots; on a Mac it currently drops when the screen locks or the app sits in the background |
| Git repository | The Bot clones a private repo of your vault over HTTPS and pushes to a branch | Vaults already backed up with Git; scheduled routines | Merge conflicts with your own edits; anything committed is on the Bot's computer |
| A copy in /workspace | You attach notes or a zip, or the Bot pulls them from Google Drive | One-off projects or a single folder of notes | The copy drifts from your real vault |

Sources: https://obsidian.md/help/data-storage, https://docs.x.ai/grok-bot/security, https://docs.x.ai/grok-bot/computer-and-apps

## Route 1: let a Bot read the vault on your computer

Grok Bot's security page says Bots can act on your own machine through the desktop app: run commands, read files, and move files between the cloud computer and your machine. It is controlled by Execution on Local Computer in Settings → General → Bot, or per computer under Settings → Computer → Computers, with Ask every time as the default; the docs describe it for Mac and Windows. Ask every time shows an approval card with the exact command, which suits a Bot that reads a few notes when you ask.

The docs recommend Never allow unless a Bot has a specific reason to work on local files, and the first prompt applies to every Bot on your account. Reading your vault is a specific reason, so keep Ask every time rather than Always allow, and point the Bot at the vault folder by path. Local access only works while your computer is on and the app is running, so it does not suit overnight routines.

On a Mac it is narrower than that for now. Cursor staff said on October 5, 8 and 9 that when the screen is locked, or the Grok Bot window has been in the background for about 10 minutes, the app treats the Mac as away and can stop its local helper, which does not restart when a Bot needs it. Bringing the Grok Bot window to the front reconnects it within about a minute. Staff call it a known issue with no setting to turn it off yet, and on October 13 a staff member said they could not confirm that any release, including 0.70.2, fully fixes it. Plan on reading the vault while you are at the Mac.

Version 0.71.2 (October 14) changed some of the surrounding behaviour: when your computer sleeps, Bots treat it as disconnected within two minutes and say so; after a Wi-Fi, VPN or other network change they can run tasks on your computer right away; commands keep going through brief connection stalls; and work meant for one of your computers that is offline is no longer run on another computer without asking. The notes do not say the background-window issue above is fixed.

Editorial template (replace placeholders and review access before running):

```text
On my local computer, read only the notes in [vault path]/[folder]. Do not open anything outside that folder. Summarize [topic] across those notes with a list of the note titles you used. Do not create, edit, move or delete any file on my computer. Ask before every command.
```

Sources: https://docs.x.ai/grok-bot/security, https://docs.x.ai/grok-bot/approvals-security-and-privacy, https://forum.cursor.com/t/grok-bot-0-68-1-macos-mac-shows-disconnected-while-awake-and-in-use-local-computer-doesnt-reconnect-until-app-is-focused/174223, https://x.ai/changelog/bot#v0.71.2

## Route 2: keep the vault in a private Git repository

Obsidian's help lists Git among its sync options. If your vault already lives in a private repository, a Bot can clone it onto its cloud computer and read it there, which also works for routines while your laptop is closed. GitHub is built into Grok Bot through your connected Cursor GitHub account, a Cursor staff member said on September 28, and since 0.75.2 (October 22) the GitHub connector can list your repositories, compare commits and read branch and issue comments, which helps a Bot see what changed in the vault since its last run. Since October 1 some Grok Bot computers can only make outbound HTTPS connections on port 443; Cursor staff said on October 2 that this is not intended and is tracked, that cloning over HTTPS still works, and users were still reporting it on October 22. Clone over HTTPS rather than SSH.

Have the Bot write to its own branch or an inbox folder and merge its changes yourself. Two writers on the same files, you in Obsidian and a Bot on its computer, is the conflict Obsidian's help warns about when it says not to sync one vault through several services at once.

Sources: https://obsidian.md/help/sync-notes, https://forum.cursor.com/t/grok-bot-delisted-github-plugin-48677658-cant-be-uninstalled-or-reconfigured-and-shows-connected-with-0-tools-after-a-401/172955, https://forum.cursor.com/t/grok-bot-computer-all-outbound-non-https-traffic-blocked-since-oct-1-mysql-ssh-imap-smtp-ftp-time-out/173504, https://x.ai/changelog/bot#v0.75.2

## Route 3: work on a copy in the Bot's workspace

For a one-off job, give the Bot a copy. Since 0.71.2 (October 14) one message can carry up to 20 attachments with a 200 MB total, and files can be up to 250 MB, though the docs' files page still listed six attachments and 25 MB documents when we checked on October 25; a zipped vault is the simplest way to stay under either limit. The computer has a shared workspace at /workspace where Bots keep durable project files. If your vault syncs to Google Drive, which Obsidian's help lists as a third-party option, the Google Drive plugin can search and read files the connected account can open.

A copy drifts from your real vault, so treat what the Bot writes as a draft to paste back by hand. Remember that every Bot on your account can read /workspace; remove private notes when the job is done. Our [shared-computer guide](https://www.grokbotwiki.com/guides/grok-bot-shared-computer) explains what persists there.

Sources: https://docs.x.ai/grok-bot/files-and-results, https://docs.x.ai/grok-bot/computer-and-apps, https://cursor.com/help/grok-bot/connect-apps, https://obsidian.md/help/sync-notes, https://x.ai/changelog/bot#v0.71.2

## What does not work

An Obsidian MCP server running on your laptop will not attach: a Cursor staff member said on August 13 that Grok Bot does not attach MCP servers that run on your own machine, over stdio or localhost. Exposing one to the internet to satisfy the public-HTTPS requirement would expose your notes too; we do not recommend it. See [our plugins and MCP guide](https://www.grokbotwiki.com/guides/grok-bot-plugins-mcp) for how custom servers work.

- [ ] The Bot can read only the folder or repository it needs.
- [ ] It writes to one inbox folder or branch, and you merge its changes.
- [ ] Execution on Local Computer is Ask every time, not Always allow.
- [ ] Private notes are not left in /workspace after the job.
- [ ] The vault is synced through one service, not several.

Sources: https://forum.cursor.com/t/does-grok-bot-support-local-mcp-e-g-workflowy/168182

## Quick answers

### Is there an Obsidian plugin for Grok Bot?

Not an official one. Obsidian does not appear in Grok Bot's documentation or in Cursor's plugin help, and we found no Obsidian thread on the Cursor forum's grok-bot tag when we checked on October 11, 2026. Several community Bots in our directory are built around Obsidian vaults; they still need one of the routes on this page to reach your notes.

### Can Grok Bot use an Obsidian MCP server on my computer?

No. A Cursor staff member said on August 13 that Grok Bot does not attach MCP servers that run on your own machine, whether over stdio or on localhost, because Bots work on a cloud computer. An MCP server would have to be reachable over public HTTPS, which means exposing your notes to the internet.

### Will Grok Bot edits conflict with my Obsidian sync?

They can. Obsidian's help warns against syncing the same vault through more than one service at once. If a Bot writes to your vault, give it one inbox folder or one Git branch, and merge its changes yourself rather than letting two sync paths edit the same files.

## Sources

- [Computer and apps: files and /workspace](https://docs.x.ai/grok-bot/computer-and-apps)
- [Files and results: attachments](https://docs.x.ai/grok-bot/files-and-results)
- [Approvals: local computer access](https://docs.x.ai/grok-bot/approvals-security-and-privacy)
- [Grok Bot security: local execution](https://docs.x.ai/grok-bot/security)
- [Obsidian help: how Obsidian stores data](https://obsidian.md/help/data-storage)
- [Obsidian help: sync your notes across devices](https://obsidian.md/help/sync-notes)
- [Cursor help: connect plugins (Google Drive)](https://cursor.com/help/grok-bot/connect-apps)
- [Forum: does Grok Bot support local MCP? (staff reply, August 13)](https://forum.cursor.com/t/does-grok-bot-support-local-mcp-e-g-workflowy/168182)
- [Forum: GitHub is built into Grok Bot (staff reply, September 28)](https://forum.cursor.com/t/grok-bot-delisted-github-plugin-48677658-cant-be-uninstalled-or-reconfigured-and-shows-connected-with-0-tools-after-a-401/172955)
- [Forum: Mac local access drops when the app is in the background (staff reply, October 9)](https://forum.cursor.com/t/grok-bot-0-68-1-macos-mac-shows-disconnected-while-awake-and-in-use-local-computer-doesnt-reconnect-until-app-is-focused/174223)
- [Forum: outbound non-HTTPS traffic blocked since October 1 (staff reply, October 2)](https://forum.cursor.com/t/grok-bot-computer-all-outbound-non-https-traffic-blocked-since-oct-1-mysql-ssh-imap-smtp-ftp-time-out/173504)
- [Grok Bot changelog: 0.71.2 (attachments, local computer connection fixes, October 14)](https://x.ai/changelog/bot#v0.71.2)
- [Grok Bot changelog: 0.75.2 (GitHub connector, Pages, October 22)](https://x.ai/changelog/bot#v0.75.2)

---

# Grok Bot Pages: reports and dashboards your Bot keeps up to date

> What Grok Bot Pages are, how to make, change, pin and share one, what public links and team sharing expose, and the limits the docs leave open.

- Canonical page: https://www.grokbotwiki.com/guides/grok-bot-pages
- Sources checked: 2026-10-29
- Evidence: Grok Bot changelog entries 0.77.0 (October 26) and 0.78.1 (October 27) read October 28 and 29, 2026 · Cursor's Pages help, the docs.x.ai files and results page and the Grok Bot changelog (0.75.2, October 22) read October 25, 2026 · use cases beyond the official examples and the prompt are editorial · no Page built or shared by us. Suggested workflows have not been independently tested.
- Publisher: Grok Bot Wiki, an independent guide not affiliated with SpaceXSI, xAI or X.

## The short answer

A Page is a styled report, memo, dashboard or tracker that a Bot builds for you in the chat. You open it full screen, ask the Bot for changes in a panel beside it, and share it with people you invite, your team or anyone with the link. The Bot can keep it current, including from a routine. Pages appear in the 0.75.2 changelog entry of October 22, 2026.

This page follows Cursor's Pages help, the docs.x.ai files and results page and the changelog, read on October 25, 2026. We have not built or shared a Page ourselves, and the use cases beyond the official examples are our suggestions.

| Question | Answer from the sources |
| --- | --- |
| What can it hold? | Text, tables, charts and controls like filters and switches (Cursor's help); the docs add heat maps, flow charts and other interactive components |
| Who edits it? | The Bot, when you ask in the chat panel beside the open Page; you can rename a Page you made from its title |
| Where does it live? | In the Bot's Library, under the Bot's details; also through Cmd+K search or the right-hand panel |
| Who can see it? | Only you until you share it; then people you invite, your team, or anyone with the link |
| Can it update itself? | A Bot can update or create Pages on routines, according to the docs |
| What version do I need? | Cursor's help says 0.60.0 or later on your computer and 1.14.0 or later on your phone, and that Pages is rolling out gradually; the changelog lists Pages as new in its October 22 entry |

Sources: https://cursor.com/help/grok-bot/pages, https://docs.x.ai/grok-bot/files-and-results, https://x.ai/changelog/bot#v0.75.2

## Make a Page and change it

Ask the Bot in chat and say what the Page is for and what should be on it. Cursor's help gives the example of asking for a Page that compares three quotes in a thread, with a table and a short recommendation; the docs suggest a summary of this week's support tickets by topic, a dashboard of signups, trials and conversions for the last 30 days, and a launch tracker of open tasks, owners and statuses. The Bot posts the Page in the chat as a card with its title and Open.

On desktop, clicking the card fills the window with the Page and keeps the chat open in a smaller panel beside it, labeled Message about and the Page's title; on the phone, tapping the card opens it in the app. Changes go through the Bot: it edits the same Page, so everyone who can open it sees the change, and the earlier card in the chat shows Updated. Filters, switches and other controls change only your view and are never saved. Since 0.75.2, Pages can capture the pointer and fill the screen, keyboard shortcuts keep working while a Page is open, and Back closes the Page and stays on its Bot.

1. Ask the Bot for a Page, naming its purpose, the sources it should use and the sections you want.
2. Open the card and read the whole Page before sharing it; check numbers against the sources the Bot cites.
3. Ask for corrections in the panel beside the Page rather than in a new chat, so the same Page is updated.
4. Rename it from its title if the Bot's title is unclear; the title becomes part of a public link's address.
5. Share it only after the content is right, at the narrowest level that works.

Sources: https://cursor.com/help/grok-bot/pages, https://docs.x.ai/grok-bot/files-and-results, https://x.ai/changelog/bot#v0.75.2

## Find and pin Pages in the Library

Each Bot keeps its Pages in its Library. On desktop, click the Bot's name at the top of the chat to open its details and choose the Library tab, which lists the Pages, files and apps the Bot has made; a Page shared with your team or with anyone who has the link shows that on its row. The docs also point to Cmd+K search and the right-hand panel for getting back to past Pages.

The More actions menu on a Page's row offers Open, Share… and Pin. Since 0.75.2 you can pin Library pages, files and links to a Pinned section that stays at the top of the Library and syncs across your devices; choose Unpin to take one off. Hovering over or focusing a Library row shows a preview with who sent the item, when, and who can see a Page, which is the quickest way to check a Page's visibility before you send its link.

Sources: https://cursor.com/help/grok-bot/pages, https://docs.x.ai/grok-bot/files-and-results, https://x.ai/changelog/bot#v0.75.2

## Share a Page, and what each option exposes

A new Page is private to you until you share it. Open the Page and click Share at the top, or choose Share… from its row in the Library, pick who can view it, then choose Copy link. People who open a team or invite link sign in with their Cursor account first. Since 0.75.2 the Share menu shows the Page's current visibility. Everyone you share with can read the Page and use its controls; only the Bot can change it.

Public links deserve the most care. Cursor's help says an anyone-with-the-link Page gets its own web address on pages.grok.bot, made from its title, that anyone can open without signing in. The address stays the same if you rename the Page, and you cannot choose a custom one yet. Treat a public Page like a published document: a Page the Bot keeps up to date will show whatever the Bot adds later, too.

| Who can view | Who can open it | Notes from Cursor's help |
| --- | --- | --- |
| People you invite | You and the teammates and groups you add, each as a Viewer | On a personal account this option is Only you |
| Your team | Everyone on your Cursor team | A Page in your personal space cannot be team-shared |
| Your organization | Everyone in the organization | Some teams see this option; the changelog adds sharing with another team in the organization (0.75.2) |
| Anyone with the link | Anyone, with no sign-in | Off on Enterprise teams; address on pages.grok.bot |

Sources: https://cursor.com/help/grok-bot/pages, https://x.ai/changelog/bot#v0.75.2

## Unshare, delete and admin limits

To narrow a Page's audience, open Share again and choose a narrower option. Cursor's help says every Page you've shared is listed under Grok Bot Pages in Shared Canvases on your Cursor dashboard, where you can change who can view it or delete it; the 0.75.2 changelog describes the same place as the dashboard's Pages section, where you can unshare or delete. Deleting a Page means anyone with the link loses access.

On teams, the 0.75.2 entry says Page owners can share a Page with their whole organization or with another team in it, and team admins can limit who can share Pages with everyone on the team. When an option is unavailable, the share menu says why: Public sharing is off for Enterprise teams, Pages in your personal space can't be team-shared, Couldn't update access (try again), or This page's access changed, which means someone else changed it while you had the menu open.

Since 0.77.0 (October 26) a Page's owner can also delete it from the Library, which the changelog says removes it for everyone it was shared with, so the dashboard is no longer the only place a delete can happen. The same entry says teammates see Pages shared with the team in a shared Bot's Library under Shared with your team, that pictures on a Page fade in and broken ones show their description, that links to Grok Bot inside a Page open in the app, and that after you are removed from a team your personal Pages show in the Library again. 0.78.1 (October 27) adds that Bots apply several Page edits at once and leave the Page unchanged if any edit does not fit, that diagrams on a Page wrap long labels instead of clipping them, that Share in a Page header matches the Share button on Shared Bots (formerly Team Bots), that a team Page appears in the Library under every Bot that published it, and that clicking the current Bot in the sidebar closes an open Page.

Sources: https://x.ai/changelog/bot#v0.78.1, https://cursor.com/help/grok-bot/pages, https://x.ai/changelog/bot#v0.75.2, https://x.ai/changelog/bot#v0.77.0

## Pages that stay up to date

The docs say you can ask Bots to update or create Pages on routines, and that you can open a Page and chat with the Bot to configure changes. That makes a Page a natural home for anything you would otherwise receive as a new file every week. The ideas below are ours, not tested setups; each pairs a Page with a routine, and each run spends usage, as our [skills vs routines guide](https://www.grokbotwiki.com/guides/skills-vs-routines) explains.

- [ ] A weekly status memo for a project, rebuilt each Monday from the tracker and pull requests the Bot can read.
- [ ] A support or sales dashboard refreshed each morning from a connected app, with the date range shown on the Page.
- [ ] A comparison table of vendor quotes that the Bot updates when a new quote arrives in its inbox.
- [ ] A reading list or research brief that grows as the Bot finds new sources, each with a link.
- [ ] A launch tracker of open tasks, owners and statuses, the docs' own example, shared with the team rather than posted in a channel.

Editorial template (replace placeholders and review access before running):

```text
Build a Page called [title] for [audience]. Use only [named sources or connected apps]. Include [sections, tables or charts], and show the date and time the data was read at the top. Cite the source of every number. Keep the Page private; do not share it. Then propose a routine that updates this same Page every [schedule] and tell me what each run will read. Do not create the routine until I approve it.
```

Sources: https://docs.x.ai/grok-bot/files-and-results, https://docs.x.ai/grok-bot/skills-routines-and-automations, https://cursor.com/help/grok-bot/routines

## Limits and open questions

Several things the sources do not settle. Enterprise availability is the clearest disagreement: Cursor's help says Pages is not yet available on Enterprise teams, while the docs describe Enterprise users sharing Pages with users, groups or teams. The version note differs too: Cursor's help points to 0.60.0 on desktop and 1.14.0 on the phone, while the changelog lists Pages as new on October 22, so a rollout rather than an app update may decide when you see them.

Neither source we read describes a version history, a size limit, an export format or a way to restore an earlier version of a Page; when the Bot updates a Page, the earlier chat card simply opens the latest version. Because a Page is built from what the Bot can reach, check a Page that pulls from connected apps before widening its audience: the people you share it with see what the Bot put there, not what their own access would show them. Our [Shared Bots guide](https://www.grokbotwiki.com/guides/grok-bot-team-bots) covers the team-side admin controls, and [Is Grok Bot safe?](https://www.grokbotwiki.com/guides/is-grok-bot-safe) the wider security model.

Sources: https://cursor.com/help/grok-bot/pages, https://docs.x.ai/grok-bot/files-and-results, https://x.ai/changelog/bot#v0.75.2

## Quick answers

### What is a Grok Bot Page?

Something a Bot builds for you to read, such as a report, memo, dashboard, tracker or explainer. Cursor's help says it can hold text, tables, charts and controls like filters and switches, and the docs add heat maps and flow charts. It lives in the Bot's Library, and the 0.75.2 changelog entry (October 22) says you can edit it together or have the Bot keep it up to date.

### Can I edit a Page myself?

Only its title. Cursor's help says you change a Page by asking the Bot in the chat panel beside it, and the Bot edits the same Page, so everyone who can open it sees the change. Filters and switches change what you see, not what the Page holds, and nothing you do on the Page is saved. To rename a Page you made, click its title.

### Who can see a Page I share?

Whoever you choose under Who can view: people you invite (Only you on a personal account), your team, or anyone with the link. A new Page is private until you share it. An anyone-with-the-link Page gets its own address on pages.grok.bot that opens without signing in, so share it only when it holds nothing private. Everyone you share with can read the Page and use its controls; only the Bot can change it.

### Are Pages available on Enterprise plans?

The sources disagree. Cursor's Pages help, checked October 25, says Pages is rolling out gradually and is not yet available on Enterprise teams, and that public sharing is off on Enterprise. The docs.x.ai files and results page says users on Enterprise plans can share Pages with specific users, groups or teams, and the 0.75.2 changelog says Page owners on teams can share with their whole organization or another team. Check your own app.

### Can a routine keep a Page up to date?

Yes, according to the docs: you can ask Bots to update or create Pages on routines. When the Bot updates a Page, Cursor's help says the earlier card in the chat shows Updated, and clicking it opens the latest version. Each run spends usage like any other routine run.

### How do I stop sharing a Page or delete it?

Open Share again and pick a narrower option, or use the dashboard. Cursor's help says Pages you've shared are listed under Grok Bot Pages in Shared Canvases on your Cursor dashboard, where you can change who can view a Page or delete it; deleting means anyone with the link loses access. The 0.75.2 changelog calls this the dashboard's Pages section.

## Sources

- [Cursor help: Pages](https://cursor.com/help/grok-bot/pages)
- [Grok Bot changelog: 0.78.1, several Page edits at once, diagram labels (October 27)](https://x.ai/changelog/bot#v0.78.1)
- [Grok Bot changelog: 0.77.0, delete a Page from the Library, Shared with your team (October 26)](https://x.ai/changelog/bot#v0.77.0)
- [Files and results: Pages](https://docs.x.ai/grok-bot/files-and-results)
- [Grok Bot changelog: 0.75.2, Pages, new chat cards and video creation (October 22)](https://x.ai/changelog/bot#v0.75.2)
- [Skills and routines](https://docs.x.ai/grok-bot/skills-routines-and-automations)
- [Cursor help: Grok Bot routines](https://cursor.com/help/grok-bot/routines)

---

# Write a workflow brief Grok Bot can finish

> Replace a vague job title with a concrete deliverable, source rules, limits, and a checkable definition of done.

- Canonical page: https://www.grokbotwiki.com/guides/write-a-workflow-brief
- Sources checked: 2026-10-29
- Evidence: Official getting started, files and results, and approvals docs and SpaceXSI's October 20 incident-sweep post rechecked October 29, 2026; the Grok Bot changelog (through 0.75.5, read October 25) refused our automated check on October 29 · the IncidentSweep example is SpaceXSI's own account, not verified by us; the brief templates are original editorial tools, not executed workflows. Suggested workflows have not been independently tested.
- Publisher: Grok Bot Wiki, an independent guide not affiliated with SpaceXSI, xAI or X.

## Start from a reviewable output

A brief Grok Bot can finish names five things, which the official getting started guide says a strong request states: the outcome (what should be finished), the sources that matter (which apps, sites, files or conversations), the constraints (what to avoid or ask about first), the deliverable (what to return) and where the Bot should stop for you.

The files and results guide adds the other half: ask for the artifact and its acceptance criteria up front, and for consequential work have the Bot separate facts found in sources, assumptions, actions already completed, actions waiting for approval and open questions. The brief below combines both into an original planning template; it is not a vendor feature or an executed workflow.

Sources: https://docs.x.ai/grok-bot/get-started, https://docs.x.ai/grok-bot/files-and-results

## Define the last mile first

'Be my research assistant' does not say what would make the task complete. 'Compare three scheduling tools against our requirements and return a cited decision table' gives the Bot a finish line. Add the columns you need, the audience, and the decision the output should support. If you are still choosing which job to hand off first, Jobbit's [50 AI automation ideas for small businesses](https://jobbit.uk/en/blog/ai-automation-ideas-for-small-business-2026) is a useful list to pick from; then write the finish line for the one you choose.

Separate inclusion rules from preference. 'Only evaluate products with a publicly documented export option' is a rule; 'I prefer a simple interface' needs interpretation. Ask for uncertainty when a requirement cannot be checked. Otherwise, the output may silently treat missing evidence as a pass.

For anything involving dates, name the time zone and cutoff. For changing information, ask for when it was checked. For an existing file, identify whether the deliverable is a revised original or a new copy. These small choices prevent review friction.

1. Name the decision or job the artifact will help you finish.
2. List the smallest source set that can answer it.
3. Define inclusion, exclusion, and freshness rules.
4. State which actions are permitted now and which require a separate decision.
5. Specify what the Bot should return if only part of the task is possible.

## An official example: give the Bot a job, not a task

SpaceXSI's October 20 post on incident response, by Chris Bowie and Isaac Hopkinson, is the clearest vendor-published example of a job-shaped brief so far. Its support team built two Grok Bot teammates. IncidentWatch runs every five minutes, reviews the previous 15 minutes of tickets for a spike around the same problem, and, if the problem is not already a known incident, alerts the on-call support engineer with the apparent issue, the number of matching tickets and examples, while holding clearly matching tickets.

IncidentSweep handles the clean-up. The engineer states which tickets to consider and which to exclude, and the exact message to send. The Bot reviews each ticket, sets aside any it cannot confidently connect to the incident, and shows the proposed batch and the exact message for approval. Only then does it send, in small batches, recording each action. It never adds tickets after approval, and if something fails it stops and reports. The post's theme is "Give Bots jobs, not tasks."

Every field of the brief below is visible in that design: a scope with explicit exclusions, a deliverable you can review (the batch and the message), a review boundary (approval of the whole batch), an evidence trail (a record per action) and failure behavior (stop and report). SpaceXSI says that on September 18 IncidentSweep cleared 204 tickets in about 10 minutes with an engineer reviewing and approving the batch. That is the vendor's own figure about its own support team; we have not verified it or run the setup.

- [ ] Scope is written as include and exclude rules, not as "the relevant tickets".
- [ ] Anything the Bot cannot confidently classify is set aside and listed, never quietly included.
- [ ] The approval covers a frozen batch and the exact outgoing text.
- [ ] Nothing joins the batch after approval; new items need a new approval.
- [ ] Each action is recorded, and the first failure stops the run with a report.

Sources: https://x.ai/news/incident-sweep

## Copy and fill in the brief

Replace the placeholders with concrete names. Remove fields that do not apply, but keep the acceptance checks and the failure behavior.

Editorial template (replace placeholders and review access before running):

```text
Outcome: [decision or finished job].
Audience: [who will use it].
Sources: [files, URLs, accounts, and authoritative source if they conflict].
Scope: [included records/topics], excluding [out of scope].
Time window: [start/end, time zone, freshness requirement].
Deliverable: [artifact and required sections/columns].
Allowed actions: [reads or explicitly authorized edits].
Review boundary: [actions requiring separate approval].
Acceptance checks: [three observable conditions].
Evidence: source links, timestamps with time zone, and a list of anything you could not verify.
If blocked: return the completed portion, identify missing evidence, and explain the smallest next step. Do not invent missing facts or quietly substitute old inputs.
At completion: link the artifact, summarize validation, and list separately the facts found, assumptions, actions completed, actions awaiting approval, and open questions.
```

## A batch-approval brief for bulk actions

When the job ends in many similar writes, such as replies to tickets, labels on emails or updates to records, borrow the approved-batch pattern from the IncidentSweep example above. This brief is our original adaptation of that published pattern, not SpaceXSI's configuration and not a tested workflow. Start it on a handful of safe records.

Editorial template (replace placeholders and review access before running):

```text
Job: prepare one batch action for my approval.
Scope: include [records matching these rules]; exclude [records matching these rules]. Source of truth: [system or export].
Action: [exact action], using this exact text: [message]. Do not reword it.
Review each candidate record against the scope. Set aside any record you cannot confidently match and list it with the reason.
Before acting, show me: the proposed batch with record IDs, the set-aside list, the exact text, and the count of each.
Wait for my approval of that batch. After approval, act only on the approved records, in small batches of [size]. Do not add records after approval; list any new matches separately for a later decision.
Record each action with record ID, time and result.
If any action fails, stop, report what completed, what failed and what was not attempted, and wait for me.
```

## Match the brief to Grok Bot's controls

A brief states intent; the app enforces it. Write the review boundary in the brief, then check that a setting backs it up. Sending, purchasing, deleting and publishing belong behind Ask first rules, which since 0.68.0 appear under Custom Rules in Settings. Email and Slack draft cards are the review point for messages; 0.64.0 lets you disable drafts for a Bot so it sends directly, so leave them on while a workflow is new.

Your wording now matters more. Since 0.75.5 (October 23), an email or Slack message you ask a Bot to send in a chat goes out once Auto-review allows it, while sends on routine and other turns still wait as drafts, and Auto-review asks less often for an action you asked for in your own words. The same release says Auto-review no longer waves through an action your request said to stop before, such as sending a message you asked only to draft, and that after you deny an approval card the Bot stops and does not retry until your next message. So write "draft only" or "stop before sending" explicitly when that is the boundary. Bots can also now save logins and cards to a Vault and check out with them; if a brief involves buying anything, name the spending limit and the approval point.

Keep the deliverable in the conversation. Bots can read files other Bots save in /workspace, which helps handoffs, but the docs treat it as a place for intermediate material; the final result or a link to it belongs in the chat. When you want changes, ask the Bot to update the existing artifact rather than produce another copy.

Sources: https://docs.x.ai/grok-bot/approvals-security-and-privacy, https://docs.x.ai/grok-bot/files-and-results, https://x.ai/changelog/bot

## Review the brief before the answer

Imagine the Bot delivers exactly what you asked for. Would that be enough to make your decision? If a critical comparison is absent from the specification, add it now. A more elaborate prompt is not automatically better; the useful detail is whatever prevents an expensive misunderstanding.

After the first run, improve one instruction at a time. Keep the failed example and the corrected rule together, and name lasting preferences explicitly, as the getting started guide suggests, so the Bot carries them into future work. Give each Bot one focus: the docs say focused Bots build more useful context than one catch-all Bot. Once the method is stable, ask the Bot to save it as a skill. Our [workflow brief builder](https://www.grokbotwiki.com/workflow-builder) turns these fields into a brief you can copy, and [the evaluation guide](https://www.grokbotwiki.com/guides/evaluate-a-workflow) shows how to score the results.

- [ ] A reviewer can tell when the task is complete.
- [ ] Source conflicts have a rule or remain explicit.
- [ ] The Bot knows what to do with partial results.
- [ ] The final output distinguishes evidence from recommendations.

Sources: https://docs.x.ai/grok-bot/get-started

## Sources

- [Official getting started guide](https://docs.x.ai/grok-bot/get-started)
- [Official files and results guide](https://docs.x.ai/grok-bot/files-and-results)
- [Official approvals and privacy guide](https://docs.x.ai/grok-bot/approvals-security-and-privacy)
- [Grok Bot changelog (0.75.5: Auto-review and draft changes)](https://x.ai/changelog/bot)
- [SpaceXSI: Using Grok Bot to detect and respond to incidents (October 20, 2026)](https://x.ai/news/incident-sweep)

---

# Is Grok Bot safe? Security, privacy and your logins

> What Grok Bot can reach, where your data lives, whether it trains on it, who sees your passwords, Vault and the Secure Form issue, plus a safer setup.

- Canonical page: https://www.grokbotwiki.com/guides/is-grok-bot-safe
- Sources checked: 2026-10-30
- Evidence: Official security documentation checked October 7, 2026 · approvals docs, Cursor's secrets (Vault), plugins and Shared Bots help, changelog entries 0.71.2, 0.75.2 and 0.75.5, and the Secure Form forum thread checked October 25, 2026 · changelog entry 0.75.8 read October 27 · changelog entry 0.77.0 and docs.x.ai's new Vault and Shared Bots pages read October 28 · changelog entry 0.78.1 (October 27) and Cursor's secrets help (CSV import) read October 29 · official 1Password and mobile (phone apps) docs read October 30 · not a security audit or penetration test · approval expiry rechecked in Cursor's how-to help and the official approvals docs October 29, 2026. Suggested workflows have not been independently tested.
- Publisher: Grok Bot Wiki, an independent guide not affiliated with SpaceXSI, xAI or X.

## The short answer

Grok Bot's documented protections are real but partial. Each user gets an isolated cloud computer, plugin tokens stay on Cursor's servers, and Privacy Mode keeps your data out of training. The risks sit closer to you: every Bot shares your logins, and now anything you save in Vault; outside content can try to steer a Bot; and in October the in-chat password form leaked into page snapshots.

This page summarizes SpaceXSI's security documentation as of October 7, 2026, its approvals and Shared Bots documentation, the changelog through 0.75.5 (October 23), and Cursor's help pages and attributed Cursor staff replies as of October 25. It is not a security audit; we have not tested these controls ourselves.

| Risk | What the docs or staff say | What to do |
| --- | --- | --- |
| Other users reaching your computer | Each user gets a dedicated Firecracker microVM; one user cannot reach another's | Nothing; this is Cursor's side |
| One of your Bots using another's login | All your Bots share one computer, its files and browser sessions; Bots are not a security boundary | Sign in only to what any Bot may use; separate Cursor user for anything that must stay apart |
| Passwords in the in-chat form | October 5: a Secure Form password appeared in a page snapshot; fix in progress, not confirmed shipped by October 25 | Choose Open the screen and type passwords yourself |
| Logins and cards saved in Vault | Since 0.75.5 Bots fill saved logins, cards and contact info without seeing the secret values; every Bot on your account can use every item, and a saved card needs no per-payment approval | Save only what any Bot may use; leave cards out if you want to approve each payment |
| A Bot paying, sending or deleting on its own | Bots can pay with X Money, Stripe Link, Shop Pay and Vault cards; since 0.75.5 messages you ask for go out once Auto-review allows them, while routine sends wait as drafts | Ask first rules on purchases, sending and deleting; they always stop a matching action |
| A web page steering a Bot | Outside content is marked untrusted; defenses reduce but do not eliminate the risk | Ask first rules on sending, buying, deleting and publishing |
| Your data used for training | Not with Privacy Mode on; Legacy Privacy Mode is unsupported | Check your Cursor privacy setting |
| A Bot running commands on your own laptop | Off unless you allow it; default is Ask every time; the docs recommend Never allow | Set Execution on Local Computer to Never allow unless you need it |

Sources: https://docs.x.ai/grok-bot/security-faq, https://docs.x.ai/grok-bot/security, https://docs.x.ai/grok-bot/approvals-security-and-privacy, https://forum.cursor.com/t/grok-bot-browser-snapshot-shows-a-password-filled-by-the-secure-form-requestuserform-in-plain-text/173748, https://cursor.com/help/grok-bot/secrets, https://x.ai/changelog/bot#v0.75.2, https://x.ai/changelog/bot#v0.75.5

## What a Bot can reach

Isolation is per user, not per Bot. The security FAQ says each user gets a dedicated Firecracker microVM with its own kernel, memory and virtual devices, and one user cannot reach another user's computer. Within your account, every Bot shares that computer, so a file, browser session or command-line credential on it is available to all of your Bots; Cursor's help puts it plainly: after you sign in, every Bot on your account can use that sign-in until it expires. A Bot has no identity of its own and cannot hold more access than you do.

A Cursor staff member said on October 2 that the team is working on letting an individual Bot keep its own browser session; until that ships, treat the shared computer as one trust zone. Plugins are account-wide too: an installed plugin is available to every Bot, and blocking a plugin does not block that service's website, which only Enterprise Network Controls can close. Our [shared-computer guide](https://www.grokbotwiki.com/guides/grok-bot-shared-computer) has the details.

Sources: https://docs.x.ai/grok-bot/security-faq, https://docs.x.ai/grok-bot/approvals-security-and-privacy, https://docs.x.ai/grok-bot/computer-and-apps, https://cursor.com/help/grok-bot/how-to, https://forum.cursor.com/t/grok-bot-ship-real-session-fences-bots-are-not-a-security-boundary/168476

## Logins, passwords, Vault and the Secure Form issue

The documented way to sign a Bot in is to take over its screen and type the password, passkey or code yourself; the docs say not to send a password or one-time code in ordinary chat. For keys, a secret request masks the value, keeps it out of the transcript and away from the model. When a page needs your input, a Bot can also show a form in the chat, the Secure Form, and fill your answers into the page. Since 0.71.2 (October 14) Bots ask for logins and other multi-field details on one Secure Form instead of a secret request card, and the form fills fields on more websites, including embedded frames. Note one change that cuts the other way: since 0.75.2 (October 22), if you already shared a password or code in the chat, the Bot uses it instead of refusing to continue. That makes a pasted password work, not safe; it is now in the conversation.

That form is the open issue. On October 5 a user reported that after the Secure Form filled a password, the snapshot the Bot took before clicking Sign in showed it in plain text, putting it in the session's tool output. A Cursor staff member replied the same day that this should not happen, that a fix was in progress, and that the safest way to sign in meanwhile is to choose Open the screen and do it yourself. No changelog entry from 0.68.1 (October 7) to 0.75.5 (October 23) mentions the snapshot. When we checked on October 25 the thread's last post was still a user asking on October 7 to be told when it is fixed; Cursor had posted nothing since October 5.

Vault, new in 0.75.5 (October 23) and needing Grok Bot 0.75.2 or later, changes the trade-off. In Settings → Vault you save logins, cards and contact info, or tick Securely save to Bot's vault on a Secure Form, and Bots fill them in to sign in or check out. Cursor's help says a Bot never sees a saved password, card number or security code; it can see your contact info and which logins you saved. Signing in, a Bot tries a Vault login first, then a connected password manager such as 1Password, then asks you with a Secure Form, and if you let it pick a password when it signs up for a site, Vault generates and saves it. Contact details you give in chat are saved as contact info once the task is done unless you say otherwise.

What you give up is control over reach. Everything in Vault is available to every Bot on your account and cannot be limited to one Bot; Vault is not supported on Shared Bots. There is no setting that makes a Bot ask before it uses a saved card, so Cursor's own advice, if you want to approve each payment, is not to save the card: leave Securely save to Bot's vault unchecked, and do not submit a form that lacks that checkbox, because it saves straight to Vault. Passwords, card numbers and websites change only in Settings → Vault, and a CSV import from another password manager leaves an unencrypted export you should delete. Our view: Vault is reasonable for low-stakes logins you would let any Bot use; for email, banking and admin accounts, keep typing the password on the Bot's screen yourself until Cursor confirms the snapshot fix, since the help does not say whether a Vault login is filled into the page differently from a Secure Form.

0.77.0 (October 26) widens what Vault decides. Settings → Vault now lists Payment accounts, wallets such as Link or X Money, and a Default payment method that Grok Bot pays with first; the changelog says you still approve every purchase, and the new docs.x.ai Vault page repeats that a saved card fills in at checkout without asking you each time and that no setting requires approval per use. Bots now try your saved Vault logins and cards before a password manager or another way to pay, each entry has a Hints field that tells Bots when to use it, and a Bot can update a saved entry's name, hint and card details when you ask, although passwords, usernames, websites and card numbers still change only in Settings. The docs also spell out where the Bot hands you the computer instead of filling: single sign-on, a passkey, a CAPTCHA, an approval on another device, a QR code or a bank card verification, and that the signed-in session then stays on the computer for every Bot. Treat the default payment method as the new boundary: if you do not want a Bot to be able to pay, keep cards out of Vault rather than relying on the approval step.

1Password changed in the same release: it now connects without a shared vault, you approve each login in 1Password, which fills it in the Bot's browser without the Bot seeing it, and on Windows and Linux the Bot notices an installed 1Password app and can offer to connect it; the change needs Grok Bot 0.68.0 or later. Before that, Cursor's help described the integration as rolling out gradually: you approve each login in 1Password, 1Password fills it, and Bots never see the values; it offers logins only from your Personal (or Private) vault and does not fill payment cards. Staff described known issues on September 30, before that help page described the new integration: on some pages, including Instagram and Letterboxd, the card says Filled while the password stays empty, and the Google sign-in popup cannot be filled from 1Password; on October 10 they said the full-page Google sign-in has the same problem, with no ETA, and that the workaround is to type the password yourself when the Bot hands you the screen. Hardware security keys work on macOS and Windows, with every use approved by you. The official docs, read October 30, 2026, add that the new 1Password integration works with personal and Family accounts and needs 1Password 8.12.42 or later. If you used 1Password with Grok Bot before, connect it again, and move the logins from the vault you shared with the old integration into your Personal or Private vault (on a Mac, Move to Private does it). A phone that says 1Password can only be set up on a Mac has not received the new integration yet, so set it up from the desktop app.

Bots can now reach apps on your phone, too. The official mobile docs, read October 30, 2026, say a Bot you own can, in your own chat, read and change your calendar, read your contacts and location, set alarms and timers and, on iPhone, change Reminders and Apple Home accessories, including locks, garage doors and security systems. Each app needs your phone's permission first. After that, if your team's admin set a limit, it decides whether each use asks you; with no team limit, Auto Review checks each use if it is on, and with Auto Review off the Bot uses your phone's apps without asking. If you would rather not let a Bot unlock a door, don't grant Home access.

0.78.1 (October 27) adds payments and cancellations that Vault makes possible. Shop Pay now connects from the Vault's Payments tab, where you can pick it under Pay with or make it the payment method Bots use first; on a product page, Buy now starts an order you approve, and after you order, the Bot tracks the shipment. Three templates act on recurring charges: Try it, don't pay for it starts a free trial for you and cancels it, or reminds you, before it bills; Find unused subscriptions cancels plans you pick; Watch subscription prices checks renewal prices; and the changelog says Bots confirm with you before changing a subscription. Cursor's secrets help, checked October 29, also describes a desktop import of logins from a CSV export of 1Password, Chrome or Edge, Safari or Apple Passwords, Firefox, Bitwarden or LastPass: the file is read on your computer and never uploaded, must be under 5 MB, items already in Vault are skipped, rows without a password or with a non-https website are not imported, LastPass exports bring cards along, and the help says to delete the CSV afterwards because it holds your passwords unencrypted. An import makes every one of those logins usable by every Bot on your account at once, so import the logins Bots need rather than the whole export.

Sources: https://x.ai/changelog/bot#v0.78.1, https://docs.x.ai/grok-bot/computer-and-apps, https://docs.x.ai/grok-bot/approvals-security-and-privacy, https://docs.x.ai/grok-bot/mobile, https://cursor.com/help/grok-bot/secrets, https://cursor.com/help/grok-bot/connect-apps, https://forum.cursor.com/t/grok-bot-browser-snapshot-shows-a-password-filled-by-the-secure-form-requestuserform-in-plain-text/173748, https://x.ai/changelog/bot, https://x.ai/changelog/bot#v0.71.2, https://x.ai/changelog/bot#v0.75.2, https://x.ai/changelog/bot#v0.75.5, https://forum.cursor.com/t/grok-bot-shared-1password-autofill-says-filled-but-password-stays-empty-instagram/173365, https://forum.cursor.com/t/grok-bot-wont-login-to-google-account-using-1password/173423, https://x.ai/changelog/bot#v0.77.0, https://docs.x.ai/grok-bot/vault

## Approvals and Auto Review

Approval cards show the proposed action: Allow once, Always allow (which can save a rule) or Deny. Auto Review is an independent review model that checks risky actions before they run, covering shell commands, plugin calls, computer use, changes to routines and triggers, and launching Cloud Agents or subagents. The docs say it does not review every side effect; memory writes and most settings changes are examples. An approval controls the proposed action; it does not reverse work already done.

Rules decide what stops. Ask first rules always stop matching actions for you; Allow automatically rules let actions through only if the review finds no other reason to stop; when both match, Ask first wins. Cursor's help and the official docs, checked October 29, say an approval raised by unattended work, such as a routine, a trigger or another Bot, expires after about 30 minutes, and the action then does not run. On Shared Bots, a conversation where nobody can answer an approval runs without Auto-review unless your team requires it; the October 11 changelog entry adds that teammates can now approve a Shared Bot's Auto-review requests, including Always allow, from their own DM with it.

The same entry (0.69.0 to 0.70.2) adds two checks of its own. Before an action it cannot undo, such as sending, posting, buying or deleting, a Bot checks your own messages for approval, which matters because Bots can now pay with X Money or Stripe Link. And after a bank or brokerage connector returns data, the Bot asks before sharing it anywhere else. The notes describe Bot behaviour rather than a setting, so they add to your rules rather than replacing them. Our [permission boundaries guide](https://www.grokbotwiki.com/guides/permission-boundaries) turns this into a worksheet.

Auto-review then changed twice in late October. Since 0.75.2 (October 22), its approval cards describe the action in one sentence, name the app with its logo and flag irreversible or sensitive changes, and an approval you do not answer in time leaves a chat line naming what expired. Since 0.75.5 (October 23), Auto-review asks less often for an action you asked for in your own words, falls back to an approval card less often, and emails and Slack messages you ask a Bot to send go out once it allows them, while sends on routine and other turns still wait as drafts. Two fixes tighten it: Auto-review no longer waves through an action your request said to stop before, such as sending a message you asked only to draft, and after you deny a card the Bot stops and does not try that action again until you send another message. Since 0.71.2, Stop also ends a Bot's background subagents and expires their pending approval cards. Fewer cards means your wording carries more weight, so say draft only or stop before sending when you mean it, and keep Ask first rules for anything you always want to see.

0.75.8 (October 24) goes one step further. Auto-review takes a second look before showing an approval card, so fewer safe actions need one, and a Bot saving or editing one of its routines no longer counts as risky by itself. The rules themselves can now change from a chat: in the app, a Bot can offer to add, change or remove one of your Auto-review rules on a card you confirm. A confirmed rule outlasts the conversation, so read the card as carefully as you would a Settings change, and remember that an Allow rule a Bot proposed is still only a suggestion until you confirm it. The same entry says a Bot in a chat only you can see reads your own private files without asking first, and that when background work finishes the Bot completes what you asked and says what it would do next instead of acting on its own or on another agent's approval.

0.77.0 (October 26) puts the rules on one screen and loosens the defaults a little more. Settings now has a Permissions section that lists your Auto-review rules under Always Ask and Allow without Asking, each with its own Add Rule button, so you can finally audit everything a Bot has been allowed in one place; the rule cards in chat show each rule as a sentence and name any older Allow rule removed to make room. Approval cards stay open for 30 minutes instead of 10, in the app and in Slack, which helps routines whose approvals used to expire but also leaves a pending action waiting longer. Auto-review now lets through more private actions you can undo without a card, keeps an approval when only your open tabs change, and background work you start in your own words no longer asks for approval to start; when a safety filter stops a computer task, the Bot tries another model before asking you to do that step. The direction since 0.75.5 is consistent: fewer cards, more weight on your wording and your rules. If there is an action you always want to see, write the Ask first rule and check it on the Permissions screen.

Sources: https://docs.x.ai/grok-bot/security, https://docs.x.ai/grok-bot/approvals-security-and-privacy, https://cursor.com/help/grok-bot/how-to, https://docs.x.ai/grok-bot/shared-bots, https://x.ai/changelog/bot, https://x.ai/changelog/bot#v0.71.2, https://x.ai/changelog/bot#v0.75.2, https://x.ai/changelog/bot#v0.75.5, https://x.ai/changelog/bot#v0.75.8, https://x.ai/changelog/bot#v0.77.0

## Prompt injection

The security page is direct about it: content a Bot reads from the outside world, such as web pages, plugin results and command output, can try to steer it. Grok Bot layers Auto Review over controls that do not depend on a model's judgment, including the network policy, per-action approvals and per-user isolation, and marks outside content as untrusted. The docs say these controls reduce, but do not eliminate, the risk, which is the reason to keep consequential actions behind approval.

In practice, the riskiest setups combine broad reading with unattended writing: a routine that reads every new email or every message in a busy channel and can also send, pay or delete. Keep listeners narrow, keep drafts on, and give a routine a stop-if-nothing-changed rule. A forum question asking for more detail on prompt-injection protection, from August 30, had no staff reply when we checked.

Sources: https://docs.x.ai/grok-bot/security, https://forum.cursor.com/t/grokbot-security-isolation-prompt-injection-protection/169955

## Your data: training, retention and location

Grok Bot uses Cursor's sign-in and data settings. It requires data storage, so Legacy Privacy Mode is not supported. Training opt-out follows your Cursor privacy settings, and with Privacy Mode on, customer data is not used for training; x.ai/bot says the cloud computer is encrypted in transit and at rest. The docs say zero data retention follows Cursor's existing provider agreements, though providers may run abuse classifiers and store flagged data for investigation.

Your computer keeps files and browser sessions on a durable disk; idle computers hibernate, which is not deletion. Under Cursor's DPA, data is deleted or returned within 30 days of written direction after the service ends, and Cursor's help says deleting your account removes all data within 30 days. Enterprise teams can turn on Action Recording, which keeps scrubbed Bot actions for 90 days. Computers run in the United States today, and Anysphere, the company behind Cursor, holds ISO/IEC 27001 and 42001 certifications that include Grok Bot.

Sources: https://docs.x.ai/grok-bot/security, https://docs.x.ai/grok-bot/faq, https://docs.x.ai/grok-bot/approvals-security-and-privacy, https://x.ai/bot, https://cursor.com/help/grok-bot/delete-account, https://forum.cursor.com/t/privacy-and-term-of-use-of-grok-bot-with-cursor-account/168075

## Shared Bots (formerly Team Bots) and shared conversations

Shared Bots, which the official docs renamed from Team Bots by October 28, keep each teammate's chat private, and a plugin that needs a sign-in uses the account of whoever is talking, so one person's access is never lent to another. Two things are shared by design: team memory, read by every teammate's conversation, and the Bot's secrets, which it can use in anyone's chat. Slack channels and threads share one computer for that Bot, so do not post anything there the whole channel should not see. Vault is not supported on shared Bots; the docs say to add keys under the Bot's Secrets instead, where they are used in every teammate's chat. Since 0.75.5, Bots record who asked for each message they post in Slack, and Shared Bots say whose connector they used. Since 0.77.0 (October 26), people without a linked Grok Bot account cannot use the owner's logins or private data through the owner's Bot in Slack, linked teammates use their own connectors and memory, in shared Slack conversations the Bot checks each post against who can read it before sending, and team admins can limit Bot sharing to admins. See [our Shared Bots guide](https://www.grokbotwiki.com/guides/grok-bot-team-bots).

Sources: https://docs.x.ai/grok-bot/shared-bots, https://docs.x.ai/grok-bot/vault, https://cursor.com/help/grok-bot/secrets, https://x.ai/changelog/bot#v0.75.5, https://x.ai/changelog/bot#v0.77.0

## A safer setup in ten minutes

These steps come from the docs' least-privilege advice and the issues above. They do not make a Bot safe on their own; they limit what a mistake can reach.

1. Check your Cursor privacy setting, and keep Privacy Mode on if training opt-out matters to you.
2. Add Ask first rules in Settings → General → Auto-review for sending messages, purchases, deletions and publishing.
3. Leave email and Slack drafts on, so you review a draft card before anything goes out.
4. Set Execution on Local Computer to Never allow unless a Bot needs your local files.
5. Prefer plugins to browser logins; connect only the accounts a task needs, and revoke them in the source service when it is done.
6. Type passwords on the Bot's screen yourself rather than in the Secure Form until Cursor confirms the snapshot fix; it had not by October 25. Do not paste them into chat either: since 0.75.2 the Bot will use what you paste.
7. Review Settings → Vault. Keep only logins any Bot may use, and remove saved cards if you want to approve each payment yourself.
8. Keep anything that must stay separate, such as banking or a work admin account, off the shared computer.
9. When a project ends, pause its routines, sign out of its sites, and remove its files from /workspace. Since 0.75.2 deleting a Bot permanently erases its conversations, memory, routines and attachments, but the note does not mention files it saved to the shared computer.

Sources: https://docs.x.ai/grok-bot/approvals-security-and-privacy, https://docs.x.ai/grok-bot/security, https://cursor.com/help/grok-bot/secrets, https://x.ai/changelog/bot#v0.75.2

## Quick answers

### Does Grok Bot train on my data?

Not with Privacy Mode on. The docs say training opt-out follows your Cursor account and privacy settings, and that with Privacy Mode enabled customer data is not used for training. A Cursor staff member said on August 12 that with Privacy Mode on, Grok Bot data is not used for training by Cursor or any model provider, including xAI. Legacy Privacy Mode, which stores nothing, does not work with Grok Bot at all.

### Is it safe to type a password into the Grok Bot Secure Form?

Not for now. On October 5 a Cursor staff member confirmed a report that a password filled by the in-chat Secure Form appeared in plain text in a page snapshot, said a fix was in progress, and advised choosing Open the screen and typing the password yourself. No changelog entry from 0.68.1 (October 7) to 0.75.5 (October 23) mentions a fix, and when we checked on October 25 the thread had no Cursor update since October 5. If you already used the form for a password, change it.

### Should I save my passwords and cards in Grok Bot's Vault?

Only what you are happy for every Bot to use. Vault (0.75.5) keeps logins, cards and contact info in Settings → Vault, and Cursor's help says a Bot never sees a saved password, card number or security code. The trade-off is reach: everything in Vault is available to every Bot on your account, you cannot limit an item to one Bot, and there is no setting that makes a Bot ask before it uses a saved card. No source says the October 5 Secure Form snapshot issue is fixed, and the help does not say whether a Vault login is filled into the page any differently, so for important accounts typing the password on the Bot's screen yourself is still the cautious choice.

### Can Grok Bot spend money or move my financial data?

It can pay, in more ways each release. The October 11 entry added X Money and Stripe Link, 0.75.2 (October 22) added Shop Pay, and 0.75.5 (October 23) lets Bots fill a card saved in Vault at checkout; Cursor's help says no setting requires your approval each time a saved card is used. Since 0.71.2 Bots also use card details or photos you send in chat. The October 11 entry says a Bot checks your own messages for approval before an action it cannot undo, such as buying, and asks before sharing data a bank or brokerage connector returned. Those are the Bot's behaviour, not settings, so add an Ask first rule for purchases and keep cards out of Vault if you want to approve each payment.

### Can I keep one Bot away from my bank or email login?

Not with Bot boundaries. Every Bot on your account shares one cloud computer, with its files, browser sessions and command-line credentials, and the docs say not to use separate Bots as a security boundary. If a login must stay isolated, keep it off Grok Bot or use a separate Cursor user, which gets its own computer.

### Where is my Grok Bot data stored?

In Cursor's cloud. The docs say Grok Bot computers run in the United States today, which is not the same as Cursor's US-only data residency program, and that your computer keeps files and browser sessions on a durable disk across sessions. Plugin tokens stay on Cursor's backend and are never stored on the computer.

### Can a web page trick my Bot into doing something?

It can try. The docs say content a Bot reads, such as web pages, plugin results and command output, can try to steer it, and that Grok Bot's defenses reduce but do not eliminate that risk. Keep sending, buying, deleting and publishing behind Ask first rules so a steered Bot still has to stop for you.

## Sources

- [Grok Bot docs: Vault and secure sign-in](https://docs.x.ai/grok-bot/vault)
- [Grok Bot changelog: 0.78.1 (Shop Pay in Vault, subscription templates, October 27)](https://x.ai/changelog/bot#v0.78.1)
- [Grok Bot changelog: 0.77.0 (Permissions screen, Vault Payments tab, 30-minute approval cards, October 26)](https://x.ai/changelog/bot#v0.77.0)
- [Grok Bot security](https://docs.x.ai/grok-bot/security)
- [Grok Bot security FAQ](https://docs.x.ai/grok-bot/security-faq)
- [Approvals, security and privacy](https://docs.x.ai/grok-bot/approvals-security-and-privacy)
- [Computer and apps](https://docs.x.ai/grok-bot/computer-and-apps)
- [Grok Bot for Mobile: let a Bot use your phone's apps](https://docs.x.ai/grok-bot/mobile)
- [Shared Bots (formerly Team Bots)](https://docs.x.ai/grok-bot/shared-bots)
- [Teams and enterprises](https://docs.x.ai/grok-bot/teams-and-enterprises)
- [Grok Bot FAQ](https://docs.x.ai/grok-bot/faq)
- [Grok Bot product page and FAQ](https://x.ai/bot)
- [Cursor help: store secrets securely](https://cursor.com/help/grok-bot/secrets)
- [Cursor help: how-tos (approval expiry)](https://cursor.com/help/grok-bot/how-to)
- [Cursor help: delete your Grok Bot account](https://cursor.com/help/grok-bot/delete-account)
- [Cursor help: Shared Bots (approvals)](https://cursor.com/help/grok-bot/shared-bots)
- [Grok Bot changelog (approval checks and payments in 0.69 to 0.70.2)](https://x.ai/changelog/bot)
- [Grok Bot changelog: 0.75.8 (Auto-review rule cards, second look before approval cards, October 24)](https://x.ai/changelog/bot#v0.75.8)
- [Grok Bot changelog: 0.75.5 (Vault, Auto-review changes, October 23)](https://x.ai/changelog/bot#v0.75.5)
- [Grok Bot changelog: 0.75.2 (approval card flags, passwords shared in chat, Shop Pay, October 22)](https://x.ai/changelog/bot#v0.75.2)
- [Grok Bot changelog: 0.71.2 (card details sent in chat, Secure Form changes, October 14)](https://x.ai/changelog/bot#v0.71.2)
- [Cursor help: connect plugins (1Password)](https://cursor.com/help/grok-bot/connect-apps)
- [Forum: password filled by the Secure Form shown in a page snapshot (staff reply, October 5)](https://forum.cursor.com/t/grok-bot-browser-snapshot-shows-a-password-filled-by-the-secure-form-requestuserform-in-plain-text/173748)
- [Forum: 1Password autofill says Filled but the password stays empty (staff reply, September 30)](https://forum.cursor.com/t/grok-bot-shared-1password-autofill-says-filled-but-password-stays-empty-instagram/173365)
- [Forum: Grok Bot will not log in to Google with 1Password (staff replies, September 30 and October 10)](https://forum.cursor.com/t/grok-bot-wont-login-to-google-account-using-1password/173423)
- [Forum: privacy and terms of use with a Cursor account (staff reply, August 12)](https://forum.cursor.com/t/privacy-and-term-of-use-of-grok-bot-with-cursor-account/168075)
- [Forum: Bots are not a security boundary (staff reply, October 2)](https://forum.cursor.com/t/grok-bot-ship-real-session-fences-bots-are-not-a-security-boundary/168476)
- [Forum: security isolation and prompt injection protection (no staff reply)](https://forum.cursor.com/t/grokbot-security-isolation-prompt-injection-protection/169955)

---

# Set permission boundaries before the work starts

> Define what a Bot may prepare, change or send, then back it with Custom Rules, draft cards and Auto Review before you approve anything.

- Canonical page: https://www.grokbotwiki.com/guides/permission-boundaries
- Sources checked: 2026-10-29
- Evidence: Official approvals docs, Cursor's Shared Bots, secrets (Vault) and agent email help, and changelog entries 0.71.2, 0.75.2 and 0.75.5 checked October 25, 2026; changelog entry 0.75.8 read October 27; changelog entry 0.77.0 and docs.x.ai's Vault page read October 28; overview docs and how-to help checked October 14 · the worksheet and brief are original editorial templates · approval expiry rechecked in Cursor's how-to help and the official approvals docs October 29, 2026. Suggested workflows have not been independently tested.
- Publisher: Grok Bot Wiki, an independent guide not affiliated with SpaceXSI, xAI or X.

## What a separate Bot does not separate

The official overview states that Bots on one account share computer files, sessions, and logins. Separate Bot names do not create separate access boundaries. The approval documentation describes model-based Auto Review and explicit action approvals; it recommends combining them with least privilege. Neither a prompt nor an automated review should be treated as an absolute guarantee.

The permission worksheet below is an original operating suggestion. Apply your organization's actual access policies when relevant. For the security model behind it, including the October Secure Form issue, see [Is Grok Bot safe?](https://www.grokbotwiki.com/guides/is-grok-bot-safe).

Sources: https://docs.x.ai/grok-bot/overview, https://docs.x.ai/grok-bot/approvals-security-and-privacy

## The controls that enforce a boundary

A boundary written in a brief is a request. These settings are what actually stop a Bot. The rows paraphrase the docs, Cursor's help and the changelog as of October 28, 2026.

| Control | What it does | Suggested starting point |
| --- | --- | --- |
| Permissions (Settings) | Since 0.77.0 (October 26), one section that lists every Auto-review rule under Always Ask and Allow without Asking, each with its own Add Rule button; needs Grok Bot 0.75.2 or later | Read it once a week; remove any Allow rule you do not remember writing |
| Approval card | Shows the proposed action and its inputs: Allow once, Always allow (saves a rule) or Deny. Since 0.75.2 Auto-review cards describe the action in one sentence, name the app and flag irreversible or sensitive changes; since 0.75.5 a denial stops the Bot from trying that action again until you send another message; since 0.77.0 cards stay open for 30 minutes instead of 10 | Allow once while you learn a workflow; deny anything you cannot identify |
| Custom Rules | Your saved approval rules, renamed from approval rules in 0.68.0. Ask first always stops a matching action; Allow automatically lets it through only if Auto Review finds no other reason to stop; Ask first wins when both match. Since 0.75.8 a Bot can offer to add, change or remove one of your rules on a card you confirm | Ask first for sending, purchasing, deleting and publishing; confirm a proposed rule only when it is as narrow as one you would write yourself |
| Auto Review | A review model that checks tool calls and computer actions before they run; an admin can require it. Since 0.75.5 it asks less often for an action you asked for in your own words, and no longer waves through an action your request said to stop before; since 0.75.8 it takes a second look before showing a card, so fewer safe actions need one, and a Bot editing its own routines is not risky by itself; since 0.77.0 it lets through more private actions you can undo and background work you start in your own words no longer asks to start | Leave on, and state stopping points explicitly in your request |
| Draft cards | Email and Slack messages arrive as editable drafts you send or discard; since 0.64.0 you can disable drafts for a Bot so it sends directly. Since 0.75.5, messages you ask a Bot to send in chat go out once Auto-review allows them; sends on routine and other turns still wait as drafts | Keep drafts on, and an Ask first rule on sending, until a Bot has sent several messages correctly |
| Vault | Since 0.75.5, saved logins, cards and contact info that every Bot on your account can fill without seeing the secret values; no setting requires approval before a saved card is used. Since 0.77.0, a Payments tab sets the Default payment method Bots pay with first, and Bots try Vault before a password manager | Save only low-stakes logins; keep cards out if you want to approve each payment |
| Execution on Local Computer | Whether Bots may run commands on the computer in front of you: Ask every time (default), Always allow or Never allow | Never allow unless a Bot needs local files |
| Stop | Since 0.68.1, ends a Bot stuck on an unresponsive step within about 30 seconds; since 0.71.2 it also ends background subagents and expires their pending approval cards | Use it, then check what already ran; Stop does not undo completed actions |
| Built-in checks (October 11) | The 0.69.0 to 0.70.2 changelog says a Bot checks your own messages for approval before an action it cannot undo (sending, posting, buying, deleting), and asks before sharing data a bank or brokerage connector returned | Count them as a backstop, not a rule: they are Bot behaviour you cannot configure |

Sources: https://docs.x.ai/grok-bot/approvals-security-and-privacy, https://cursor.com/help/grok-bot/how-to, https://x.ai/changelog/bot, https://x.ai/changelog/bot#v0.71.2, https://x.ai/changelog/bot#v0.75.2, https://x.ai/changelog/bot#v0.75.5, https://x.ai/changelog/bot#v0.75.8, https://x.ai/changelog/bot#v0.77.0, https://cursor.com/help/grok-bot/secrets, https://docs.x.ai/grok-bot/vault

## Rules that behave differently than you expect

The approvals docs, checked October 25, say personal Auto-review rules are saved to your account, so they apply from every desktop and the mobile app; earlier versions of the docs said rules stayed on the desktop where you made them. Rules your team locks cannot be edited, and your own rules can only make behavior stricter than the team's. Keep each rule narrow: ask first before sending external email, not allow everything in the browser.

Approvals raised by routines, triggers or other Bots expire after about 30 minutes, according to Cursor's help and the official docs checked October 29, and the action does not run; approvals in a chat you are in wait for you. That is a safe failure, but it can stall unattended work, so turn on notifications for Bots that own routines rather than broadening Always allow. Your starred primary Bot can offer to take work off your plate since 0.66.0; an offer is not an approval, and the same rules apply to whatever it does next.

Three changes in the October 11 changelog entry (0.69.0 to 0.70.2) affect where a boundary should sit. Bots can now pay with X Money or Stripe Link, so purchases are no longer only a browser checkout you would take over; put an Ask first rule on them. On a Shared Bot, teammates can approve Auto-review requests, including Always allow, from their own DM with it, so an Always allow there can come from anyone on the team; Cursor's Team Bots help, checked October 25, now says a Shared Bot asks the person it is answering. And passwords still belong on the Bot's screen: no release through 0.75.5 mentions the October 5 report of a Secure Form password appearing in a page snapshot, and Cursor had posted no update in that thread by October 25.

The October 23 release (0.75.5) moves the line between asking and sending. A message you ask for in chat now goes out once Auto-review allows it, and Auto-review asks less often for actions you asked for in your own words, so the wording of your request is part of the boundary: draft a reply and send a reply now lead to different outcomes. Cursor's agent email help says email from a routine or any turn you did not start with that request still waits as a draft, and that instructions inside an email the Bot received never count as your permission to send. Vault, added in the same release, is a boundary you set by what you save: every Bot on your account can use every saved item, and a saved card can be used at checkout without a per-payment approval.

Since 0.75.8 (October 24) the rules can also move from inside a chat: a Bot can offer to add, change or remove one of your Auto-review rules on a card you confirm. That is convenient when a Bot keeps hitting the same Ask first card for something you trust it with, but a rule confirmed on a card is the same as one written in Settings and applies to later chats too. Treat a proposed Allow rule like a boundary you are rewriting: check the verb and the target on the card, and decline it if it is broader than the one you would have written. The same release says Auto-review takes a second look before it shows a card, so a boundary you rely on should be an explicit Ask first rule rather than the expectation that a card will appear.

0.77.0 (October 26) gives you the audit tool this guide has been missing: Settings → Permissions lists every rule under Always Ask and Allow without Asking, so proposed rules you confirmed on cards can be reviewed next to the ones you wrote. It also moves two defaults: approval cards now wait 30 minutes instead of 10, so an unattended approval no longer fails as quickly, and the Vault's new Default payment method means a Bot pays with that method first, with Vault tried before a password manager. The payment boundary is therefore set by what you save, not by a rule, since the docs still say no setting requires approval per use of a saved card.

Sources: https://docs.x.ai/grok-bot/approvals-security-and-privacy, https://cursor.com/help/grok-bot/how-to, https://x.ai/changelog/bot, https://x.ai/changelog/bot#v0.75.5, https://x.ai/changelog/bot#v0.75.8, https://cursor.com/help/grok-bot/shared-bots, https://cursor.com/help/grok-bot/agent-email, https://cursor.com/help/grok-bot/secrets, https://forum.cursor.com/t/grok-bot-browser-snapshot-shows-a-password-filled-by-the-secure-form-requestuserform-in-plain-text/173748

## Write boundaries around verbs and targets

'Be careful with email' leaves too much open. 'Read the approved folder and draft replies; do not send, forward, archive, or change labels' identifies observable behavior. Do the same for a database, repository, or publishing system: name the resources and the permitted operation.

For a recurring job, consider three stages. First, gather evidence. Next, prepare a proposed change. Finally, apply a specific approved change if authorized. The evidence and proposal should be useful on their own so a human can decline execution without losing the value of the work.

When credentials are needed, take over the Bot's screen and type them yourself, or use a secure secret request where a connection offers one; the docs say not to paste passwords or one-time codes into chat. Since 0.75.2 a Bot uses a password or code you already pasted instead of refusing, so a pasted secret is no longer stopped for you. Do not put secret values in the brief, a reusable skill, or an example intended for sharing. [The shared-computer guide](https://www.grokbotwiki.com/guides/grok-bot-shared-computer) explains why every Bot can reach a login once any Bot has used it, and the same holds for anything saved in Vault.

1. List the systems the task needs and the smallest usable account permissions.
2. Write allowed operations and prohibited operations in plain language.
3. Define what an approval request must show: exact target, before/after values, and likely effect.
4. Use a harmless sample to check that the workflow pauses at the intended point.
5. Revisit access when you add a Bot, connection, or new responsibility.

Sources: https://docs.x.ai/grok-bot/approvals-security-and-privacy, https://x.ai/changelog/bot#v0.75.2, https://cursor.com/help/grok-bot/secrets

## A preparation-only brief

Adapt the allowed actions to your actual task. This template does not configure or replace technical permissions.

Editorial template (replace placeholders and review access before running):

```text
Work only with [approved sources]. You may read and produce a separate draft artifact. Do not send messages, publish, purchase, delete, modify permissions, accept terms, or alter the source systems. For each recommended change, show the exact target, current state, proposed state, rationale, and uncertainty. Finish the analysis and draft before asking for a decision. If the task requires additional access, explain the specific missing operation; do not broaden access yourself.
```

## Review the effect, not just the explanation

A persuasive rationale cannot compensate for the wrong destination or account. Compare the actual operation with the approved scope. For batch work, check the count and selection rule as well as a sample record. Keep approval narrow enough that you can tell what you authorized later.

- [ ] The target account and resource are recognizable.
- [ ] The proposed change can be inspected before execution.
- [ ] The scope does not silently include unrelated records.
- [ ] Completed changes will be reported separately from pending ones.

## Sources

- [Grok Bot changelog: 0.75.8 (Auto-review rule cards, fewer approval cards, October 24)](https://x.ai/changelog/bot#v0.75.8)
- [Grok Bot changelog: 0.77.0 (Permissions screen, 30-minute approval cards, default payment method, October 26)](https://x.ai/changelog/bot#v0.77.0)
- [Grok Bot docs: Vault and secure sign-in (payments)](https://docs.x.ai/grok-bot/vault)
- [Official approvals and privacy guide](https://docs.x.ai/grok-bot/approvals-security-and-privacy)
- [Shared computer model](https://docs.x.ai/grok-bot/overview)
- [Cursor help: how-tos (Custom Rules, approval expiry)](https://cursor.com/help/grok-bot/how-to)
- [Cursor help: Shared Bots (approvals)](https://cursor.com/help/grok-bot/shared-bots)
- [Cursor help: store secrets securely (Vault)](https://cursor.com/help/grok-bot/secrets)
- [Cursor help: give your Bot an email address (who must approve a send)](https://cursor.com/help/grok-bot/agent-email)
- [Grok Bot changelog](https://x.ai/changelog/bot)
- [Grok Bot changelog: 0.71.2 (Stop ends subagents, October 14)](https://x.ai/changelog/bot#v0.71.2)
- [Grok Bot changelog: 0.75.2 (approval card flags, passwords shared in chat, October 22)](https://x.ai/changelog/bot#v0.75.2)
- [Grok Bot changelog: 0.75.5 (Vault, fewer approval cards, October 23)](https://x.ai/changelog/bot#v0.75.5)
- [Forum: password filled by the Secure Form shown in a page snapshot (staff reply, October 5)](https://forum.cursor.com/t/grok-bot-browser-snapshot-shows-a-password-filled-by-the-secure-form-requestuserform-in-plain-text/173748)

---

# How to tell whether a Grok Bot workflow actually works

> Use varied examples, a small scorecard, and review-time measurements before calling a workflow reliable or claiming time saved.

- Canonical page: https://www.grokbotwiki.com/guides/evaluate-a-workflow
- Sources checked: 2026-10-29
- Evidence: Official files and results and skills and routines docs, Cursor's routines and how-to help, and SpaceXSI's October 20 incident-sweep post rechecked October 29, 2026; the Grok Bot changelog (through 0.75.5, read October 25) refused our automated check on October 29 · the IncidentSweep example is SpaceXSI's own account, not verified by us; the scorecard is an original editorial framework, not a measured result. Suggested workflows have not been independently tested.
- Publisher: Grok Bot Wiki, an independent guide not affiliated with SpaceXSI, xAI or X.

## A finished message is not the acceptance test

Official guidance emphasizes reviewable artifacts and testing workflows before automation. The scorecard here is our original evaluation framework. It is not a SpaceXSI benchmark, a certification, or evidence of measured Grok Bot performance.

The skills and routines docs give a short review list for every test run: did the Bot select current inputs, meet the output format, leave an audit trail, stop at the intended approval point, and report failures explicitly? Use it as the floor for the scorecard below.

Sources: https://docs.x.ai/grok-bot/files-and-results, https://docs.x.ai/grok-bot/skills-routines-and-automations

## Build a small set with known answers

Choose examples where a human can establish the expected result. For an action extractor, include notes with clear assignments, ambiguous ownership, and no actions. For a reconciliation, include a correct match, an intentional mismatch, and a missing record.

Keep the inputs and expected outputs before you run the Bot. Otherwise, it is easy to accept a plausible result and redefine success around it. A few cases expose obvious failure modes; they do not measure every situation the workflow might encounter.

1. Write three to five acceptance checks specific to the job.
2. Prepare a normal input, an ambiguous input, an empty input, and an unavailable-source case.
3. Run with safe records and preparation-only permissions.
4. Score each result against the checks before changing the instructions.
5. Revise the method, then retest failed cases and one previously passing case.

## Score usefulness, completeness, and boundaries

For each case, record pass, fail, or not assessable for correctness, completeness, traceability, permission behavior, and usability. Keep the reason beside the score. 'Not assessable' is a useful result when the source cannot establish truth; do not count it as a pass.

Measure your review and correction time separately from machine run time. A report that arrives overnight may still take too long to verify. Compare the human effort with a similar manual task, including setup and maintenance. Publish a time-saving claim only with the measurement method and sample size.

- [ ] Correctness: the result agrees with known source facts.
- [ ] Completeness: expected items are present, including awkward cases.
- [ ] Traceability: another person can locate the supporting evidence.
- [ ] Boundaries: the workflow stays within the authorized actions.
- [ ] Usability: the artifact answers the intended question without major repair.

## Test a bulk action the way SpaceXSI's sweep is built

SpaceXSI's October 20 post describes IncidentSweep, a Grok Bot its support team uses after an incident: an engineer sets which tickets to consider and exclude and the exact message, the Bot sets aside tickets it cannot confidently connect, shows the batch and message for approval, sends in small batches while recording each action, never adds tickets after approval, and stops and reports on failure. Its companion IncidentWatch checks the last 15 minutes of tickets every five minutes and alerts the on-call engineer with the issue, the count and examples. SpaceXSI reports that IncidentSweep cleared 204 tickets in about 10 minutes on September 18 with an engineer approving the batch; that is the vendor's own figure, not a result we measured.

Each of those properties is testable before you trust a bulk action of your own. The cases below are our original test plan for that pattern, not SpaceXSI's. Run them on safe or synthetic records with the write action replaced by a draft or a test label.

1. Scope: include one record that matches an exclude rule. Pass only if it stays out of the proposed batch.
2. Uncertainty: include a record that only partly matches. Pass only if it lands on the set-aside list with a reason, not in the batch.
3. Frozen batch: after you approve, add a new matching record. Pass only if it is listed for a later decision and not acted on.
4. Exact text: check that every sent or drafted message matches the approved text character for character.
5. Failure: make one action fail, for example with a record ID that no longer exists. Pass only if the run stops and reports what completed, what failed and what was not attempted.
6. Trail: pick three records at random and confirm each has a recorded action, time and result you can trace.

Sources: https://x.ai/news/incident-sweep

## Ask for a review packet

Let the Bot help assemble evidence, while retaining an independent human check of the outcome.

Editorial template (replace placeholders and review access before running):

```text
For this workflow run, return a review packet containing the exact input scope, source links or record IDs, the final artifact, checks performed, unresolved uncertainties, and any actions taken. Compare the output with these acceptance criteria: [criteria]. Mark criteria that cannot be assessed rather than assuming success. Do not claim time saved or production reliability. Include enough detail for me to verify a sample independently.
```

## Retest the change that matters

When a website, source format, connector, or instruction changes, rerun the cases that depend on it; the docs make the same recommendation for routines. Keep the previous accepted result for comparison. Promote a workflow gradually: useful draft, repeatable draft, supervised action, then only the specific unattended behavior you have chosen to authorize. The [research and review team recipe](https://www.grokbotwiki.com/workflows/research-review-team) applies this to a two-Bot setup, with a deliberately flawed answer to catch.

Sources: https://docs.x.ai/grok-bot/skills-routines-and-automations

## Evaluate a routine, not just a run

A workflow that passes in chat can still fail on a schedule. Test performs real work and spends usage, so run it with safe inputs and keep write actions behind approval. A new routine does not run when created; it waits for its next scheduled time, so check the first unattended run as carefully as the test.

Keep your own record of accepted outputs. The docs say each routine keeps only its 20 most recent run records, and the phone app's Run history shows Running, Succeeded or Failed, not whether the result was right. For webhook triggers, Cursor's help notes that a 200 response means the run started, not that it finished.

Count an expired approval as a failed run, not a pass. Approvals raised by routines, triggers or other Bots expire after about 30 minutes, according to Cursor's how-to help and the official docs checked October 29, and the action does not run, so an unattended run can end quietly incomplete. Record weekly usage before and after a few runs as well: frequent schedules and busy Slack triggers can use a large share of the allowance.

Count rate-limited and signed-out runs too. Cursor's routines help says routines can run up to 300 times an hour in total and each routine up to 200 times, and a run past either limit fails with "Automation run rate limit exceeded"; a five-minute check like IncidentWatch uses 12 runs an hour. Since 0.71.2 a routine that needs to sign in to a site asks you in chat at that step, and since 0.75.2 a routine that hits a signed-out connector shows a Reconnect card at most once a day. Either way the run did not finish its job, so score it as a failure. Since 0.75.5, sends on routine turns still wait as drafts, so an unattended run that ends in a pending draft has not delivered anything yet.

Sources: https://docs.x.ai/grok-bot/skills-routines-and-automations, https://cursor.com/help/grok-bot/routines, https://cursor.com/help/grok-bot/how-to, https://x.ai/changelog/bot

## Sources

- [Official files and results guide](https://docs.x.ai/grok-bot/files-and-results)
- [Official skills and routines guide](https://docs.x.ai/grok-bot/skills-routines-and-automations)
- [Cursor help: Grok Bot routines](https://cursor.com/help/grok-bot/routines)
- [Cursor help: how-tos (approval expiry)](https://cursor.com/help/grok-bot/how-to)
- [Grok Bot changelog (0.71.2, 0.75.2 and 0.75.5)](https://x.ai/changelog/bot)
- [SpaceXSI: Using Grok Bot to detect and respond to incidents (October 20, 2026)](https://x.ai/news/incident-sweep)

---

# Is Grok Bot down? Live status and every recent outage

> Live Grok Bot status from status.x.ai, where Cursor's status page moved in October, every incident since September with UTC times, and how to tell an outage from a problem on your account.

- Canonical page: https://www.grokbotwiki.com/guides/is-grok-bot-down
- Sources checked: 2026-11-01
- Evidence: Live status read from status.x.ai, where Cursor's status page moved on October 26, 2026 (status.cursor.com now redirects there; checked October 27) · incident history through November 1 and the status.x.ai incidents API checked November 1 · official troubleshooting (last updated by Cursor October 22) checked October 25 · Grok Bot changelog through 0.77.0 read October 28 · forum reports attributed, not reproduced. Suggested workflows have not been independently tested.
- Publisher: Grok Bot Wiki, an independent guide not affiliated with SpaceXSI, xAI or X.

## Is Grok Bot down right now?

The panel at the top of this page reads status.x.ai, where Cursor's status page moved on October 26 and which lists Grok Bot as its own component, and refreshes every minute while the page is open. If the Grok Bot component shows an incident, wait rather than reset anything. If it shows operational and only your account is affected, the likely cause is your account's shared computer or a Bot waiting on you, and the official recovery steps apply.

A green panel only means no incident has been declared. It says nothing about your account, and a declared incident can trail the first forum reports by hours.

Cursor's October 19 notice said that from October 26, 2026 its status updates would be published on status.x.ai, that status.cursor.com would stop sending notifications, and that incidents from the last 90 days could be found on status.x.ai. When we checked on October 27 the move was complete: every status.cursor.com address, including old incident links and the notice itself, redirected to status.x.ai, which lists Grok Bot and cursor.com as components and shows Cursor's incident history back to September. The incident links in this guide now open the status.x.ai history page.

Grok Bot signs in with your Cursor account, and the docs say the computers Bots work on run in Cursor's cloud. That is why the two components worth watching are Grok Bot, for the Bots and their computer, and cursor.com, for sign-in.

Sources: https://status.x.ai, https://status.x.ai/history?incident=grok-bot%2Fhnh7j4gwv771, https://docs.x.ai/grok-bot/overview, https://docs.x.ai/grok-bot/troubleshooting

## Where to check, in order

Declared incidents and user reports do not always arrive together. On September 16 the first post in the main unresponsive-Bots forum thread went up at 11:06 UTC and a Cursor staff member replied at 11:23 that they were investigating; the Grok Bot incident on the status page opened at 14:27 UTC. On a bad day, check the forum as well as the status page.

| Source | What it covers | When to use it |
| --- | --- | --- |
| Status page (status.x.ai) | Declared incidents for Grok Bot, cursor.com sign-in, Cloud Agents, Automations, the IDE and the CLI, alongside Grok on web, iOS, Android and X, the API and the console; Cursor's status page moved here on October 26 | First, every time |
| Status history (status.x.ai/history) | Past incidents with start and resolve times, including Cursor's incidents from before the move | To match a bad evening against a past incident |
| Status RSS feed (status.x.ai/feed.xml) | Every declared incident, including other products; Grok Bot items are prefixed [Grok Bot] | To be notified; Slack users can add it with /feed subscribe |
| Cursor forum, grok-bot tag | User reports and Cursor staff replies | When the status page is green but many people report the same symptom in the same hour |

Sources: https://status.x.ai, https://status.x.ai/history, https://status.x.ai/feed.xml, https://status.x.ai/history?incident=grok-bot%2Fhnh7j4gwv771, https://forum.cursor.com/tag/grok-bot, https://forum.cursor.com/t/some-of-the-bots-became-unresponsive-failed-to-send-on-my-messages-to-them/171858, https://status.x.ai/history?incident=grok-bot%2F37hs7jj05wkx

## Latest Grok Bot incidents (updated automatically)

This table is read from the incident history on status.x.ai, which now also holds Cursor's older status history, and refreshed every few minutes. It lists every incident from the last 30 days that named Grok Bot or cursor.com sign-in as affected, newest first, with times in UTC. The summaries below put the bigger ones in context.

Live incident history: https://www.grokbotwiki.com/guides/is-grok-bot-down (refreshed from status.x.ai, where Cursor's status page moved on October 26, 2026).

Sources: https://status.x.ai/history, https://status.x.ai

## What happened in October 2026

October has been the busiest month so far. On October 3 Bots stopped answering in the early hours US Eastern time; a Cursor staff member wrote that the fix landed at about 3:10 AM ET, that messages sent while it lasted were not retried automatically, and that routines due between about 2:00 and 3:10 AM ET that day did not run. On October 6 a degradation affecting Cloud Agents and Grok Bot opened at 19:27 UTC, Grok Bot was marked restored at 21:25 UTC, and a second Cloud Agents incident listing Grok Bot followed. On October 7 Grok Bot's computers in certain regions were degraded for about an hour and a half.

October 8 brought several problems at once. Early in the day (UTC) every Bot on some accounts answered Bot failed to respond; staff said it was a temporary issue on their side and resolved by about 09:55 UTC. From about 13:30 UTC some Bots could not reach their model because of a capacity limit, which staff said cleared at about 21:00 UTC; the status page listed Grok Bot in two incidents about errors and rate limiting on a model used across Cursor. Replies also failed for some users in one region, including Hong Kong, until a fix that evening. Scheduled routines were held back, ran late or were marked Failed from about 10 AM ET on October 8 into October 9, with no status entry; staff said the resolved notice on the status page that evening referred to a different issue, and that missed runs would not be replayed. On October 9 from 22:37 to 23:09 UTC some new Cloud Agents and Grok Bot sessions failed to start.

Not every problem gets a status entry. Cursor staff confirmed in the forum that since October 1 some Grok Bot computers can only make outbound HTTPS connections, so mail, database, SSH and FTP connections time out; they called it unintended and said resetting does not help. More accounts reported it after service-side computer refreshes on October 7 and 8, new reports were still arriving on October 14, and Cursor had not posted a fix in the thread by then.

A wider incident followed in the early hours of October 13 (UTC): the status page reported errors or failed requests across the IDE, Cloud Agents, Automations, Grok Bot and Origin starting at 00:22. Cursor said a fix was implemented by 00:53, that Grok Bot specifically had recovered and was operating normally by 01:49, and marked the whole incident resolved at 03:07 once Cloud Agents, which lagged behind the other services, caught up.

Routines failed twice more later on October 13. A Cursor staff member wrote in the forum that scheduled routines were held back again for a few hours that morning (US time) and had been going through since about 16:00 UTC, and that missed runs would not be replayed. Separately, Cursor posted a status notice after the fact: between 10:52 AM and 1:29 PM PT (17:52 to 20:29 UTC), many routines started by webhooks, Slack, git, email and Linear events did not run. Webhook callers may have seen an HTTP 400 error reading Automation run rate limit exceeded, while other triggers failed without an error. Cursor said users' own usage did not cause it and that events sent in that window were not processed and will not be retried, so resend anything important. That notice was published already resolved and lists no affected component.

The second half of the month has been quieter but not clean. On October 14 from 15:46 to 21:04 UTC Cursor reported a Grok Bot degradation that stopped some users reaching their computers, and said at 20:08 that it had identified the cause. On October 19 Grok Bot routines were delayed for about an hour (16:15 to 17:21 UTC), and shortly afterwards Grok Bot and grok.com showed errors about billing, plans and usage for 19 minutes. On October 21 errors on billing dashboards, usage and plan changes listed both cursor.com and Grok Bot for almost two hours, with a fix in place after about ten minutes. The largest was a major outage from 23:39 UTC on October 23 to 00:20 UTC on October 24, when Grok models were unavailable across Grok Bot, cursor.com, the IDE, the CLI, Cloud Agents and Automations; Cursor said a fix was implemented at 23:50. The first Grok Bot incident on the new status.x.ai page followed on October 27: from 20:33 to 20:43 UTC some Grok Bot responses were delayed, marked major with only Grok Bot listed, and Cursor said responses were back to normal when it closed the incident ten minutes later. A larger one followed on October 28: from 21:15 to 23:13 UTC Cursor reported failures across Cloud Agents, Grok Bot and Origin, then Automations and BugBot as well, marked major; it said a fix was in place at 22:06 and services had recovered by 22:40, and closed the incident about half an hour after that. October 29 brought two shorter, minor ones: from 09:01 to 09:18 UTC degraded performance in Cloud Agents and Origin, with Grok Bot among the listed components, where users could see slow responses, timeouts or retried requests; and from 23:44 UTC to 01:20 UTC on October 30 a degradation in Auto Review, with only Grok Bot listed, so approvals that Auto Review normally checks may have stalled or behaved oddly in that window. Another minor one followed on October 31: from 06:04 to 06:47 UTC Cursor reported multiple services degraded, listing Grok Bot, Cloud Agents, Automations and cursor.com, and closed it as resolved without posting a cause.

Grok Bot 0.71.2 (October 14) changed how some of these moments look in the app: while the Bot's computer is asleep it now says Your computer is asleep instead of Couldn't refresh or a connection error, a working Bot reconnects to the new computer when its computer updates, and a computer that fails to wake is reported as one that couldn't start rather than one still starting. If you are on an older version, update before deciding an error is an outage.

| Date (UTC) | What the status page said | Duration |
| --- | --- | --- |
| October 3, 06:50 to 07:26 | Degradation affecting Grok Bot and Review Agents | About 35 minutes |
| October 6, 19:27 to 22:06 | Degradation affecting some Cloud Agents and Grok Bot features; Grok Bot marked restored at 21:25 | About 2 hours for Grok Bot |
| October 6, 22:48 to 23:04 | Cloud Agents degradation, with Grok Bot listed as affected | 16 minutes |
| October 7, 15:59 to 17:25 | Degradation affecting Grok Bot's computers in certain regions | About 1.5 hours |
| October 8, 13:54 to 15:31 | Rate limiting (429 errors) on a model used across Cursor, with Grok Bot listed | About 1.5 hours |
| October 8, 19:52 to 20:51 | Elevated errors on the same model, with Grok Bot listed | About 1 hour |
| October 9, 22:37 to 23:09 | Some new Cloud Agents and Grok Bot sessions may fail to start | About 30 minutes |
| October 13, 00:22 to 03:07 | Widespread errors across the IDE, Cloud Agents, Automations, Grok Bot and Origin; Grok Bot itself recovered by 01:49 | About 2.75 hours overall, about 1.5 hours for Grok Bot |
| October 13, 17:52 to 20:29 | Many Grok Bot routines started by webhooks, Slack, git, email and Linear events did not run; posted after it ended, with no component listed | About 2.5 hours |
| October 14, 15:46 to 21:04 | Grok Bot degradation preventing some users from reaching their computers; cause identified at 20:08 | About 5.25 hours |
| October 19, 16:15 to 17:21 | Grok Bot degradation where routines may be delayed | About 1 hour |
| October 19, 18:09 to 18:28 | Grok Bot and grok.com errors related to billing, plans and usage | 19 minutes |
| October 21, 15:46 to 17:40 | Billing dashboard errors on billing, usage and plan changes, with cursor.com and Grok Bot listed; fix in place at 15:56 | About 2 hours |
| October 23 to 24, 23:39 to 00:20 | Outage: Grok models unavailable, with Grok Bot, cursor.com, the IDE, the CLI, Cloud Agents and Automations listed (marked major) | About 40 minutes |
| October 27, 20:33 to 20:43 | Delayed responses in Grok Bot, with only Grok Bot listed (marked major); the first incident posted on status.x.ai after the move | 10 minutes |
| October 28, 21:15 to 23:13 | Multiple services degraded: failures across Cloud Agents, Grok Bot and Origin, then also Automations and BugBot (marked major); a fix was in place at 22:06 and services had recovered by 22:40 | About 2 hours |
| October 29, 09:01 to 09:18 | Degraded performance in Cloud Agents and Origin, with Grok Bot, Automations, BugBot and Review Agents listed: slow responses, timeouts or retried requests | 17 minutes |
| October 29 to 30, 23:44 to 01:20 | Auto Review degradation, with only Grok Bot listed | About 1.5 hours |
| October 31, 06:04 to 06:47 | Multiple services degraded, with Grok Bot, Cloud Agents, Automations and cursor.com listed (marked minor) | About 45 minutes |
| November 1, from 05:38 | Degradation affecting the billing and usage dashboard, with cursor.com and the Enterprise Dashboard listed but not Grok Bot (marked minor); forum users tied it to Grok Bot weekly usage meters that jumped the same morning | Still being investigated at 08:44 |

Sources: https://status.x.ai/history?incident=grok-bot%2Fps_45622ec185897742, https://status.x.ai/history?incident=automations%2Fps_d25569b21cabd283, https://status.x.ai/history?incident=automations%2Fps_95a4f0b2be913452, https://status.x.ai/history?incident=grok-bot%2Fps_e5eb22a9954466c4, https://status.x.ai/history?incident=automations%2Fps_061cf14060aff263, https://status.x.ai/history?incident=cursor-com%2Fps_838fe2a3a154acfa, https://forum.cursor.com/t/grok-bot-weekly-usage-meter-flips-between-77-and-100-in-real-time/176909, https://status.x.ai/history?incident=grok-bot%2Ftjs10pzx9qxg, https://forum.cursor.com/t/grok-bots-failing-to-respond-again/173658, https://status.x.ai/history?incident=cloud-agents%2Fbccntkmymws0, https://status.x.ai/history?incident=cloud-agents%2Flft9b2dfmfsy, https://forum.cursor.com/t/grok-bot-failed-to-respond-on-every-bot-after-reset-recover-computer/173919, https://status.x.ai/history?incident=grok-bot%2Fp7fmcg2j968f, https://status.x.ai/history?incident=automations%2Fx4mnlflpqc4w, https://status.x.ai/history?incident=automations%2F25l5bm6rdrb6, https://forum.cursor.com/t/grok-bot-0-68-1-bot-failed-to-respond-after-reset-sends-get-requestid-but-no-assistant-reply/174090, https://forum.cursor.com/t/all-grok-bot-routines-failed-to-run/174125, https://status.x.ai/history?incident=cloud-agents%2Fgh45ycs0zs0g, https://forum.cursor.com/t/grok-bot-computer-all-outbound-non-https-traffic-blocked-since-oct-1-mysql-ssh-imap-smtp-ftp-time-out/173504, https://status.x.ai/history?incident=automations%2F8nlyd6t95xjm, https://status.x.ai/history?incident=grok-bot%2Fbg1b759jsjqf, https://status.x.ai/history?incident=grok-bot%2F6y0yq43mvwg2, https://status.x.ai/history?incident=grok-bot%2F48bg6xqptq72, https://status.x.ai/history?incident=grok-bot%2Fc30f94k6rtrp, https://status.x.ai/history?incident=cursor-com%2Fqy67qt0s4n18, https://status.x.ai/history?incident=automations%2Fz1rz4fcd48j6, https://x.ai/changelog/bot#v0.71.2

## Grok Bot incidents in September 2026

These are the incidents on Cursor's status page (now redirected to status.x.ai) in September that listed Grok Bot as affected, plus one cursor.com sign-in incident. Times are UTC, from when Cursor opened each incident to when it marked it resolved. The history also shows Grok Bot incidents on August 18, when connectors hung, and August 27.

In the forum, a Cursor staff member wrote on September 17 that services should be back after about 24 hours of disruption, although two more Grok Bot incidents followed on September 18. Staff closed the main thread on September 21, saying things were stable, and asked people to open a new thread for fresh reports. Five shorter incidents followed between September 25 and 29. [Our not-responding guide](https://www.grokbotwiki.com/guides/grok-bot-not-responding) describes what those days looked like from the user side.

| Date (UTC) | What the status page said | Duration |
| --- | --- | --- |
| September 3, 13:41 to 17:07 | Degradation affecting all Grok models, Automations, Cloud Agents, Grok Bot and Review Agents (marked critical) | About 3.5 hours |
| September 3 to 4, 23:42 to 00:42 | Degraded performance for Grok Bot routine triggers; some trigger fires may be dropped | 1 hour |
| September 7, 20:32 to 21:37 | Some users unable to reach their Grok Bot computer; Recover or Reset may fail; data not affected | About 1 hour |
| September 15, 21:26 to 22:00 | Degradation across Cursor components, including Grok Bot | About 35 minutes |
| September 16, 14:27 to 20:57 | Grok Bot degradation: degraded performance or bots that don't respond | About 6.5 hours |
| September 17, 12:30 to 14:34 | The same Grok Bot degradation | About 2 hours |
| September 17, 15:20 to 20:04 | Cloud Agents and Automations degradation, with Grok Bot listed as affected | About 4.75 hours |
| September 18, 11:37 to 14:33 | Grok Bot degradation: degraded performance or bots that don't respond | About 3 hours |
| September 18, 17:19 to 23:02 | Grok Bot service degradation | About 5.75 hours |
| September 18, 23:02 to 23:13 | Sign-in and dashboard errors on cursor.com; existing sessions kept working | 11 minutes |
| September 25, 05:17 to 06:51 | Grok Bot computers could temporarily not be created, reached, or reset | About 1.5 hours |
| September 25 to 26, 23:47 to 00:32 | Grok Bot service degradation | About 45 minutes |
| September 28, 20:23 to 20:36 | Grok Bot service degradation | 13 minutes |
| September 29, 14:25 to 18:05 | Degradation affecting Cloud Agents and Grok Bot | About 3.75 hours |
| September 29, 19:43 to 20:18 | Degradation affecting xAI models: errors, slow responses or rate limiting, with Grok Bot listed | About 35 minutes |

Sources: https://status.x.ai/history, https://status.x.ai/history?incident=grok-bot%2Fdj4cgfmwgm65, https://status.x.ai/history?incident=grok-bot%2Fkt27kgrd7pf1, https://status.x.ai/history?incident=grok-bot%2Fjw6mzctqkq56, https://status.x.ai/history?incident=automations%2F2bw21tcjqzg6, https://status.x.ai/history?incident=grok-bot%2F37hs7jj05wkx, https://status.x.ai/history?incident=grok-bot%2Flqp75t47dvpm, https://status.x.ai/history?incident=automations%2Fjdm0j510q78b, https://status.x.ai/history?incident=grok-bot%2F3slwgs0612sc, https://status.x.ai/history?incident=grok-bot%2F14xbn0wxbpdb, https://status.x.ai/history?incident=cursor-com%2Fr44l5qk34kj1, https://status.x.ai/history?incident=grok-bot%2Fn540z31sbqp6, https://status.x.ai/history?incident=grok-bot%2Fbfcck6qks18q, https://status.x.ai/history?incident=grok-bot%2Fx2g19tzq27sg, https://status.x.ai/history?incident=cloud-agents%2Fjb59kzth2pwf, https://status.x.ai/history?incident=cloud-agents%2Fdk1g1h4q8yf8, https://forum.cursor.com/t/some-of-the-bots-became-unresponsive-failed-to-send-on-my-messages-to-them/171858

## An outage, or just your account?

Every Bot on an account shares one cloud computer, so a problem with that computer looks like an outage: all your Bots stop together. The difference is whether other people are affected at the same time. Use the status page and the forum to answer that before you change anything.

| What you see | Most likely | What to do |
| --- | --- | --- |
| Several Bots stop at once and the status page shows a Grok Bot incident | A service outage | Wait; do not Reset. Note the time and your app version |
| Every Bot stops but the status page is green and the forum is quiet | Your account's shared computer is stuck or unreachable | Retry, restart the app, Recover computer, then Update Bot's Computer in Settings → Computer; Reset only last |
| The app says Your computer is asleep (older versions showed Couldn't refresh or a connection error) | An idle computer, not an outage; 0.71.2 replaced the misleading messages with this one | On 0.71.2 or later, click the Computer is asleep preview to wake it in place (it replaced the separate Wake button); switching chats does not wake it |
| "Blocked by a safety check" with "Try a different message" | A safety check blocked that Bot's reply, not an outage; 0.71.2 shows this instead of a generic error | Rephrase, or start the work with another Bot; see [the not-responding guide](https://www.grokbotwiki.com/guides/grok-bot-not-responding) |
| One Bot is silent while others reply | That Bot is waiting on a question, approval, login, CAPTCHA or secret request | Open the computer view, answer it, or send a short redirect or "Stop now" |
| Bots stop after a busy week, or show a usage message | Weekly usage is used up or the on-demand spending limit is reached | Check Usage & Billing; see [our weekly usage limit guide](https://www.grokbotwiki.com/guides/grok-bot-weekly-usage-limit) |
| Sign-in never completes | A cursor.com sign-in incident, an SSO step, or Legacy Privacy Mode | Check the cursor.com component, then [the sign-in checks](https://www.grokbotwiki.com/guides/grok-bot-sign-in-error-windows) |
| A scheduled routine did not run | A routine-trigger incident, or a disabled or misconfigured routine | Compare the time with the status history, then run [the routine checklist](https://www.grokbotwiki.com/guides/grok-bot-routines-not-running) |
| Bots are missing, or the app says your plan has no Grok Bot, after switching plans | An account split during the switch to The X Subscription, not an outage (Cursor staff, October 21) | Do not reset, delete or buy a second plan; follow [the account-switch steps](https://www.grokbotwiki.com/guides/grok-bot-sign-in-error-windows) |
| Grok on grok.com or in X is failing too | A wider xAI problem | Check status.x.ai as well |

Sources: https://docs.x.ai/grok-bot/troubleshooting, https://docs.x.ai/grok-bot/faq, https://status.x.ai, https://x.ai/changelog/bot, https://x.ai/changelog/bot#v0.71.2, https://forum.cursor.com/t/all-my-grok-bot-disappear/175510

## What to do during an outage

The goal is to avoid making things worse. User-side recovery rarely helps during a declared incident, and the one destructive option, Reset, can discard recent work.

1. Leave running work alone. Bot work runs on the cloud computer, and the FAQ says closing the app, laptop or phone does not stop a background turn or routine.
2. Do not use Reset. It restores the last saved snapshot and can lose recent or unsynced work, and during the September 7 incident Cursor said Recover or Reset might fail anyway.
3. Subscribe to status updates so you know when the incident is marked resolved: from October 26 Cursor publishes them on status.x.ai (RSS at status.x.ai/feed.xml), and status.cursor.com stops sending notifications.
4. Once it is resolved, open each Bot, read its last message, and resend anything that did not go through; Cursor staff said messages sent during the October 3 incident were not retried automatically.
5. Check routines that were due during the incident window and run missed ones by hand, for example by asking the Bot to run them; the September 3 to 4 incident dropped some routine trigger fires, routines due during the October 3 incident did not run, runs missed on October 8 and 13 were not replayed, webhook, Slack, git, email and Linear events sent during the October 13 routine-trigger incident must be sent again, and routines were delayed on October 19.
6. If Bots still do not respond after the incident is resolved, treat it as your computer and follow the recovery order in [our not-responding guide](https://www.grokbotwiki.com/guides/grok-bot-not-responding).

- [ ] Before contacting support, collect your Grok Bot version and operating system.
- [ ] Copy the exact error message and the Bot or routine name.
- [ ] Note the approximate time and your time zone, and any request or conversation ID shown.
- [ ] Record whether Retry, an app restart, or updating Grok Bot's computer changed anything.
- [ ] Leave out passwords, one-time codes, private keys and secret values.

Sources: https://docs.x.ai/grok-bot/faq, https://docs.x.ai/grok-bot/troubleshooting, https://status.x.ai/history?incident=grok-bot%2Fjw6mzctqkq56, https://status.x.ai/history?incident=grok-bot%2Fkt27kgrd7pf1, https://status.x.ai/feed.xml, https://status.x.ai/history?incident=grok-bot%2Fhnh7j4gwv771, https://forum.cursor.com/t/all-grok-bot-routines-failed-to-run/174125, https://status.x.ai/history?incident=grok-bot%2Fbg1b759jsjqf, https://status.x.ai/history?incident=grok-bot%2F48bg6xqptq72

## Quick answers

### Is there an official Grok Bot status page?

Yes, on status.x.ai. Cursor's October 19 notice said that from October 26, 2026 its status updates would be published there, and that has happened: status.x.ai now lists Grok Bot as its own component next to cursor.com, Cloud Agents, Automations, the IDE and the CLI, alongside the Grok apps, the API and the console, its history page carries Cursor's past incidents back to September, and the panel at the top of this page reads it live. When we checked on October 27, every status.cursor.com address, including old incident links, redirected to status.x.ai, so links in this guide now point there.

### Why is the status page green when my Bots are not responding?

Two reasons. The status page reports incidents Cursor has declared, not the state of your account, and every Bot on an account shares one cloud computer, so a stuck computer stops them all at once without affecting anyone else. And declared incidents can lag or never appear: on September 16 the first forum report came about three hours before the Grok Bot incident was opened, and the October 8 routine failures had no status entry at all. Check the forum's grok-bot tag, then follow the official recovery order.

### Do I need to reset my computer after an outage?

Usually not. After the October 3, 6 and 8 incidents, Cursor staff said the fix was on their side, that no reset or reinstall was needed, and that any message still showing Bot failed to respond should simply be sent again. Messages sent during the October 3 incident were not retried automatically, and routines missed on October 3, October 8 and October 13 were not replayed, so run those by hand; events sent to event-triggered routines during the October 13 incident were not processed, so resend them. Routines were also delayed for about an hour on October 19, so check any that were due then. Reset restores the last saved snapshot and can lose recent work.

### Will I lose my Bots or files during an outage?

Not from the outage itself, going by what Cursor has published. The September 7 status notice said data was not affected, and the troubleshooting page says Bot profiles and saved conversations are not necessarily lost when the computer is temporarily unreachable. The risk is Reset: it restores the last saved snapshot and can lose recent or unsynced work, so leave it until last.

### How do I get notified when Grok Bot is down?

Move your subscription to status.x.ai. Cursor's October 19 notice says that from October 26 status.cursor.com stops sending notifications. Email subscriptions move over automatically, with mail sent from status@email.api.x.ai; the RSS feed to use is status.x.ai/feed.xml, which Slack users can add with /feed subscribe; and SMS, Microsoft Teams and webhook notifications stop on October 26, so re-subscribe by email or RSS. The feeds carry every declared incident, including ones for other products, so filter for Grok Bot and cursor.com if you only care about sign-in and Bots.

## Sources

- [SpaceXSI status page (Cursor's status page since October 26; Grok Bot and cursor.com components)](https://status.x.ai)
- [Status history on status.x.ai (Cursor's incidents back to September)](https://status.x.ai/history)
- [Status RSS feed (status.x.ai/feed.xml; Grok Bot items are prefixed [Grok Bot])](https://status.x.ai/feed.xml)
- [Status: billing and usage dashboard degradation, cursor.com and Enterprise Dashboard, November 1](https://status.x.ai/history?incident=cursor-com%2Fps_838fe2a3a154acfa)
- [Forum: Grok Bot weekly usage meters jump on November 1 (user reports)](https://forum.cursor.com/t/grok-bot-weekly-usage-meter-flips-between-77-and-100-in-real-time/176909)
- [Status: multiple services degraded, including Grok Bot, October 31](https://status.x.ai/history?incident=automations%2Fps_061cf14060aff263)
- [Status: Auto Review degradation in Grok Bot, October 29 to 30](https://status.x.ai/history?incident=grok-bot%2Fps_e5eb22a9954466c4)
- [Status: degraded performance in Cloud Agents and Origin, listing Grok Bot, October 29](https://status.x.ai/history?incident=automations%2Fps_95a4f0b2be913452)
- [Status: multiple services degraded, including Grok Bot, October 28](https://status.x.ai/history?incident=automations%2Fps_d25569b21cabd283)
- [Cursor status notice: status updates move to status.x.ai from October 26 (posted October 19)](https://status.x.ai/history?incident=grok-bot%2Fhnh7j4gwv771)
- [Status: delayed responses in Grok Bot, October 27](https://status.x.ai/history?incident=grok-bot%2Fps_45622ec185897742)
- [Cursor status: outage, Grok models unavailable, October 23 to 24](https://status.x.ai/history?incident=automations%2Fz1rz4fcd48j6)
- [Cursor status: billing, usage and plan-change errors, October 21](https://status.x.ai/history?incident=cursor-com%2Fqy67qt0s4n18)
- [Cursor status: Grok Bot billing, plans and usage errors, October 19](https://status.x.ai/history?incident=grok-bot%2Fc30f94k6rtrp)
- [Cursor status: Grok Bot routines delayed, October 19](https://status.x.ai/history?incident=grok-bot%2F48bg6xqptq72)
- [Cursor status: some users unable to reach their computers, October 14](https://status.x.ai/history?incident=grok-bot%2F6y0yq43mvwg2)
- [Cursor status: Grok Bot routines not triggering, October 13](https://status.x.ai/history?incident=grok-bot%2Fbg1b759jsjqf)
- [Cursor status: widespread degradation across the IDE, Cloud Agents, Automations, Grok Bot and Origin, October 13](https://status.x.ai/history?incident=automations%2F8nlyd6t95xjm)
- [Cursor status: degradation across Grok models and Grok Bot, September 3](https://status.x.ai/history?incident=grok-bot%2Fdj4cgfmwgm65)
- [Cursor status: routine trigger fires dropped, September 3 to 4](https://status.x.ai/history?incident=grok-bot%2Fkt27kgrd7pf1)
- [Cursor status: Grok Bot computers unreachable, September 7](https://status.x.ai/history?incident=grok-bot%2Fjw6mzctqkq56)
- [Cursor status: service degradation including Grok Bot, September 15](https://status.x.ai/history?incident=automations%2F2bw21tcjqzg6)
- [Cursor status: Grok Bot degradation, September 16](https://status.x.ai/history?incident=grok-bot%2F37hs7jj05wkx)
- [Cursor status: Grok Bot degradation, September 17](https://status.x.ai/history?incident=grok-bot%2Flqp75t47dvpm)
- [Cursor status: Cloud Agents and Automations degradation, September 17](https://status.x.ai/history?incident=automations%2Fjdm0j510q78b)
- [Cursor status: Grok Bot degradation, September 18 (morning UTC)](https://status.x.ai/history?incident=grok-bot%2F3slwgs0612sc)
- [Cursor status: Grok Bot degradation, September 18 (evening UTC)](https://status.x.ai/history?incident=grok-bot%2F14xbn0wxbpdb)
- [Cursor status: sign-in and dashboard errors, September 18](https://status.x.ai/history?incident=cursor-com%2Fr44l5qk34kj1)
- [Cursor status: computers could not be created, reached or reset, September 25](https://status.x.ai/history?incident=grok-bot%2Fn540z31sbqp6)
- [Cursor status: Grok Bot degradation, September 25 to 26](https://status.x.ai/history?incident=grok-bot%2Fbfcck6qks18q)
- [Cursor status: Grok Bot degradation, September 28](https://status.x.ai/history?incident=grok-bot%2Fx2g19tzq27sg)
- [Cursor status: Cloud Agents and Grok Bot degradation, September 29](https://status.x.ai/history?incident=cloud-agents%2Fjb59kzth2pwf)
- [Cursor status: xAI model degradation, September 29](https://status.x.ai/history?incident=cloud-agents%2Fdk1g1h4q8yf8)
- [Cursor status: Grok Bot and Review Agents degradation, October 3](https://status.x.ai/history?incident=grok-bot%2Ftjs10pzx9qxg)
- [Cursor status: Cloud Agents and Grok Bot degradation, October 6](https://status.x.ai/history?incident=cloud-agents%2Fbccntkmymws0)
- [Cursor status: Cloud Agents degradation listing Grok Bot, October 6 (late)](https://status.x.ai/history?incident=cloud-agents%2Flft9b2dfmfsy)
- [Cursor status: computers in certain regions degraded, October 7](https://status.x.ai/history?incident=grok-bot%2Fp7fmcg2j968f)
- [Cursor status: model rate limiting listing Grok Bot, October 8](https://status.x.ai/history?incident=automations%2Fx4mnlflpqc4w)
- [Cursor status: model errors listing Grok Bot, October 8 (evening UTC)](https://status.x.ai/history?incident=automations%2F25l5bm6rdrb6)
- [Cursor status: new Cloud Agents and Grok Bot sessions failing to start, October 9](https://status.x.ai/history?incident=cloud-agents%2Fgh45ycs0zs0g)
- [Forum: Grok Bots failing to respond again (staff reply on the October 3 fix)](https://forum.cursor.com/t/grok-bots-failing-to-respond-again/173658)
- [Forum: Bot failed to respond on every Bot (staff replies, October 6 to 9)](https://forum.cursor.com/t/grok-bot-failed-to-respond-on-every-bot-after-reset-recover-computer/173919)
- [Forum: replies failing for some users in one region (staff fix, October 9)](https://forum.cursor.com/t/grok-bot-0-68-1-bot-failed-to-respond-after-reset-sends-get-requestid-but-no-assistant-reply/174090)
- [Forum: all Grok Bot routines failed to run (staff replies, October 8)](https://forum.cursor.com/t/all-grok-bot-routines-failed-to-run/174125)
- [Forum: outbound non-HTTPS traffic blocked since October 1 (staff reply)](https://forum.cursor.com/t/grok-bot-computer-all-outbound-non-https-traffic-blocked-since-oct-1-mysql-ssh-imap-smtp-ftp-time-out/173504)
- [Cursor forum: grok-bot tag](https://forum.cursor.com/tag/grok-bot)
- [Forum: some Bots became unresponsive (September 16, staff replies)](https://forum.cursor.com/t/some-of-the-bots-became-unresponsive-failed-to-send-on-my-messages-to-them/171858)
- [Official troubleshooting](https://docs.x.ai/grok-bot/troubleshooting)
- [Grok Bot FAQ](https://docs.x.ai/grok-bot/faq)
- [Grok Bot overview](https://docs.x.ai/grok-bot/overview)
- [Grok Bot changelog (Wake button in 0.69.0 to 0.70.2, October 11)](https://x.ai/changelog/bot)
- [Grok Bot changelog 0.71.2 (October 14): asleep and safety-check messages, wake in place](https://x.ai/changelog/bot#v0.71.2)
- [Forum: all my Grok Bots disappeared after the X Subscription switch (staff replies, October 21)](https://forum.cursor.com/t/all-my-grok-bot-disappear/175510)

---

# Grok Bot not responding or 'failed to respond': fixes in order

> Bots gone silent, one Bot that always fails, a computer shown offline. Live status, the official recovery order, the October incidents, and when not to reset.

- Canonical page: https://www.grokbotwiki.com/guides/grok-bot-not-responding
- Sources checked: 2026-10-30
- Evidence: Official troubleshooting rechecked October 25, 2026 (last updated by Cursor October 22) · Grok Bot changelog through 0.78.1 (October 27) read October 29, 2026 · status.x.ai incident history checked October 29 · forum staff replies checked October 30, 2026 · fixes are as described in release notes, not tested by us · forum reports attributed, not reproduced. Suggested workflows have not been independently tested.
- Publisher: Grok Bot Wiki, an independent guide not affiliated with SpaceXSI, xAI or X.

## First, work out which of three things is wrong

A silent Bot has one of three causes: the Bot is waiting on you, the shared computer is unhealthy, or the service is degraded. The symptoms look identical from the chat, so open the computer view before touching anything. The official docs say to check the sidebar and conversation status, watch the computer, and look for a question, approval, login page, CAPTCHA, or secret request the Bot is stuck behind.

The troubleshooting page also flags a fourth, easy-to-miss cause: a Bot can look stuck simply because weekly usage is exhausted and an on-demand spending limit has been reached. Check usage and billing before assuming the computer is unhealthy. Until recently the app could stay completely silent in that case: a Cursor staff member wrote in a September forum thread that a used-up allowance made every message fail before the Bot could reply, with no usage limit reached notice, and on October 30 posted in the same thread (357 views) that this was fixed, so after updating Grok Bot to the latest version you should see a clear message that the limit has been reached. If Bots go silent again without one, staff asked for your Grok Bot version and the time it happened, with your time zone.

If the Bot is waiting, answer it or send a redirect. If the computer view will not load or shows setting up or unreachable, follow the recovery order below. If several Bots died at once and the forum shows a fresh degradation thread, stop and wait.

The panel at the top of this page shows live Grok Bot status from status.x.ai, where Cursor's status page moved on October 26. Our guide [Is Grok Bot down?](https://www.grokbotwiki.com/guides/is-grok-bot-down) keeps every incident since September with its times, so you can tell an outage from a problem on your account.

Sources: https://docs.x.ai/grok-bot/troubleshooting, https://docs.x.ai/grok-bot/overview, https://forum.cursor.com/t/grok-bot-all-bots-completely-unresponsive-after-update-agent-computer-recovery-and-reset/172118

## Update the app first (fixes in 0.71.2 to 0.78.1)

Several symptoms in this guide have official fixes in recent releases, so check Settings → Updates → Check for Updates before any recovery step. The troubleshooting page notes that the app and the Bot's computer update separately, and that updating the desktop app does not reset the cloud computer. These are the fixes as the release notes describe them; we have not tested them, and forum reports show some symptoms still turning up for some accounts.

| Symptom | Fixed in | What the release notes say |
| --- | --- | --- |
| "Couldn't refresh" or connection errors while the Bot's computer sleeps | 0.71.2 (October 14) | The app says Your computer is asleep instead |
| A separate Wake button, or waiting behind a full-window Setting up Grok Bot's computer screen | 0.71.2 | Clicking the Computer is asleep preview wakes it in place, and the app opens while the computer is still starting |
| The Bot keeps retrying as if a computer that failed to wake were still starting | 0.71.2 | The Bot says the computer couldn't start |
| A working Bot drops when its computer updates | 0.71.2 | It reconnects to the new computer and keeps going |
| Your own Mac or PC unreachable after a Wi-Fi, VPN or network change | 0.71.2 | Bots can run tasks on it right away; commands also keep going through brief connection stalls |
| Bots slow to notice that your computer went to sleep | 0.71.2 | A sleeping computer counts as disconnected within two minutes, and Bots say so right away |
| Connector calls failing after one minute | 0.71.2 | They wait up to two minutes, longer while the connector reports progress |
| A generic error when a safety check blocks a reply | 0.71.2 | The chat shows Blocked by a safety check and Try a different message |
| A Bot silent after you hand its computer back with I'm done or Skip | 0.71.2 | The Bot posts its answer |
| The desktop app does not load behind a corporate proxy | 0.75.2 (October 22) | The app connects directly unless you have turned on a system proxy |
| Connect Apps shows Couldn't refresh | 0.75.2 | It waits longer for your plugins |
| A message silently fails to save | 0.75.2 | The app says whether your computer is out of disk space; since 0.71.2 a Bot whose computer runs low on disk also tells you once and names the biggest files |
| Errors after resetting a chat whose first message was blocked | 0.75.5 (October 23) | New messages get replies |
| Your own Mac or PC stays disconnected after the Bot's computer wakes, with Route traffic through this computer on | 0.75.8 (October 24) | For most accounts the connection comes back as soon as the Bot's computer wakes |
| A connector shows Connected while the Bot says it is signed out | 0.75.8 (October 24), on 0.71.2 or later | The app shows Authenticate when a connector's sign-in has expired; sign in again instead of resetting |
| No status line after you send, so a quick reply looks like silence | 0.75.8 (October 24) | A Bot's status line shows up right after you send, even for quick replies |
| A Bot in Slack goes quiet when a safety check blocks its reply | 0.75.8 (October 24) | The Bot says so in Slack and suggests trying a different message |
| Turns end on Couldn't Reach Grok Bot's Computer, especially during heavy work | 0.77.0 (October 26) | The Bot's computer stays up when memory runs low and recovers faster after a crash, so fewer turns end that way |
| A command on the Bot's computer hangs because it is waiting for input, such as a package install prompt | 0.77.0 | Such commands finish instead of hanging |
| A message shows Not delivered yet although the server accepted it, or the computer view stays on Waking up | 0.77.0 | An accepted message stays delivered and Resend sends one that is not; the computer view leaves Waking up once the screen is ready |
| An update interrupts a working Bot, or Usage & Billing goes blank when usage cannot load | 0.77.0 | Grok Bot offers Stop and Update when an update is ready while a Bot is working; Usage & Billing keeps the last reading with Try again |
| With Route traffic through this computer on, plain http pages fail, or the Bot does not say your computer went offline | 0.77.0 | Plain http pages load, and the Bot says when your computer goes offline |
| The computer card flips off Asleep during a brief background wake, or does not show Waking up when you wake it | 0.78.1 (October 27) | The card stays on Asleep during brief background wakes and shows Waking up… as soon as you wake it |
| Update installs a different version than the one you clicked, or stays on Restarting… with no explanation when a restart is refused | 0.78.1 | Update installs the version you clicked, an open Update ready dialog switches to the newest finished download, and when a restart is refused every Update button says why |
| Task lists and thread names stay stale after the app reconnects | 0.78.1 | They refresh after the app reconnects |
| With Route traffic through this computer on, Settings does not say the Bot's computer is asleep, or pages fail as soon as one other host on them is refused | 0.78.1 | Settings says when the Bot's computer is asleep and that routing reconnects when it wakes; pages no longer fail right away when only another host on them is refused |
| Approved browser actions fail on some Bot computers when the page has not changed | 0.78.1 | They no longer fail |
| Reset or Recover restores an older backup when the computer has been refusing saves | 0.78.1 | Reset and Recover keep the current disk instead of restoring an older backup |

Sources: https://x.ai/changelog/bot#v0.71.2, https://x.ai/changelog/bot#v0.75.2, https://x.ai/changelog/bot#v0.75.5, https://x.ai/changelog/bot#v0.75.8, https://x.ai/changelog/bot#v0.77.0, https://x.ai/changelog/bot#v0.78.1, https://docs.x.ai/grok-bot/troubleshooting

## Error messages and what they usually mean

These are messages quoted in the official docs, Cursor's billing page, or forum reports where Cursor staff replied. The cause column is the most common explanation in those sources, not a diagnosis of your account.

| What you see | Likely cause | What to do |
| --- | --- | --- |
| "Bot failed to respond" on one or every Bot | The shared computer is stuck, or the service is degraded; it hits every Bot on the account at once. Since 0.63.0, a used-up plan shows the usage limit notice instead | Check the live status first. After the October 3 and 6 incidents, staff said to resend the message rather than reset; otherwise follow the recovery order below and leave Reset until last |
| "Bot failed to respond" on one Bot only, even after a reset, while other Bots reply | Staff traced October cases to the model provider's safety filter refusing that Bot's conversation history, for example security or biology research content; the app shows a generic error | Use another or a new Bot for new work; do not ask other Bots to read or continue that chat, and do not delete the stuck Bot. On 0.71.2 or later a blocked reply reads Blocked by a safety check |
| Your messages show "Failed to send" | Reported during the September 16 to 18 incidents and after long tool waits | Restart the app, send "Stop now" to the stuck Bot, and check status before resetting |
| Can't reach your computer (unreachable-computer state) | The cloud computer is temporarily unreachable; on September 7 Cursor's status page said Recover or Reset could also fail | Retry, restart, then Recover computer; if that is not offered, Settings → Computer → Update Bot's Computer |
| "Starting your computer" or "Updating your computer" does not finish | Initial setup or an image update, which can take several minutes | Wait while progress changes; if it stops, Retry, restart, check for an app update, then Update Bot's Computer under Settings → Computer |
| "Starting desktop" with "Can't reach Grok Bot's screen", or SEND AFTER RECONNECT on mobile | On October 5 Cursor staff said a recent change left some computers without enough storage to finish starting; they fixed the reported accounts the same day | Fully quit and reopen the app on every device; if it persists, post your version and time in the forum rather than resetting |
| Shell or terminal commands hang while the desktop still renders | A server-side fault Cursor staff were fixing account by account in early October; Update and Reset did not clear it. In an October 21 reply staff also pointed to the computer's shell startup files, since every Shell command starts a login shell first | Hold off on Update, Recover and Reset, since a Reset restores the same files; have a Bot open its startup files with its file reading tool, not Shell, then report what it finds in the forum; the section on Shell commands below has the details |
| Mail, database, SSH or FTP connections from the computer time out | Since October 1 some computers can only make outbound HTTPS connections; staff called it unintended, and more accounts reported it after service-side refreshes on October 7 and 8. New reports were still arriving on October 14 with no fix posted | Use HTTPS endpoints, or clone git repositories over HTTPS; resetting does not help. Users report that connecting by a server's real IPv4 address, looked up over DNS-over-HTTPS, works for most ports, which Cursor has not endorsed. Users were still reporting blocked mail ports on October 22, and no staff reply in the thread since October 14 announced a fix (checked October 25) |
| Can't reach the Bot's screen on a new account, and deleting a Bot or Update does nothing | The computer did not finish its very first startup (staff, October 7); chat still works. On October 12 staff said computers in that group were coming back up, and that one similar case was instead the desktop app connecting through a VPN or proxy route Cursor's servers did not accept between October 10 and 12, while the phone app worked | Fully quit and reopen the app. If you use a VPN or proxy on that computer, try without it. Do not keep pressing Update or Reset; post in the forum thread if it persists |
| The app says Your computer is asleep, or, on versions before 0.71.2, Couldn't refresh or a connection error | An idle computer; since the October 11 release (0.69.0 to 0.70.2) switching chats or focusing the window no longer wakes it, while opening a file does. 0.71.2 replaced the misleading errors with the asleep message | Update to 0.71.2 or later and click the Computer is asleep preview, which wakes it in place and replaced the Wake button; do not Recover or Reset. Publishing, sharing or deleting a Bot works while the computer sleeps, and since 0.71.2 a voice call from your phone also wakes it |
| Your Bots are gone, or the app says your plan does not include Grok Bot, after switching to The X Subscription | Cursor staff said on October 21 that the switch can leave your Bots on one account and your plan on another; the Bots are not deleted. Users were still reporting it on October 25 | Do not reset the Bot's computer, delete anything or buy a second subscription; see [the account-switch steps](https://www.grokbotwiki.com/guides/grok-bot-sign-in-error-windows) |
| The app keeps crashing, or the window is blank after an update | Fixed in the October 11 release: a crash loop now offers to reload or quit, and a blank window after an update relaunches | Choose reload; if you are on an older version, install the latest from x.ai/bot |
| A turn stops and says the model is not available in your region | Since the October 11 release the turn stops with an explanation and Bots fall back to Grok | Send the message again; it is not a computer problem, so do not Recover or Reset |
| "Grok Bot is having trouble connecting", and Recover and Reset fail | On October 8 staff found one such case was an ended trial: the account had no Grok Bot access and the app showed it as a connection error. 0.71.2 says accounts without access now finish setup and see just the access notice | Update the app, then check your plan with the same account: on The X Subscription, Cursor's plans help says Premium, Super and Ultra include Grok Bot and Plus and Free do not. Fully quit and reopen the app afterwards |
| "Reset failed" with a partial-state warning | During the October 8 incidents staff said the bots' errors were on Cursor's side and the partial state would clear on its own | Do not retry the reset; check the live status and the forum first |
| A Bot says your Mac or PC is offline or disconnected when it is on | Since recent desktop versions, the app pauses the local connection when the screen locks, the computer sleeps, or the Grok Bot window is not the active window for about 10 minutes, and it does not resume on its own when a Bot needs it (staff, October 5 to 13). On October 13 staff said they could not confirm that 0.70.2 fixes it. 0.71.2 changed related behaviour: a sleeping computer counts as disconnected within two minutes, and after a Wi-Fi, VPN or network change Bots can reach it right away. Two users wrote that the drops stopped for them, one on 0.70.2 and one from just before 0.72.0; Cursor has not said the window-focus pause was removed | Update first. If it still happens, click into the Grok Bot window on that computer; it reconnects within about a minute. Keep the window in front before scheduled jobs; there is no setting to turn this off. Staff also called a user's workaround, running Tailscale on that machine, valid. Drops while the window stays in front are a separate case staff asked to be reported in its own thread |
| Update stuck at 43 percent on "Transferring your data" | Computers failing to fully rehydrate during recreation (Cursor staff, September 20); a second thread shows the stall recurring past September 21 | Do not reset; post your app version and the time you first saw it in the forum thread and staff will clear the account, sometimes within about 20 minutes |
| "Authentication error. If you are logged in, try logging out and back in." | For most users in the Windows thread, the app stayed signed in but the computer needed an update | Settings → Computer → Update Bot's Computer; see [the sign-in guide](https://www.grokbotwiki.com/guides/grok-bot-sign-in-error-windows) if login itself never completes |
| The screen says you have reached your Grok Bot usage limit | Weekly usage is used up and on-demand is off | Wait for the weekly reset, or turn on on-demand with a monthly limit; see [the usage limit guide](https://www.grokbotwiki.com/guides/grok-bot-weekly-usage-limit) |
| An error mentioning Legacy Privacy Mode | The Cursor account uses a data mode that does not allow Grok Bot's required storage | Change the Cursor data setting, or ask your organization's administrator |

Sources: https://docs.x.ai/grok-bot/troubleshooting, https://status.x.ai/history, https://forum.cursor.com/t/some-of-the-bots-became-unresponsive-failed-to-send-on-my-messages-to-them/171858, https://forum.cursor.com/t/grokbot-unavailable-hung-on-updating-grok-bots-computer-at-43/172401, https://forum.cursor.com/t/grokbot-unavailable-hung-on-updating-grok-bot-s-computer-at-43/172535, https://forum.cursor.com/t/grok-bot-windows-0-44-0-authentication-error-persists-after-update-logout-login-and-cache-clear/171115, https://cursor.com/help/grok-bot/plans, https://cellcog.ai/blog/grok-bot-problems/, https://forum.cursor.com/t/grok-bots-computer-is-stuck-on-starting-desktop-with-cant-reach-grok-bots-screen-attachments-wont-download-and-the-mobile-app-shows-send-after-reconnect-with-no-response/173788, https://forum.cursor.com/t/grok-bot-shared-computer-fully-wedged-since-2026-10-05-shell-dead-update-recover-reset-all-fail-please-reprovision/173881, https://forum.cursor.com/t/grok-bot-computer-all-outbound-non-https-traffic-blocked-since-oct-1-mysql-ssh-imap-smtp-ftp-time-out/173504, https://forum.cursor.com/t/grok-bot-primary-bot-silent-bot-failed-to-respond-since-oct-8-other-bots-ok-restart-this-bots-runner-only-do-not-reset/174138, https://forum.cursor.com/t/grok-bot-restore-existing-agents-that-fail-with-bot-failed-to-respond-since-oct-8-do-not-reset/174246, https://forum.cursor.com/t/grok-bot-bots-error-out-and-stop-responding-whenever-i-ask-for-a-scientific-literature-review-reset-didnt-help/174218, https://forum.cursor.com/t/grok-bot-0-68-1-macos-cant-reach-computer-delete-fails-update-does-nothing/173950, https://forum.cursor.com/t/grok-bot-completely-unusable-recovery-and-reset-both-fail/174022, https://forum.cursor.com/t/grok-bot-0-68-1-reset-failed-computer-stuck-in-partial-state/174099, https://forum.cursor.com/t/grok-bot-0-68-1-macos-mac-shows-disconnected-while-awake-and-in-use-local-computer-doesnt-reconnect-until-app-is-focused/174223, https://forum.cursor.com/t/grok-bot-thinks-my-computer-is-offline-or-sleeping-but-it-is-not/174267, https://forum.cursor.com/t/grok-bot-0-68-1-on-mac-mini-local-computer-drops-while-idle-and-does-not-self-heal/174109, https://x.ai/changelog/bot, https://x.ai/changelog/bot#v0.71.2, https://x.ai/changelog/bot#v0.75.5, https://forum.cursor.com/t/all-my-grok-bot-disappear/175510

## The official recovery order

These steps are from the official troubleshooting page for a computer that cannot be reached. Do them in order and stop as soon as Bots reply again.

One exception comes from Cursor staff rather than the docs: when the live status shows an open incident, or staff are already handling a server-side fault on your account, they have asked people to hold off on Update, Recover and Reset. In October those actions did not clear server-side problems and could make a half-finished recreate worse.

1. Choose Retry, or reopen the conversation.
2. Restart the Grok Bot app, then check for an app update under Settings → Updates → Check for Updates.
3. Choose Recover computer when the unreachable-computer state offers it (the confirmation dialog calls it Recover Grok Bot's Computer) and wait for it to complete.
4. If recovery is not available, open Settings → Computer and, under Bot's computer, choose Update Bot's Computer, then wait for the replacement to come up. Since the October 11 release, Settings → Computer separates your own computer from the Bot's computer, and Settings → Updates shows only app updates; on iPhone and Android the troubleshooting page names only Reset Computer under Settings → Bot → Bot Computer.
5. Only then use Reset Bot's Computer, in the same section, knowing it restores the last saved snapshot and can lose recent or unsynced work; Recover computer and Update preserve durable files and logins.

Sources: https://docs.x.ai/grok-bot/troubleshooting, https://docs.x.ai/grok-bot/settings-and-notifications, https://x.ai/changelog/bot, https://forum.cursor.com/t/grok-bot-was-reprovisioned-to-a-new-context-but-recent-data-from-the-previous-computer-was-not-carried-over/173771, https://forum.cursor.com/t/grok-bot-shared-computer-fully-wedged-since-2026-10-05-shell-dead-update-recover-reset-all-fail-please-reprovision/173881

## What the August to October incidents looked like

CellCog's problems tracker, citing a Cursor staff reply, describes an August 20 to 21 incident in which the shared computer behind affected accounts entered a stuck state, so every Bot on the account stopped at once. A larger wave followed in September. Cursor's status page records Grok Bot computers unreachable for some users on September 7, when Recover or Reset could also fail, then service degradations with bots that don't respond on September 16, 17 and 18. A forum thread opened September 16 gathered over 180 replies describing Bots that stopped responding and messages that were sent but never answered.

On September 20 and 21 a different symptom appeared: Updating Grok Bot's Computer hung at 43 percent on Transferring your data. Cursor staff said some computers were failing to fully rehydrate during recreation and most came up on their own, then closed the first thread on September 21 once computers stopped getting stuck.

That was not the end of it. A second thread, opened the same day the first was closed, collected the identical stall through September 23, including one user who said they had not been able to update the bot computer in about two weeks. Staff did not describe a systemic fix in that thread; instead they cleared individual accounts on request, once about 20 minutes after a September 21 screenshot and again for a different user on September 23. Treat the 43 percent stall as a recurring, not fully resolved, issue: post your version and the time in the forum thread rather than resetting, and expect staff to clear your account manually.

October brought a different mix. On October 3 Bots stopped answering in the early hours US Eastern time; a Cursor staff member said the fix landed at about 3:10 AM ET, that messages sent while it lasted were not retried, and that routines due between about 2:00 and 3:10 AM ET did not run. On October 5 an update left some computers stuck on Starting desktop because a recent change gave them too little storage, and the same storage problem left some replacement computers with a 16GB disk that was full on arrival until staff restored full-size disks on October 6. Some accounts got an automatic recreate that did not finish cleanly and came up from an incomplete copy; staff told those users not to press Update, Recover or Reset and replaced the computers individually. On the evening of October 6 (UTC) every Bot on some accounts answered Bot failed to respond until Cursor fixed it on its side; staff said no reset was needed.

October 8 piled several problems together. Early in the day (UTC) every Bot on some accounts answered Bot failed to respond until a fix on Cursor's side; from about 13:30 UTC a capacity limit stopped some Bots reaching their model until about 21:00 UTC; and replies failed for some users in one region, including Hong Kong, where people found a VPN helped, until a fix that evening. In each case staff said Bots and history were safe and a reset would not help. The same week, staff explained a quieter failure: a single Bot that always fails because the model provider's safety filter refuses its conversation history. The October 6 incident also pulled new replies into a five-week-old thread opened back on September 1 under the same error text; staff resolved it the same way, telling the latest posters their Bots should already be replying again and that no reset or other change was needed.

These are attributed community reports and status notices. The pattern they share is that user-side recovery did nothing during the incident window, and resets made things worse by discarding state. If your symptom matches a live status incident or thread, the useful action is to add your app version and timestamp to the thread and wait.

Sources: https://forum.cursor.com/t/grok-bot-failed-to-respond-on-every-bot-after-reset-recover-computer/173919, https://forum.cursor.com/t/grok-bot-0-68-1-bot-failed-to-respond-after-reset-sends-get-requestid-but-no-assistant-reply/174090, https://forum.cursor.com/t/grok-bot-primary-bot-silent-bot-failed-to-respond-since-oct-8-other-bots-ok-restart-this-bots-runner-only-do-not-reset/174138, https://forum.cursor.com/t/grok-bots-failing-to-respond-again/173658, https://forum.cursor.com/t/grok-bots-computer-is-stuck-on-starting-desktop-with-cant-reach-grok-bots-screen-attachments-wont-download-and-the-mobile-app-shows-send-after-reconnect-with-no-response/173788, https://forum.cursor.com/t/grok-bot-computer-reprovisioned-from-126gb-to-16gb-and-immediately-100-full-ticket-t-g55930/173656, https://forum.cursor.com/t/grok-bot-was-reprovisioned-to-a-new-context-but-recent-data-from-the-previous-computer-was-not-carried-over/173771, https://forum.cursor.com/t/grok-bot-failed-to-respond/170235, https://status.x.ai/history, https://forum.cursor.com/t/some-of-the-bots-became-unresponsive-failed-to-send-on-my-messages-to-them/171858, https://forum.cursor.com/t/grokbot-unavailable-hung-on-updating-grok-bots-computer-at-43/172401, https://forum.cursor.com/t/grokbot-unavailable-hung-on-updating-grok-bot-s-computer-at-43/172535, https://cellcog.ai/blog/grok-bot-problems/

## A Bot that goes quiet after a long tool wait

One report describes a Bot becoming unresponsive after a long-running tool call, with a recreated Bot showing 'Failed to send' until the app was restarted. If one Bot is silent while others work, the computer is probably fine. Send a 'Stop now' message, restart the app, and give the Bot a smaller bounded task before retrying the long one. If it is a routine that went quiet, [the routines guide](https://www.grokbotwiki.com/guides/grok-bot-routines-not-running) has its own checklist.

Recent versions handle this better, so update first. The changelog says 0.66.0 (October 2) makes a Bot that hangs on an unresponsive command or computer stop itself with a note, and your next message picks up where it left off. 0.68.1 (October 7) makes Stop or a new message end a Bot stuck on an unresponsive step within about 30 seconds, and the Bot's browser now gives up on a stuck page after 25 seconds. The October 11 release (0.69.0 to 0.70.2) adds two more: Bots acknowledge your message before longer work, and a Bot can wait for a background command to finish, shown as Waiting on results, so a quiet Bot is not necessarily a stuck one. 0.71.2 (October 14) goes further: Stop also ends a Bot's background subagents and expires their pending approval cards, connector calls wait up to two minutes instead of timing out after one, and a Bot posts its answer when you hand its computer back with I'm done or Skip instead of sometimes staying silent. Since 0.75.2 (October 22) the Bot also tells you before a browser or desktop task that will take a few minutes.

- [ ] You opened the computer view and looked for a login, CAPTCHA, or approval before resetting.
- [ ] You checked the status page (status.x.ai, formerly status.cursor.com) and the forum tag for an incident with a matching timestamp.
- [ ] You followed Retry, restart, Recover, Update before Reset.
- [ ] You noted the app version and time in case you need to report it.
- [ ] You are on the latest app version (Settings → Updates), since 0.66.0, 0.68.1 and 0.70.2 fixed hung-Bot, crash-loop and sleeping-computer handling, and 0.71.2 to 0.75.5 fixed the asleep, reconnect, safety-check and proxy cases in the table above.

Sources: https://docs.x.ai/grok-bot/troubleshooting, https://x.ai/changelog/bot, https://x.ai/changelog/bot#v0.71.2, https://x.ai/changelog/bot#v0.75.2

## Your own Mac or PC looks connected, but a file copy drops it

A forum thread opened August 29, past 690 views by October 29, describes Settings → Computer showing your own Mac as connected while the Bot cannot use it: one Shell command works, the next fails as disconnected, and copying a file to or from the Mac fails with the computer unavailable. A Cursor staff member (deanrie) explained on August 29 that when a command or a file copy hits a timeout, the machine is removed from the Bot's machine list for about a minute even though Settings still shows connected, and that the set of available machines is fixed when a turn starts, so No registered machines were available when this turn started means the machine reconnected mid-turn and a new message will pick it up. They confirmed the same cause for a large archive copy on September 3 and for a Windows report, and still had no ETA on September 17.

The staff workaround, repeated in each reply: split large copies into smaller pieces instead of one big archive; if the machine drops, wait about a minute before retrying rather than retrying at once; and if it stays stuck, fully quit Grok Bot (Cmd+Q on a Mac), end any stuck local-exec-daemon process (pkill -f local-exec-daemon in Terminal, or Task Manager on Windows), and reopen the app. A Windows user added a workaround of their own on September 16: delete the local-exec-daemon log files under the .grokbot folder in your user profile, restart the computer, open Grok Bot, wait a full minute, then start a new chat. On October 29 a user on Grok Bot 0.78.1 reported copies over about 100 KB still failing with temporarily unreachable on an M1 MacBook Air, so treat this as open. It is a community report with a staff reply, not a fix we tested, and the release notes through 0.78.1 do not name it.

Sources: https://forum.cursor.com/t/grok-bot-local-computer-execution-looks-connected-in-settings-but-is-not-actually-usable-for-file-i-o/169877, https://x.ai/changelog/bot#v0.78.1

## Every Shell command hangs, but Bots can still read files

A forum thread opened on October 20 describes a Bot's computer where every Shell command, even echo ok, failed with "The Shell tool call timed out after 840 seconds" for all 11 Bots on the account, while connectors such as Gmail and Calendar kept working. Update and Reset did not help.

A Cursor staff member replied on October 21 that the Reset had moved the computer onto a fresh machine with the files restored, so the stall pointed to something in the saved files rather than the machine. Every Shell command first starts a login shell, which runs the computer's shell startup files; if one of them waits on something, such as a line that starts a service, runs sudo or calls a script, every command hangs. Their recovery step: ask a Bot to open /home/box/.bashrc, /home/box/.profile and /home/box/.bash_profile (or the same names under ~/) with its file reading tool, not Shell, look for anything recently added near the end, and hold off on another Reset or Update, since a Reset restores the same files.

In that thread the poster's Bots found an autostart line for a relay script near the end of .bashrc, which they suspected. The computer started working again on October 25 without a further staff reply, and the poster said they did not know whether it recovered on its own or was fixed. On October 26 another user reported the same symptom for two to three days, with file reads also timing out, so the file check does not work once the computer stops answering entirely. If you add startup commands to a Bot's computer, keep them out of shell startup files, or make sure they return immediately. This is a community report with a staff reply, not a fix we tested.

More accounts hit the same symptom in the last week of October, and staff replies point to two different causes. In a 204-view thread opened October 23, the poster's computer had been frozen since the afternoon of October 22: every command stalled for about 14 minutes and failed, Update Bot's Computer did not help, and the app showed disk space unknown. A Cursor staff member replied on October 24 that the computer was running but every command stalled before it started, that a move to a fresh machine, Update Bot's Computer and Reset all bring the saved files along, so a stalling startup file comes back each time, and asked users not to Reset, since it can lose recent work that has not been saved yet. Their recovery step: from the desktop app on your Mac, ask a Bot that uses its computer to copy /home/box/.profile and /home/box/.bashrc to your Mac with its file copy action, not a terminal command, and look for lines near the end that start a program, connect to something or run a script. The fix is usually to copy the corrected files back the same way and run Update Bot's Computer once, which keeps saved files. Staff added that a stalled command uses no usage while it waits, but each failure costs a short follow-up step and routines that need the computer keep retrying, so pause those routines meanwhile.

In that thread the cause was a watchdog line in .bashrc written as pgrep ... || nohup ... &. Staff explained on October 26 that the trailing & sends the whole line to the background, which keeps terminal startup from finishing whenever the watchdog is not already running, as on a fresh computer after a move or update. Their advice: keep the line commented out and start the program from a routine instead, or wrap only the launch part in braces, { nohup ... & }, so only that part runs in the background.

The second cause needed Cursor's side. In a 213-view thread opened October 25, a computer that froze again right after a Reset on October 23 hung every command and file read for about 14 minutes, and Update and Reset both failed, while chat, memory and connectors still worked. A Cursor staff member wrote on October 26 that some users had two computers started, and on October 27 that the team had run manual cleanup for accounts stuck with two; the poster's computer came back that day, froze again, and was working by October 29. Another user, whose startup files were clean and whose computer view never got past Starting desktop…, reported on October 29 that theirs had come back too after staff said they were investigating. If your startup files are clean and Update and Reset fail, this is not something you can fix yourself: contact support with your ticket number instead of resetting again. These are community reports with staff replies, not fixes we tested.

One related cause now has a release-note fix: the 0.77.0 changelog (October 26) says commands on the Bot's computer that wait for input, such as package install prompts, finish instead of hanging. That covers a single command stuck on a prompt, not a startup file that stalls every login shell, so if every command still times out after updating, the file check above is still the step to take.

Sources: https://forum.cursor.com/t/grok-bot-box-unresponsive/175485, https://forum.cursor.com/t/grok-bot-computer-frozen-since-oct-22-1-45-pm-et-all-commands-time-out/175846, https://forum.cursor.com/t/grok-bot-shared-computer-frozen-since-10-23-after-reset-shell-and-file-reads-hang-about-14-min-and-update-and-reset-both-fail-t-i28766/176129, https://x.ai/changelog/bot#v0.77.0

## A Bot that keeps trying the same thing

Sometimes a Bot is not silent but stuck in a loop: retrying a page, re-running a search, or repeating an approach without new evidence. Before sending the whole request again, find out whether the first attempt already wrote anything. A retry can create a second draft, ticket or message if the earlier attempt succeeded just before it lost its way.

Ask for the last action it confirmed, the first step that failed, and any changes it already made outside the chat. If a source failed, test one small read before rerunning the full task. This brief is our editorial template; it moved here from a separate triage guide that now redirects to this page.

One common loop has an official fix. The October 11 changelog says that when a connector is rate-limited, Bots now wait for its retry delay instead of looping, and Slack, Gmail and Outlook drafts retry through temporary rate limits and say if they still could not send. Connector calls should also fail less often. If a Bot on an older version keeps hammering one connector, update the app first.

Editorial template (replace placeholders and review access before running):

```text
Pause the current approach and diagnose the blocker. State the last action confirmed successful, the first failing step, the exact visible error if any, and whether any external changes already occurred. Do not repeat writes or reset the computer. Suggest one small, non-destructive check that distinguishes missing access from unavailable data or a changed interface. If you need my input, identify the precise action I should take. Preserve partial results and link them here.
```

Sources: https://x.ai/changelog/bot

## Quick answers

### Which Grok Bot version fixed which symptom?

Going by the release notes: 0.71.2 (October 14) shows Your computer is asleep instead of Couldn't refresh or connection errors, lets you wake an asleep computer in place by clicking its preview, says a computer couldn't start instead of retrying as if it were still starting, reconnects a working Bot when its computer updates, treats a sleeping Mac or PC as disconnected within two minutes, keeps your computer reachable after a Wi-Fi, VPN or other network change, gives connector calls up to two minutes instead of timing out after one, and shows Blocked by a safety check instead of a generic error. 0.75.2 (October 22) fixes loading behind some corporate proxies and says when a message could not be saved because the disk is full. 0.75.5 (October 23) makes new messages get replies after you reset a chat whose first message was blocked. Update first; the notes describe fixes, not a guarantee for every account.

### Why did all my Bots stop responding at the same time?

Every Bot in an account shares one cloud computer. When that computer is stuck, unreachable, or mid-update, all Bots fail together. That is why 'Bot failed to respond' tends to hit the whole account, and why the fix is on the computer, not the Bot.

### Should I reset the Agent Computer?

Only as the last step. The official order is Retry, restart the app, Recover computer, Update Agent Computer, and then Reset. Reset can lose unsynced work, and forum users report resets that stall at 50 percent during service incidents. In October, Cursor staff repeatedly asked people whose problem was on Cursor's side to hold off on Update, Recover and Reset altogether; after the October 3 and October 6 incidents the fix was simply to send the message again.

### How do I know if it is an outage and not me?

Look at the live status panel at the top of this page, which reads status.x.ai (Cursor's status page redirects there since its October 26 move), then the Cursor forum's grok-bot tag, and compare timestamps. Cursor's status page recorded 21 incidents involving Grok Bot on 14 different days between September 3 and October 9; the main forum thread from September 16 passed 180 replies while nothing on the user side helped. If many people report the same symptom in the same hour, wait rather than reset.

### Why does one Bot always say Bot failed to respond while my other Bots work?

Often its conversation, not the computer. In October, Cursor staff explained several such cases: the AI model provider's safety filter had flagged something in that Bot's history, such as security or biology research material, and because every new message is sent with that history, every reply was refused and shown as a generic error. Resetting does not help. Staff advise using another or a new Bot for new work, not asking other Bots to read or continue the stuck Bot's chat, and not deleting it while they look for a recovery option. Since 0.71.2 the release notes say a reply blocked by a safety check shows Blocked by a safety check and Try a different message instead of a generic error, and 0.75.5 says that after you reset a chat whose first message was blocked, new messages get replies instead of an error.

## Sources

- [Official troubleshooting](https://docs.x.ai/grok-bot/troubleshooting)
- [Grok Bot overview](https://docs.x.ai/grok-bot/overview)
- [Status history (Cursor's incidents, on status.x.ai since October 26)](https://status.x.ai/history)
- [Forum: Grok bot failed to respond (15 replies, resurfaced during the October 6 incident)](https://forum.cursor.com/t/grok-bot-failed-to-respond/170235)
- [Forum: some Bots became unresponsive (September 16, 186 replies)](https://forum.cursor.com/t/some-of-the-bots-became-unresponsive-failed-to-send-on-my-messages-to-them/171858)
- [Forum: computer update hung at 43 percent (staff update)](https://forum.cursor.com/t/grokbot-unavailable-hung-on-updating-grok-bots-computer-at-43/172401)
- [Forum: computer update hung at 43 percent, second thread (12 replies, reports into a second week)](https://forum.cursor.com/t/grokbot-unavailable-hung-on-updating-grok-bot-s-computer-at-43/172535)
- [Forum: Windows authentication error (staff fix)](https://forum.cursor.com/t/grok-bot-windows-0-44-0-authentication-error-persists-after-update-logout-login-and-cache-clear/171115)
- [Cursor plans and billing (usage-limit screen)](https://cursor.com/help/grok-bot/plans)
- [CellCog problems tracker](https://cellcog.ai/blog/grok-bot-problems/)
- [Grok Bot changelog (versions 0.63.0 to 0.70.2)](https://x.ai/changelog/bot)
- [Settings: update or reset Bot's computer](https://docs.x.ai/grok-bot/settings-and-notifications)
- [Forum: Grok Bots failing to respond again (staff reply on the October 3 fix)](https://forum.cursor.com/t/grok-bots-failing-to-respond-again/173658)
- [Forum: Starting desktop and Can't reach Grok Bot's screen (staff fix, October 5)](https://forum.cursor.com/t/grok-bots-computer-is-stuck-on-starting-desktop-with-cant-reach-grok-bots-screen-attachments-wont-download-and-the-mobile-app-shows-send-after-reconnect-with-no-response/173788)
- [Forum: computers reprovisioned with a 16GB disk (staff fix, October 6)](https://forum.cursor.com/t/grok-bot-computer-reprovisioned-from-126gb-to-16gb-and-immediately-100-full-ticket-t-g55930/173656)
- [Forum: an automatic recreate that did not finish cleanly (staff reply, October 5)](https://forum.cursor.com/t/grok-bot-was-reprovisioned-to-a-new-context-but-recent-data-from-the-previous-computer-was-not-carried-over/173771)
- [Forum: shell dead, Update, Recover and Reset all fail (staff reply, October 7)](https://forum.cursor.com/t/grok-bot-shared-computer-fully-wedged-since-2026-10-05-shell-dead-update-recover-reset-all-fail-please-reprovision/173881)
- [Forum: every Shell command times out, check shell startup files (staff reply, October 21)](https://forum.cursor.com/t/grok-bot-box-unresponsive/175485)
- [Forum: computer frozen, every command times out after 14 minutes; startup-file check and watchdog fix (staff replies, October 24 and 26)](https://forum.cursor.com/t/grok-bot-computer-frozen-since-oct-22-1-45-pm-et-all-commands-time-out/175846)
- [Forum: computer frozen after Reset, Update and Reset fail; two computers started, manual cleanup (staff replies, October 26 and 27)](https://forum.cursor.com/t/grok-bot-shared-computer-frozen-since-10-23-after-reset-shell-and-file-reads-hang-about-14-min-and-update-and-reset-both-fail-t-i28766/176129)
- [Forum: all Bots silent with no usage limit message, fixed (staff update, October 30)](https://forum.cursor.com/t/grok-bot-all-bots-completely-unresponsive-after-update-agent-computer-recovery-and-reset/172118)
- [Forum: Bot failed to respond on every Bot (staff reply, October 6)](https://forum.cursor.com/t/grok-bot-failed-to-respond-on-every-bot-after-reset-recover-computer/173919)
- [Forum: outbound non-HTTPS traffic blocked since October 1 (staff reply)](https://forum.cursor.com/t/grok-bot-computer-all-outbound-non-https-traffic-blocked-since-oct-1-mysql-ssh-imap-smtp-ftp-time-out/173504)
- [Forum: one Bot fails while others reply, blocked by the model provider's safety filter (staff reply, October 8)](https://forum.cursor.com/t/grok-bot-primary-bot-silent-bot-failed-to-respond-since-oct-8-other-bots-ok-restart-this-bots-runner-only-do-not-reset/174138)
- [Forum: existing Bots fail since October 8, safety filter on biology content (staff reply, October 10)](https://forum.cursor.com/t/grok-bot-restore-existing-agents-that-fail-with-bot-failed-to-respond-since-oct-8-do-not-reset/174246)
- [Forum: Bots stop responding after a literature review request (staff reply, October 10)](https://forum.cursor.com/t/grok-bot-bots-error-out-and-stop-responding-whenever-i-ask-for-a-scientific-literature-review-reset-didnt-help/174218)
- [Forum: trouble connecting and Reset fails after a trial ended (staff reply, October 8)](https://forum.cursor.com/t/grok-bot-completely-unusable-recovery-and-reset-both-fail/174022)
- [Forum: Reset failed, computer stuck in a partial state (staff reply, October 8)](https://forum.cursor.com/t/grok-bot-0-68-1-reset-failed-computer-stuck-in-partial-state/174099)
- [Forum: Can't reach the Bot's screen after the computer's first startup failed (staff replies, October 7 and 12)](https://forum.cursor.com/t/grok-bot-0-68-1-macos-cant-reach-computer-delete-fails-update-does-nothing/173950)
- [Forum: Mac shows disconnected until the app is focused (staff replies, October 9 to 13)](https://forum.cursor.com/t/grok-bot-0-68-1-macos-mac-shows-disconnected-while-awake-and-in-use-local-computer-doesnt-reconnect-until-app-is-focused/174223)
- [Forum: Bot thinks my computer is offline or sleeping (staff reply, October 10)](https://forum.cursor.com/t/grok-bot-thinks-my-computer-is-offline-or-sleeping-but-it-is-not/174267)
- [Forum: your own computer looks connected but a file copy drops it (staff workaround, August 29 to September 17; still reported on 0.78.1, October 29)](https://forum.cursor.com/t/grok-bot-local-computer-execution-looks-connected-in-settings-but-is-not-actually-usable-for-file-i-o/169877)
- [Grok Bot changelog: 0.75.8 (October 24): reconnect after the Bot's computer wakes, Authenticate state, status line, Slack safety-check notice](https://x.ai/changelog/bot#v0.75.8)
- [Grok Bot changelog: 0.77.0 (October 26): computer stays up on low memory, commands waiting for input, Not delivered yet, Stop and Update](https://x.ai/changelog/bot#v0.77.0)
- [Grok Bot changelog: 0.78.1 (computer card, Update dialog, Route traffic and Reset fixes, October 27)](https://x.ai/changelog/bot#v0.78.1)
- [Forum: Mac mini local computer drops while idle (staff reply, October 8)](https://forum.cursor.com/t/grok-bot-0-68-1-on-mac-mini-local-computer-drops-while-idle-and-does-not-self-heal/174109)
- [Forum: replies failing for some users in one region (staff fix, October 9)](https://forum.cursor.com/t/grok-bot-0-68-1-bot-failed-to-respond-after-reset-sends-get-requestid-but-no-assistant-reply/174090)
- [Grok Bot changelog 0.71.2 (October 14): asleep computer, reconnects, safety-check message, connector timeouts](https://x.ai/changelog/bot#v0.71.2)
- [Grok Bot changelog 0.75.2 (October 22): corporate proxy loading, disk-space message, Couldn't refresh in Connect Apps](https://x.ai/changelog/bot#v0.75.2)
- [Grok Bot changelog 0.75.5 (October 23): replies after resetting a blocked chat](https://x.ai/changelog/bot#v0.75.5)
- [Forum: all my Grok Bots disappeared after the X Subscription switch (staff replies, October 21)](https://forum.cursor.com/t/all-my-grok-bot-disappear/175510)

---

# Grok Bot weekly usage limit: why it runs out, how to cap it

> Grok Bot's weekly allowance is unpublished and Cursor's on-demand cap isn't a hard stop. What burns usage, when it resets, X Subscription top-ups, and settings that help.

- Canonical page: https://www.grokbotwiki.com/guides/grok-bot-weekly-usage-limit
- Sources checked: 2026-11-01
- Evidence: The X Subscription usage, top-up and spending-cap docs, cursor.com/pricing, and Cursor billing and routines help rechecked October 25, 2026 · x.ai/bot and the Grok Bot changelog through 0.75.5 read in a browser October 25, 2026 · changelog entry 0.77.0 and docs.x.ai's Shared Bots page read October 28 · changelog entry 0.78.1 read October 29 · x.ai/pricing last read October 14, 2026 · forum staff replies rechecked October 14, 2026 · Cursor staff forum replies and user cost reports attributed, not reproduced · forum token-usage thread read October 27 · Cursor forum grok-bot tag rechecked November 1 · status.x.ai incidents API read November 1. Suggested workflows have not been independently tested.
- Publisher: Grok Bot Wiki, an independent guide not affiliated with SpaceXSI, xAI or X.

## How the meter actually works

The X Subscription, launched October 12, 2026, changes the meter for anyone who buys or switches to it. SpaceXSI's docs say each paid seat gets one weekly pool shared across eligible Grok and Cursor use, including Grok Bot, rather than a separate Grok Bot allowance, and that usage rates vary by product. Once the pool is used, further use is Additional Usage paid from prepaid credit bought with top-ups, and third-party models in Cursor are paid from that credit from the first use. On a team, each seat has its own pool and the team shares one prepaid balance. After switching, usage is under Usage at grok.com/dashboard. The rest of this section describes the existing Cursor and SuperGrok plans, which continue for current subscribers.

On the existing plans, every eligible plan includes Grok Bot usage that resets weekly, in a bucket separate from Grok chat and Cursor editor usage; Cursor staff confirmed in September that Grok Bot chats and routines do not draw on Cursor plan quota, with one exception: a Cursor Cloud Agent that a Bot launches bills to your Cursor plan. Allowances do not add together: Cursor's billing page says a Cursor plan and a linked SuperGrok or X Premium+ subscription do not stack, and Grok Bot uses whichever grants more weekly usage. After upgrading a linked SuperGrok tier, allow up to 24 hours for the weekly allowance to move. Consumption is measured by agent steps and tokens, not messages: a Bot that spends twenty minutes scrolling a website costs far more than twenty short chat replies.

That separation has a limit, and even Cursor staff got it wrong once. In an August thread a Pro user asked why Grok Bot was showing up against their Cursor model quota after an email had promised a dedicated pool. A staff reply first said Grok Bot simply used the plan's Cursor quota, not a separate limit; after the user quoted the announcement email back, staff corrected themselves: the weekly included Grok Bot pool genuinely is separate from Cursor plan usage, but only up to that weekly limit. Once the weekly pool is used up, any further Grok Bot usage on an on-demand-enabled account bills from the same shared on-demand pool as the rest of your Cursor usage, not a second dedicated on-demand allowance. If your dashboard shows Grok Bot eating into Cursor spend before your weekly allowance looks exhausted, that overflow behavior, not a bug, is the likely explanation; check the usage screen for which pool it charged.

A second, cosmetic version of the same confusion turned up on a Teams seat in September: grok-bot-default and grok-bot-cua rows were appearing inside the Cursor Models and Other Models breakdown on the Spending page, making it look like Grok Bot was eating the Cursor quota even though the headline percentages stayed Cursor-only. Cursor staff (mohitjain, Colin) called it a display bug they were tracking and confirmed by September 11 that the rows were removed from that breakdown. Asked on October 20 whether the same separate-pool behavior carries over to the new Ultra, a Cursor staff member said no: on The X Subscription (Premium, Super and Ultra) there is no separate Grok Bot allowance at all, Grok Bot draws from the same shared weekly pool as your Cursor and Grok usage, and only third-party models such as Claude or GPT bill from prepaid top-up credit; the legacy separate-allowance behavior described above applies only to the older Cursor plans.

Usage readings jumped for many accounts on November 1. In a forum thread started at 04:25 UTC, AerethoS, on Cursor Ultra, wrote that the weekly meter at the bottom of the app kept flipping between about 77% and 100% while their own tracking read 77.7%. Within hours about twenty users in all had reported similar jumps, many of them roughly a doubling (33% to 66%, 44% to 88%, 50% to 100%) with no new activity, some on legacy Cursor Pro+ and Super; some saw the Bot and Settings disagree, and at least one said the Bot later stopped replying with limit reached. At 05:38 UTC the status page opened an incident on a degradation affecting the billing and usage dashboard, listing cursor.com and the Enterprise Dashboard rather than Grok Bot, and it was still being investigated at 08:44 UTC. No Cursor staff member had replied in the thread by 10:00 UTC, and the incident does not say whether usage will be corrected. The official step for now is to follow that incident on [our status guide](https://www.grokbotwiki.com/guides/is-grok-bot-down) or status.x.ai, and note your reading before and after so you can raise it with support.

Cursor staff also explained why long chats get expensive: every turn re-reads that Bot's whole conversation, and it only auto-summarizes near the model's limit. In one account staff reviewed, the busiest Bots were re-reading roughly 80,000 to 90,000 tokens per step, and about a third of all turns were Bots waking other Bots.

A second staff explanation, from October 14, covers the usage page itself. A user asked why rows on the usage page showed 50,000 to 165,000 tokens for one-line replies. A Cursor staff member replied that the Tokens number on each row counts everything the model read on that call, including the Bot's instructions, memory, tool list and recent chat, that most of it is cached context billed at a much lower rate than new input, and that hovering over a token count on the usage page splits it into input, output, cache read and cache write; all of those rows count against the plan's included usage, so nothing extra had been charged. Staff endorsed the same levers: fewer event-triggered wake-ups (the user's change-watch routine had been waking a Bot on every pull request), fewer Bot-to-Bot messages, and a leaner background for each Bot, which cut the user's per-call size to roughly a third. Cloud Agent coding jobs are always much larger than a single reply, and staff pointed to an AGENTS.md map of each repo and a .cursor/CLOUD.md file to shorten them. The same user later reported spending $100 of on-demand usage in under a day, and another user agreed on October 27; there is still no way to route a coordinating Bot to a cheaper model.

When the allowance runs out, work continues on on-demand billing derived from model and token cost, provided on-demand is enabled on the account. Since 0.63.0, running out shows the usage limit notice rather than Bot failed to respond, and since 0.59.0 the limit banner offers Upgrade, Set Spend Limit, or Request Upgrade to ask your admins. Since 0.75.5 (October 23), if your Grok Business seat does not cover Grok Bot yet, the usage limit message says to ask your Grok Business admin to connect your team. See [our plan and pricing guide](https://www.grokbotwiki.com/guides/grok-bot-which-plan) for the plans and spending controls; the linked forum report describes an earlier user experience. The usage banner can be dismissed but returns, which one thread asks to fix. Since 0.77.0 (October 26), when usage cannot load, Usage & Billing keeps the last reading with Try again, even after a relaunch, instead of going blank. Since 0.78.1 (October 27) the usage limit banner closes on its own once you are back under your limit, and a usage breakdown from a Bot labels its catch-all row Deleted bots, group chats and other people's bots. On a shared Bot (the docs' new name for a Team Bot), the docs say a reply uses the usage of the person it is answering, in your own chat, in Slack and in group chats, and that Your usage limit has been reached in a teammate's shared Bot means your own allowance ran out, while This Bot's owner has reached their usage limit means that reply was billed to the owner.

Sources: https://x.ai/changelog/bot#v0.78.1, https://docs.x.ai/grok-bot/shared-bots, https://x.ai/changelog/bot#v0.77.0, https://docs.x.ai/x-subscription/usage-limits, https://docs.x.ai/x-subscription/extra-usage, https://docs.x.ai/x-subscription/grok-bot, https://x.ai/news/x-subscription, https://docs.x.ai/grok-bot/faq, https://cursor.com/help/grok-bot/plans, https://x.ai/changelog/bot, https://forum.cursor.com/t/grok-bot-spend-cursor-usage-i-cant-accept-it/169796, https://forum.cursor.com/t/does-grok-bot-consume-cursor-quota/171742, https://forum.cursor.com/t/1-500-in-one-week-running-a-grok-bot-fleet-expected-or-a-bug/172705, https://forum.cursor.com/t/grok-bot-gives-no-warning-before-weekly-usage-spills-into-paid-on-demand/169679, https://forum.cursor.com/t/grok-bot-token-usage/174723, https://forum.cursor.com/t/is-grok-bot-eating-at-cursor-usage-i-thought-it-had-its-seperate-usage/170990, https://forum.cursor.com/t/grok-bot-weekly-usage-meter-flips-between-77-and-100-in-real-time/176909, https://status.x.ai/history?incident=cursor-com%2Fps_838fe2a3a154acfa

## What burns it fastest

Community reports point at the same culprits: many Bots running in parallel, long unattended browser sessions, routines that run whether or not there is new data, and Bots retrying a stuck page. One user described 42 percent of a weekly allowance gone on day one across six Bots; another put five percent on a hundred small completions plus a ten-minute script. A forum thread on the API path reports costs far above expectation.

There is no model picker, so you cannot route small jobs to a cheaper model. The levers you do have are fewer Bots, shorter tasks, and routines that stop early when nothing changed. Cursor staff add four more: start a fresh chat for each task from the + at the top of the sidebar, keep standing instructions in the Bot's profile so a fresh chat loses little, tell Bots to message each other only when action is needed, and space routines out rather than running them every few minutes. Cursor's routines help puts the last point bluntly: an hourly schedule, a short interval, or a Slack trigger on a busy channel can use a week of usage in a day. The run caps are no brake on that: since 0.75.5 your routines can run up to 300 times an hour in total, up from 100, and each routine up to 200 times an hour.

A forum thread on stretching the weekly allowance (380 views by October 31) collects similar user tips. Its author, linkd, notes that a long chat re-reads its whole history on every step and suggests starting new conversations with the same Bot; another user, bee, batches requests into one text file that a Bot reads and splits into tasks for other Bots, keeps shared rules in a common workspace, and avoids spreading work across many Bots. A third user said they had sent Cursor feedback asking for chat branches that carry a short core memory of the Bot's role instead of the full history. No Cursor staff member had replied there by October 31; the official step remains the one above: start a fresh chat per task and keep standing instructions in the Bot's profile.

Coding work a Bot hands off is billed separately. Cursor staff said in September that a Cursor Cloud Agent launched by a Bot bills to your Cursor plan, and on a team, everything you run, including the Cloud Agents your Bot starts, is billed through your team seat. Our [shared-computer guide](https://www.grokbotwiki.com/guides/grok-bot-shared-computer) explains why long chats cost more on every reply.

Troubleshooting during an outage burns usage too. When scheduled routines failed on October 8, several users said they spent a large share of their week having Bots investigate, one reporting over 90 percent used with five days left. Cursor staff said pausing, editing or recreating routines would not help during that incident. Check [Is Grok Bot down?](https://www.grokbotwiki.com/guides/is-grok-bot-down) and the forum before asking a Bot to debug itself.

Retry loops are cheaper on current versions. The October 11 release (0.69.0 to 0.70.2) says Bots now wait for a rate-limited connector's retry delay instead of looping, and connector calls fail less often, so update the app if a Bot seems to spend usage retrying the same connector.

Sources: https://x.ai/changelog/bot, https://cellcog.ai/blog/grok-bot-problems/, https://forum.cursor.com/t/all-grok-bot-routines-failed-to-run/174125, https://forum.cursor.com/t/anyone-used-grokbot-on-the-api-very-high-costs/169551, https://forum.cursor.com/t/grok-bot-ultra-users-how-do-you-make-the-weekly-allowance-last-mine-reached-99-in-three-days/171221, https://forum.cursor.com/t/1-500-in-one-week-running-a-grok-bot-fleet-expected-or-a-bug/172705, https://cursor.com/help/grok-bot/routines, https://forum.cursor.com/t/does-grok-bot-consume-cursor-quota/171742, https://forum.cursor.com/t/cloud-agents-by-grokbot-using-team-cloud-credits-instead-of-personal-usage/173419, https://forum.cursor.com/t/best-practices-for-using-grok-bot-more-token-efficiently/175188

## The setting that protects you

Review the on-demand control described in [our plan and pricing guide](https://www.grokbotwiki.com/guides/grok-bot-which-plan); do not assume a spending limit interrupts work immediately. Decide deliberately whether on-demand is enabled, and if it is, set the limit before the first routine runs unattended. On a legacy self-serve Cursor Teams plan, on-demand is enabled by default.

On The X Subscription the controls are different. SpaceXSI's docs list four: the weekly pool, a prepaid balance, a monthly additional usage limit, and Auto Top-up, which is off unless you turn it on. Set them under Additional usage credits at grok.com/dashboard. Adding credit does not raise the monthly limit, and spend alerts warn without stopping usage. The steps below are for the existing Cursor plans.

1. In Grok Bot, open Settings → Usage & Billing and find On-demand monthly limit (choose Enable if it is off); on the web, the same cap is Spending, Monthly Limit at cursor.com/dashboard. If Grok Bot asks for a card, or you subscribed in the iOS or Android app, set it on the web.
2. Either disable on-demand, accepting that Bots stop when the allowance ends, or set a monthly limit you can afford, remembering that a run already in progress can finish past it.
3. In the Grok Bot app, open Settings → Usage & Billing and note today's level and when it resets, which the screen shows since 0.63.0. Since the October 11 release the meter labels its percentage as used, so 80% means 80% gone, not left, and Current plan shows your plan's name.
4. Run one Bot on one bounded task and reread usage to learn what a single run costs.
5. Add routines last, with a no-change early exit, and check usage after their first unattended week.

- [ ] On-demand (or, on The X Subscription, Auto Top-up and the monthly additional usage limit) is deliberately set.
- [ ] Each new task starts in a fresh chat instead of one ever-growing thread.
- [ ] You know your reset day.
- [ ] Every routine has a stop-if-nothing-changed instruction.
- [ ] You are running the fewest Bots that get the job done.

Sources: https://docs.x.ai/grok-bot/faq, https://cursor.com/help/grok-bot/plans, https://docs.x.ai/grok-bot/settings-and-notifications, https://x.ai/changelog/bot, https://docs.x.ai/x-subscription/spending-caps, https://docs.x.ai/x-subscription/extra-usage

## Quick answers

### Is there a Grok Bot spending cap?

Yes, and how it behaves depends on your plan. On The X Subscription, SpaceXSI's docs say a monthly additional usage limit is how you put a hard stop on paid extra usage, and extra usage also stops when your prepaid balance is empty; spend alerts only warn. On the existing Cursor plans there is a caveat. The On-demand monthly limit in Grok Bot Settings is the same cap as Monthly Limit under Spending on the Cursor dashboard, and Cursor's billing page says it is not a hard stop in the middle of a run: a Bot already working can finish past it. With on-demand off, Grok Bot stops when weekly usage runs out. A Cursor staff reply also suggests a $0 on-demand limit if you want a hard stop.

### How big is the weekly allowance?

Unpublished. On The X Subscription, x.ai/pricing and cursor.com/pricing give Premium 4x the usage of Plus, Super 15x and Ultra 50x, without an absolute figure, and that pool also covers your Grok and Cursor use. The x.ai/bot pricing panel words it relative to Premium instead: Super 3.5x and Ultra 12x Premium usage. For the existing plans, the docs describe it only relatively: Pro below Pro+ below Ultra, with SuperGrok tiers following the same pattern and an X Premium+ link below SuperGrok Plus. Cursor staff said on September 22 that there is no tier above Ultra and no published dollar figure, and on September 10 that Cursor Ultra and SuperGrok Heavy give the same top-tier Grok Bot allowance. Forum users report a full week consumed in one day by a six-Bot setup, and around five percent consumed by about a hundred short completions plus one ten-minute script.

### When does the allowance reset?

Weekly. Cursor's billing page says the included grant resets weekly but does not name a day; on The X Subscription, SpaceXSI's docs say the live usage view shows the next reset date. Since version 0.63.0 (September 29), Settings → Usage & Billing shows your included usage and when it resets; before that fix, some accounts saw a message saying their plan had none. If your app is older, update it, or note the day the meter moves back up.

## Sources

- [SpaceXSI: Introducing The X Subscription (October 12, 2026)](https://x.ai/news/x-subscription)
- [Grok Bot docs: Shared Bots (whose usage pays for a shared Bot chat)](https://docs.x.ai/grok-bot/shared-bots)
- [Grok Bot changelog: 0.78.1 (usage limit banner closes itself, October 27)](https://x.ai/changelog/bot#v0.78.1)
- [Grok Bot changelog: 0.77.0 (Usage & Billing keeps the last reading, October 26)](https://x.ai/changelog/bot#v0.77.0)
- [x.ai pricing: usage by plan](https://x.ai/pricing)
- [Forum: Grok Bot token usage (staff reply on what the usage page's Tokens column counts, October 14)](https://forum.cursor.com/t/grok-bot-token-usage/174723)
- [Forum: best practices for using Grok Bot more token-efficiently (user tips, October 18 to 31)](https://forum.cursor.com/t/best-practices-for-using-grok-bot-more-token-efficiently/175188)
- [Forum: weekly usage meter flips between 77% and 100% (user reports, November 1)](https://forum.cursor.com/t/grok-bot-weekly-usage-meter-flips-between-77-and-100-in-real-time/176909)
- [Status: billing and usage dashboard degradation, November 1](https://status.x.ai/history?incident=cursor-com%2Fps_838fe2a3a154acfa)
- [Cursor pricing: usage by plan](https://cursor.com/pricing)
- [Grok Bot product page: usage by plan](https://x.ai/bot)
- [The X Subscription docs: usage limits](https://docs.x.ai/x-subscription/usage-limits)
- [The X Subscription docs: extra usage credits and top-ups](https://docs.x.ai/x-subscription/extra-usage)
- [The X Subscription docs: spending caps](https://docs.x.ai/x-subscription/spending-caps)
- [The X Subscription docs: Grok Bot on The X Subscription](https://docs.x.ai/x-subscription/grok-bot)
- [Billing and access FAQ](https://docs.x.ai/grok-bot/faq)
- [Cursor Grok Bot docs](https://cursor.com/help/grok-bot/plans)
- [Settings: usage and billing](https://docs.x.ai/grok-bot/settings-and-notifications)
- [Forum: "Grok Bot spend cursor usage, I can't accept it" (staff correction, 1,369 views)](https://forum.cursor.com/t/grok-bot-spend-cursor-usage-i-cant-accept-it/169796)
- [Forum: Ultra allowance at 99% in three days (staff tips)](https://forum.cursor.com/t/grok-bot-ultra-users-how-do-you-make-the-weekly-allowance-last-mine-reached-99-in-three-days/171221)
- [Forum: about $1,500 in one week running a Bot fleet (staff reply)](https://forum.cursor.com/t/1-500-in-one-week-running-a-grok-bot-fleet-expected-or-a-bug/172705)
- [Forum: usage too low even on Cursor Ultra (staff reply)](https://forum.cursor.com/t/grok-bot-usage-too-low-even-on-cursor-ultra/172584)
- [Forum: does Grok Bot consume Cursor quota? (staff reply)](https://forum.cursor.com/t/does-grok-bot-consume-cursor-quota/171742)
- [Forum: no warning before weekly usage spills into on-demand](https://forum.cursor.com/t/grok-bot-gives-no-warning-before-weekly-usage-spills-into-paid-on-demand/169679)
- [Forum: very high costs on the API](https://forum.cursor.com/t/anyone-used-grokbot-on-the-api-very-high-costs/169551)
- [Forum: usage-limit banner keeps coming back](https://forum.cursor.com/t/grok-bot-let-dismiss-of-weekly-usage-limit-banner-stick-x-keeps-coming-back/172013)
- [CellCog problems tracker](https://cellcog.ai/blog/grok-bot-problems/)
- [Cursor help: routines (usage warning)](https://cursor.com/help/grok-bot/routines)
- [Grok Bot changelog (usage screens in 0.59.0, 0.63.0 and the October 11 release)](https://x.ai/changelog/bot)
- [Forum: Cloud Agents started by Grok Bot bill to the team seat (staff reply, September 30)](https://forum.cursor.com/t/cloud-agents-by-grokbot-using-team-cloud-credits-instead-of-personal-usage/173419)
- [Forum: all Grok Bot routines failed to run, October 8 (staff replies; users report usage spent troubleshooting)](https://forum.cursor.com/t/all-grok-bot-routines-failed-to-run/174125)
- [Forum: is Grok Bot eating at Cursor usage? (staff replies fixing a display bug, then clarifying the new Ultra's shared pool, October 20)](https://forum.cursor.com/t/is-grok-bot-eating-at-cursor-usage-i-thought-it-had-its-seperate-usage/170990)

---

# Grok Bot shared computer: logins, passwords and context

> Every Bot shares one cloud computer and its logins. The open Secure Form password issue, why logins reset, why long chats cost more, and how to start fresh.

- Canonical page: https://www.grokbotwiki.com/guides/grok-bot-shared-computer
- Sources checked: 2026-10-29
- Evidence: Official architecture docs checked September 23, 2026 · official troubleshooting (last updated October 22), Cursor how-to help, x.ai/bot FAQ, Grok Bot changelog through 0.75.5 and forum staff replies (Secure Form, 1Password, X login, context threads) checked October 25, 2026 · changelog entry 0.77.0 and the Chrome extension forum thread read October 28, 2026 · changelog entry 0.78.1 read October 29 · community reports attributed, not reproduced. Suggested workflows have not been independently tested.
- Publisher: Grok Bot Wiki, an independent guide not affiliated with SpaceXSI, xAI or X.

## What is shared, officially

The overview is explicit: an account has one cloud computer, and Bots work on it with a browser, a file system, and a terminal. Bots sign into your apps with your real logins, and Cursor's help adds that once you sign in, every Bot on your account can use that sign-in until it expires. Approvals and ask-first rules govern what a Bot does, not which Bot can see what. A shared Bot link copies profile, skills, and routines, but recipients never get your computer, logins, or history. The FAQ on x.ai/bot, read October 25, puts it the same way: every Grok Bot shares one persistent cloud computer with its files, browser and logins, and isolation is per user, not per Bot.

So a Bot named Finance and a Bot named Marketing are two roles on one machine. Treat everything the computer is signed into as reachable by every Bot, and design your access accordingly. A Cursor staff member said on October 2 that letting an individual Bot keep its own browser session is something the team is actively working on; until it ships, [Is Grok Bot safe?](https://www.grokbotwiki.com/guides/is-grok-bot-safe) covers how to set up around the shared session.

Sources: https://docs.x.ai/grok-bot/overview, https://docs.x.ai/grok-bot/approvals-security-and-privacy, https://cursor.com/help/grok-bot/how-to, https://forum.cursor.com/t/grok-bot-ship-real-session-fences-bots-are-not-a-security-boundary/168476, https://x.ai/bot

## Why browser logins disappear

Community reports from mid-August describe Chrome profiles on the shared computer resetting daily, so sites that were signed in yesterday ask again today. The official troubleshooting page covers the symptom rather than the cause: take over, sign in manually, complete two-factor or CAPTCHA yourself, confirm the page loaded, and tell the Bot to continue. It also notes that some sites expire sessions or require verification for each sensitive action, which is not always avoidable even with a plugin. Never paste a password or a verification code into the chat.

Practical consequence: prefer plugins over browser sign-in wherever a plugin exists. Plugins are managed in Connect Apps (called Marketplace before version 0.67.0), not in Settings, and the Teams documentation says plugin OAuth tokens stay on Cursor's connector backend rather than in the shared browser, so they do not depend on a cookie that may expire. When a page needs you to type something yourself, the approvals guide says the Bot can show a Secure Form in the chat and fill your answers into the page, and the same page describes hardware security key support on macOS and Windows. For passwords, read the next section first: until Cursor ships a fix, type them on the computer yourself. Our [plugins guide](https://www.grokbotwiki.com/guides/grok-bot-plugins-mcp) covers installing and authorizing plugins.

X is a common case. In a forum thread opened August 16 that has passed 600 views, a user reported that after the Bot repeatedly submitted their X login from its computer, X answered We've temporarily limited your login there, and the limit did not lift after a day, while the same account signed in normally on their own devices. A Cursor staff member replied on August 17 that the team is aware of the issue and tracking it, and suggested trying a new agent and signing in yourself rather than asking the Bot to; another user later got in by fully closing Chrome on the Bot's computer and clicking the Google login themselves. Another user reported the same block on October 21 and asked for a workaround; none had been posted when we checked on October 25. The 0.75.5 release notes (October 23) offer a route around the browser: asking a Bot about your X account connects X through your linked X account, even if you removed the X plugin, and 0.71.2 says Bots now hit X's rate limit less often. Two 0.77.0 fixes (October 26) should also help logins last: the Bot's browser keeps site logins after its last window closes, and keys that apps on the computer store in the system keyring, such as Okta Verify's, now survive when the computer is recreated.

Some sites refuse the Bot's browser outright rather than forgetting it. A forum thread opened September 2 asking for a Grok Bot Chrome extension, past 750 views by October 28, collected examples: QuickBooks blocking a Bot after two weeks of reconciliations, geo-restricted stores that do not load, and marketplace accounts that demand a fresh sign-in several times a day. A Cursor staff member (deanrie) answered each. There is no extension and the Bot cannot control your local Chrome or your signed-in tabs, because everything runs on its cloud computer; the request has been passed on with no timeline. For a site that flags the cloud browser as automated traffic, use a connector or a custom MCP server where one exists, since those talk to the service's API and skip browser checks, and vote for a native connector where there is none. For a site that blocks by location or IP, open Settings → Computer in the desktop app and turn on Route traffic through this computer, so the Bot's browser traffic leaves through your own network and IP; staff said on October 26 it is usually the first thing to try, with no guarantee, because some sites block automated browsers whatever the IP. The docs' private networks page describes the setting. Since 0.78.1 (October 27), with Route traffic through this computer on, Settings says when the Bot's computer is asleep and that routing reconnects when it wakes, and pages no longer fail right away when only another host on them is refused. The same entry says that when the Bot's computer has been refusing saves, Reset and Recover keep the current disk instead of restoring an older backup, and that files already saved in another chat, such as Slack uploads to a Shared Bot (formerly Team Bot), save in the new chat instead of failing.

Sources: https://x.ai/changelog/bot#v0.78.1, https://docs.x.ai/grok-bot/troubleshooting, https://docs.x.ai/grok-bot/settings-and-notifications, https://docs.x.ai/grok-bot/teams-and-enterprises, https://docs.x.ai/grok-bot/approvals-security-and-privacy, https://docs.x.ai/grok-bot/private-networks, https://cellcog.ai/blog/grok-bot-problems/, https://forum.cursor.com/t/grok-bot-x-login-lock-limit-not-lifting/168541, https://forum.cursor.com/t/grok-bot-chrome-extension/170305, https://x.ai/changelog/bot#v0.75.5, https://x.ai/changelog/bot#v0.71.2, https://x.ai/changelog/bot#v0.77.0

## Passwords: skip the Secure Form for now (October 2026)

On October 5 a user reported that after the in-chat Secure Form filled a GitHub username and password into the Bot's browser, the snapshot the Bot took before clicking Sign in showed the password in plain text. That put the password into the session's tool output and transcript, although it never appeared in chat. A Cursor staff member replied the same day that a password filled by the Secure Form should not show up in a page snapshot, that the team was already working on a fix, and that the safest way to sign in until it ships is to do it yourself on the Bot's screen.

The Grok Bot 0.68.1 changelog on October 7 changes where Secure Forms fill, but it does not mention snapshot redaction, and neither do the notes for 0.69.0 to 0.70.2 on October 11. A user asked in the thread on October 7 to be told when it is fixed; Cursor had not posted an update when we checked on October 25. The later release notes do not mention snapshot redaction either: 0.71.2 (October 14) says Bots now ask for logins and other multi-field details on one Secure Form and that the form fills fields on more websites, including embedded frames, and 0.75.5 (October 23) adds a Vault in Settings where Bots save your logins, cards and contact info and fill them in to sign in or check out. Neither note says whether filled passwords are kept out of page snapshots, so treat the issue as open. Separately, staff described a known issue on September 30 where 1Password autofill on some login pages, including Instagram and Letterboxd, reports Filled while the password field stays empty, and on October 10 said the Google password step cannot be filled from 1Password on the full page either, not just in the popup. Their workaround is the same: when the Bot hands you the screen, type the password from 1Password yourself, finish two-step verification, and hand control back; the Bot's browser usually keeps the Google session afterwards.

One 1Password problem now has a server-side fix. In a 344-view thread about the 1Password connection failing with a message that the credential delivery outcome was unknown, a Cursor staff member (Colin) explained on September 27 that a single login with an extremely long website address, over 2,000 characters, was blocking the whole connection, and gave a workaround: shorten that item's website to the site's normal address, fully quit Grok Bot with Cmd+Q, and click Connect 1Password again, then delete the leftover Grok Bot agents service accounts each failed attempt created, under Developer, then Service Accounts on 1Password.com. On October 20 he wrote that this is now fixed on Cursor's side: the oversized address is skipped, it no longer blocks the connection or the background sync, and no Grok Bot update is needed. If the connector still fails, he asked for the exact message and roughly how many items the shared vault holds. Separately, 0.71.2 says screenshot, computer and browser actions keep working when you haven't connected 1Password.

1. When a Bot asks for a password, choose Open the screen instead of filling the Secure Form. Since the October 11 release notes, full-screen computer view opens in Watching; press Take control before you type. If the computer is asleep, click the Computer is asleep preview to wake it in place (0.71.2 and later; older versions have a Wake button on the Computer tab).
2. Type the password on the Bot's computer yourself and press Sign in yourself, then hand control back. Once the page moves past the login form, the password is no longer in the page for the Bot to read.
3. Treat recovery codes, API keys and other secrets the same way: type them on the screen, never in chat.
4. If you already entered a password through the Secure Form, change it, as the person who reported the issue did.
5. Watch the forum thread for Cursor's confirmation of a fix before going back to the form, or to the new Vault, for passwords.

Sources: https://forum.cursor.com/t/grok-bot-browser-snapshot-shows-a-password-filled-by-the-secure-form-requestuserform-in-plain-text/173748, https://forum.cursor.com/t/grok-bot-shared-1password-autofill-says-filled-but-password-stays-empty-instagram/173365, https://forum.cursor.com/t/grok-bot-wont-login-to-google-account-using-1password/173423, https://forum.cursor.com/t/grokbot-1password/173142, https://x.ai/changelog/bot, https://x.ai/changelog/bot#v0.71.2, https://x.ai/changelog/bot#v0.75.5, https://docs.x.ai/grok-bot/approvals-security-and-privacy

## Long threads, and how to start fresh

A Bot's conversation grows without a visible context meter and without a clear or compact option. Cursor staff said in September that every turn re-reads that conversation and the product only summarizes automatically near the model's limit, so a long-running chat costs more on every reply. A forum thread from September describes memory writes failing across a fleet while a state snapshot was cut short.

Start fresh instead of letting one thread grow. Cursor staff recommend a new chat per task, with standing instructions kept in the Bot's profile so they carry over. Since 0.71 the + in the sidebar opens Create new Bot rather than a new chat, which staff said on October 20 is intentional; to open a new chat with the same Bot, press Ctrl+Shift+N, or Ctrl+K and run New group chat, then select that one Bot and press Enter. A Bot made with Create new Bot does not get the old Bot's own memory or routines; it sees only shared memory. To reset a Bot entirely, Duplicate it: the official docs say the copy keeps the profile, settings, enabled skills, routines, and avatar, but not conversation history, learned memory, or attachments, so paste a short handoff summary as its first message. Hide the original rather than deleting it until you are sure: the 0.75.2 release notes say deleting a Bot permanently erases its conversations, memory, routines and attachments and removes its Slack app.

Memory carries further than it used to. The 0.75.2 notes say what a personal Bot saves to memory in one chat is now remembered in all your chats with it. On October 19 and 20 Cursor staff (deanrie) answered a user who saw earlier turns turning up in a new group chat: a Bot's own account of its context is not a reliable signal, because its durable memory is shared across its chats, and staff could neither confirm nor rule out that chat history has started merging across chats, which the team is checking. There is no screen to view or edit a Bot's memory yet; staff suggest asking the Bot to print its memory profile and memory log and delete specific entries, and remember that every Bot can see shared memory.

A forum thread opened August 13 and past 1,500 views, titled a request to prune or compact a Bot's context without creating a new Bot, describes exactly this pain in detail: a fleet operator argued each Bot is one unbounded thread, so obsolete tool dumps and agent-to-agent pings stay in context forever, and the only documented workaround is spawning another Bot, which splits memory and inflates the roster. Cursor staff (deanrie) replied on August 20 and again on September 23 and 30 that durable state already lives apart from the transcript and survives a reset, that a new chat on the same Bot starts with a clean working set (a point staff said on October 20 they are re-confirming), and that an explicit new-session-with-archive control, a manual Compact, and a visible working-set meter are still missing; on October 20 staff said they remain on the team's radar with no timeline. Until those ship, a community workaround from the same thread is to give each long-lived Bot a durable notes file that a routine rewrites at the end of every session, so a reset or Duplicate can point the fresh chat at that file instead of losing continuity; a notes file that stays small while the transcript keeps growing is also a rough signal that tokens are going to large tool output rather than real state.

There is still no one-click export either. A September thread asked for the best way to back up each Bot's individual and shared memory, separate from chat history. Cursor staff (mohitjain) replied that a Bot's durable state lives as plain text files on its own computer that it can zip and hand back: ask a Bot to copy its complete memory, routines and connectors into a backup folder, zip it, and send the zip as a chat attachment, then ask a Chief-of-Staff-style Bot to do the same for shared memory and skills. A reply in the same thread (izgorodin) cautioned against folding that raw backup straight into SKILL.md files, since memory is timestamped, scoped state that can go stale, while a skill should stay a reviewed, stable procedure; staff agreed, and recommended exporting the raw memory as its own zip first and promoting only stable material into skills afterward. The traffic now runs the other way too: 0.77.0 (October 26) adds Import Memory to Grok Bot in Settings, which brings your preferences and context from another AI assistant into your primary Bot, but the changelog describes no export, so the zip procedure above is still the backup route.

- [ ] Nothing signed into the shared computer would be catastrophic if any Bot touched it.
- [ ] Passwords are typed on the Bot's screen yourself (Open the screen), not through the Secure Form, until Cursor confirms the snapshot fix.
- [ ] Plugins are used where they exist; browser logins are the fallback.
- [ ] Local computer execution stays disabled unless a task needs it.
- [ ] New tasks start in a fresh chat, standing rules live in the Bot's profile, and finished Bots are hidden rather than deleted.
- [ ] Long-lived Bots keep a durable notes file a routine rewrites each session, since explicit compact and new-session controls are not shipped yet.
- [ ] Important Bots have had their memory, routines and connectors zipped and backed up at least once, since there is still no one-click export.

Sources: https://docs.x.ai/grok-bot/bots, https://x.ai/changelog/bot#v0.77.0, https://forum.cursor.com/t/grok-bot-context-window-size-and-token-accumulation-logic-in-pro/171540, https://forum.cursor.com/t/1-500-in-one-week-running-a-grok-bot-fleet-expected-or-a-bug/172705, https://forum.cursor.com/t/grok-bot-update-state-memory-writes-fail-fleet-wide-brain-docs-snapshot-was-cut-short-before-completing/171895, https://forum.cursor.com/t/grok-bot-prune-compact-an-agent-s-context-without-creating-a-new-bot/168333, https://x.ai/changelog/bot#v0.75.2, https://forum.cursor.com/t/best-way-to-export-memory/170714

## Quick answers

### Is it safe to enter a password in the Grok Bot Secure Form?

Not for passwords at the moment. On October 5 Cursor staff confirmed a report that a password filled by the in-chat Secure Form appeared in plain text in the page snapshot the Bot took before signing in, which puts it in the session's tool output and transcript. Staff said a fix is in progress and, until it ships, advise choosing Open the screen, typing the password yourself and pressing Sign in yourself. As of October 25 Cursor had not posted a fix in the thread, and the release notes from 0.69.0 through 0.75.5 (October 11 to 23) do not mention one, although 0.71.2 moved logins onto a single Secure Form and 0.75.5 added a Vault that saves and fills logins. If you already entered a password through the form, change it.

### Do my Bots have separate computers?

No. The official overview describes one persistent cloud computer per account, with its browser, file system, and terminal shared by every Bot you create, and the FAQ on x.ai/bot, read October 25, says isolation is per user, not per Bot. Separate Bots are separate conversations and roles, not separate machines or separate logins.

### Can I use one Bot for sensitive accounts and keep the others away from them?

Not by using Bot boundaries. Any Bot on the account can reach a browser session another Bot signed into. If a login must stay isolated, keep it off the shared computer entirely or use a second account.

### Can I clear a Bot's context or start a fresh session?

You cannot clear or compact a conversation; Cursor staff said in September that a Bot re-reads its conversation every turn and only auto-summarizes near the model's limit, and on October 19 that there is still no supported way to shrink a Bot's working set other than Duplicate or Delete. You can start fresh two ways. Since 0.71, staff said on October 20, the + in the sidebar intentionally opens Create new Bot; to start a new chat with the same Bot, press Ctrl+Shift+N, or Ctrl+K and run New group chat, select that one Bot and press Enter. Staff had said on September 23 that such a chat starts with a clean working set, but on October 20, after a user reported old turns carrying over, said they no longer want to claim that until the team confirms it. Or use Duplicate: the official docs say the copy keeps the profile, settings, enabled skills, routines, and avatar but not conversation history, learned memory, or chat attachments. A forum thread open since August 13 tracks the request for an explicit same-Bot new session, a manual Compact and a working-set meter; staff said again on October 20 that these are on the team's radar with no timeline.

## Sources

- [Grok Bot overview](https://docs.x.ai/grok-bot/overview)
- [Grok Bot changelog: 0.78.1 (Route traffic sleep notice, Reset and Recover keep the current disk, October 27)](https://x.ai/changelog/bot#v0.78.1)
- [Grok Bot changelog: 0.77.0 (browser keeps site logins, Import Memory, Route traffic fixes, October 26)](https://x.ai/changelog/bot#v0.77.0)
- [Forum: Grok Bot Chrome extension request (staff replies on sites that block the cloud browser, September 12 to October 26)](https://forum.cursor.com/t/grok-bot-chrome-extension/170305)
- [Connect to private networks (Route traffic through this computer)](https://docs.x.ai/grok-bot/private-networks)
- [Approvals, security and privacy](https://docs.x.ai/grok-bot/approvals-security-and-privacy)
- [Official troubleshooting](https://docs.x.ai/grok-bot/troubleshooting)
- [Create and manage Bots (Duplicate)](https://docs.x.ai/grok-bot/bots)
- [Settings: plugins live in Marketplace](https://docs.x.ai/grok-bot/settings-and-notifications)
- [Teams and enterprises: plugin tokens](https://docs.x.ai/grok-bot/teams-and-enterprises)
- [Forum: context size and token accumulation (staff reply)](https://forum.cursor.com/t/grok-bot-context-window-size-and-token-accumulation-logic-in-pro/171540)
- [Forum: about $1,500 in one week running a Bot fleet (staff reply)](https://forum.cursor.com/t/1-500-in-one-week-running-a-grok-bot-fleet-expected-or-a-bug/172705)
- [CellCog problems tracker](https://cellcog.ai/blog/grok-bot-problems/)
- [Forum: memory writes fail fleet-wide](https://forum.cursor.com/t/grok-bot-update-state-memory-writes-fail-fleet-wide-brain-docs-snapshot-was-cut-short-before-completing/171895)
- [Forum: prune/compact an agent's context without creating a new Bot (1,590 views, staff replies through October 20)](https://forum.cursor.com/t/grok-bot-prune-compact-an-agent-s-context-without-creating-a-new-bot/168333)
- [Forum: best way to export memory (staff backup procedure, September 7)](https://forum.cursor.com/t/best-way-to-export-memory/170714)
- [Forum: password filled by the Secure Form shown in a page snapshot (staff reply, October 5)](https://forum.cursor.com/t/grok-bot-browser-snapshot-shows-a-password-filled-by-the-secure-form-requestuserform-in-plain-text/173748)
- [Forum: 1Password autofill says Filled but the password stays empty (staff reply, September 30)](https://forum.cursor.com/t/grok-bot-shared-1password-autofill-says-filled-but-password-stays-empty-instagram/173365)
- [Grok Bot changelog](https://x.ai/changelog/bot)
- [Forum: Bots are not a security boundary (staff reply, October 2)](https://forum.cursor.com/t/grok-bot-ship-real-session-fences-bots-are-not-a-security-boundary/168476)
- [Forum: Grok Bot will not log in to Google with 1Password (staff replies, September 30 and October 10)](https://forum.cursor.com/t/grok-bot-wont-login-to-google-account-using-1password/173423)
- [Cursor help: how-tos (shared sign-ins)](https://cursor.com/help/grok-bot/how-to)
- [Forum: Grokbot and 1Password, long website addresses (staff workaround September 27, server-side fix October 20)](https://forum.cursor.com/t/grokbot-1password/173142)
- [Forum: X login limited on the Bot's computer (630 views, staff reply August 17, new reports October 21)](https://forum.cursor.com/t/grok-bot-x-login-lock-limit-not-lifting/168541)
- [Grok Bot changelog 0.71.2 (October 14): Secure Form, wake in place, 1Password-free actions](https://x.ai/changelog/bot#v0.71.2)
- [Grok Bot changelog 0.75.2 (October 22): shared memory across a Bot's chats, deleting a Bot](https://x.ai/changelog/bot#v0.75.2)
- [Grok Bot changelog 0.75.5 (October 23): Vault, X through your linked account](https://x.ai/changelog/bot#v0.75.5)
- [Grok Bot FAQ on x.ai/bot (one shared computer, isolation per user)](https://x.ai/bot)

---

# Grok Bot routines not running: fixes, limits and webhooks

> Routines that never fire, run late or show Failed, webhook routines with no POST URL. The official checks, the limits, and the October 8 scheduler incident.

- Canonical page: https://www.grokbotwiki.com/guides/grok-bot-routines-not-running
- Sources checked: 2026-10-29
- Evidence: Official troubleshooting rechecked October 25, 2026 (last updated by Cursor October 22) · Cursor's routines help, including its new hourly run limits, rechecked October 25 · Cursor status history and Grok Bot changelog through 0.75.5 (October 23) checked October 25 · changelog entries 0.77.0 (October 26) and 0.78.1 (October 27) read October 28 and 29 · fixes as described in release notes, not tested by us · user reports attributed, not reproduced · approval expiry rechecked in Cursor's how-to help and the official approvals docs October 29, 2026. Suggested workflows have not been independently tested.
- Publisher: Grok Bot Wiki, an independent guide not affiliated with SpaceXSI, xAI or X.

## Run the official checklist first

The official troubleshooting entry for a routine that did not run lists the things to verify before anything else. Most missed runs come down to one of these.

Four changes in Grok Bot 0.77.0 (October 26) touch this checklist. Approval cards raised by unattended work now stay open for 30 minutes instead of 10, in the app and in Slack, so a routine that needs you has three times as long before its action is dropped. Background work that hits a connector you were signed out of stops calling it and tells you to reconnect, instead of failing quietly; when background work needs one of your apps, the Bot asks with an allow card in the app, or Allow once and Skip in Slack. Slack routines that listen for messages now see images on the message that started them. And if your plan does not include routines, the Bot now names the plan that does, which is the quickest way to tell a missing feature from a broken one.

0.78.1 (October 27) adds three fixes worth knowing. Routines made in a new Bot's first chat now run in your time zone instead of UTC, so a routine that fired hours off from a brand-new Bot has a release-note explanation; check its schedule after updating. Clicking a webhook routine opens its details, including the webhook URL. And when a Shared Bot (formerly Team Bot) routine needs one of your connectors, it asks in the routine's Slack thread and tags you, so look for the ask there before assuming the run failed.

- [ ] The routine is enabled, not just saved.
- [ ] The schedule and time zone are what you intended.
- [ ] The Bot that owns the routine still exists and was not deleted or recreated.
- [ ] Every plugin the routine needs is still authenticated.
- [ ] The computer can reach the source system the routine reads from; a stuck or unreachable computer silently skips scheduled work.
- [ ] Usage or account access has not been paused; an exhausted allowance with on-demand disabled stops routines.
- [ ] For an event-triggered routine, the source channel, repository, and matching rule are still valid.
- [ ] Recent run history has been checked for a failure, including Automation run rate limit exceeded (see the hourly limits below).
- [ ] A manual Test run is tried only with a safe input: the troubleshooting page, last updated October 22, notes Test run can perform real external actions, not a dry run.
- [ ] The app is up to date: since 0.71.2 a routine that needs a site sign-in asks you in chat instead of quietly stopping, and since 0.75.2 a signed-out connector shows a Reconnect card in the chat.

Sources: https://x.ai/changelog/bot#v0.78.1, https://docs.x.ai/grok-bot/troubleshooting, https://x.ai/changelog/bot#v0.71.2, https://x.ai/changelog/bot#v0.75.2

## Routine failures on October 8, 9, 13 and 19

From about 10 AM ET on October 8, scheduled routines across many accounts started late, were marked Failed, or never started, into October 9. Cursor staff said it happened during a period of very high demand, that nothing was wrong with people's Bots, settings or computers, and that direct messages to Bots were not affected. Routines briefly recovered that evening and were then held back again. The status page did not list it; staff said a resolved notice there that evening referred to a different issue.

Staff explained the odd patterns people saw. While one run is waiting, the routine's next scheduled slots are skipped rather than queued, so a five-minute routine showed gaps of one and a half to two hours. A run that looked early was the previous slot's run finally starting. A backup routine set a few minutes after the primary waits in the same queue, so it gives no protection. Missed runs are not replayed.

On October 13 a Cursor staff member posted the all-clear in the main thread: the October 8 problem had been resolved on October 9, routines had been held back again for a few hours on the morning of October 13 (US time), and they had been going through since about 16:00 UTC. Staff added that some routines may still start later than scheduled during busy periods, which Cursor is tracking. Afterwards one user reported a weekly routine due at 18:00 UTC that never fired and others starting 13 to 24 minutes late; staff asked anyone whose routine still fails outright to reply with its name and due time.

Event-triggered routines had their own failure the same day. Cursor's status page says that between 10:52 AM and 1:29 PM PT on October 13 (17:52 to 20:29 UTC) many routines started by webhooks, Slack, git, email and Linear events did not run. Webhook callers may have seen HTTP 400 with Automation run rate limit exceeded; other triggers failed silently. Cursor said users' own usage did not cause it, and that events sent in that window were not processed and will not be retried. The notice was posted after the incident ended.

Routines were delayed once more on October 19. Cursor's status page reported a Grok Bot degradation where routines may be delayed from 16:15 to 17:21 UTC, with a fix in place at 17:10. The notice did not say whether delayed runs were dropped, so check anything due in that hour.

1. Leave affected routines switched on; staff said pausing, resuming, editing the schedule, copying or recreating them does not help. If you did any of that while troubleshooting, check the routines you want are switched back on.
2. For anything time-sensitive, message the Bot and ask it to run the routine now.
3. Resend any webhook call, Slack message, email or other event that should have started a routine between 17:52 and 20:29 UTC on October 13.
4. Avoid long troubleshooting sessions with your Bots during an incident; several users said it used much of their weekly usage.
5. Check the forum's grok-bot tag as well as the status page: the October 8 incident never got a status entry, and the October 13 trigger notice appeared only after it was over.

Sources: https://forum.cursor.com/t/all-grok-bot-routines-failed-to-run/174125, https://status.x.ai/history?incident=grok-bot%2Fbg1b759jsjqf, https://status.x.ai/history?incident=grok-bot%2F48bg6xqptq72, https://forum.cursor.com/t/grok-bot-routines-failing-or-running-hours-late-across-several-bots-since-10-20-am-et-oct-8/174131, https://forum.cursor.com/t/grok-bot-scheduled-routines-firing-late-early-or-not-at-all-all-day-oct-8-primary-backup-both-missed/174142, https://forum.cursor.com/t/grok-bot-routines-dont-auto-run-on-schedule/170358

## The limits that look like bugs

Two documented numbers explain a lot of confusion. A Bot can own up to 50 routines, and only the 20 most recent run records are kept per routine. If you inspect history after a busy routine has run more than twenty times, earlier runs are simply gone. Keep your own log for anything you need to audit.

There are hourly run limits too. Cursor's routines help says your routines can run up to 300 times an hour in total and each routine up to 200 times an hour, figures the 0.75.5 release notes (October 23) describe as raised from 100 in total. A run past either limit fails with Automation run rate limit exceeded and is not retried, so rerun it with Test or resend the webhook call, and ask the Bot to narrow the trigger or widen the schedule if one routine keeps hitting the limit. The help page adds that some runs fail with the same error because of a limit shared by all Grok Bot routines, even when yours run less often; Cursor calls that a known issue and says it will update the article once it no longer affects routines.

A routine that seems to have done nothing may have left a draft. The 0.75.5 notes say emails and Slack messages you ask a Bot to send go out once Auto-review allows them, while sends on routine and other turns still wait as drafts. Check the Bot's drafts before assuming the run failed.

The docs also say Grok Bot may ask whether to keep routines running after a long period away and pause them if there is no response. People who set up a routine and then stop opening the app find it paused, not broken. Open the app periodically or expect that prompt.

Routine management still leans on desktop: the mobile guide says editing schedules and test runs require the desktop app, and Cursor's routines help puts Test on desktop only, while the phone shows each recent run as Running, Succeeded or Failed with the reason. The help adds behaviours that look like bugs: a new routine waits for its next scheduled time rather than running when it is created; schedules follow the time zone under Settings → General → Bot → Timezone, where Auto-detect follows the computer you are on; and an hourly schedule, a short interval or a Slack trigger on a busy channel can use a week of usage in a day; see [the usage limit guide](https://www.grokbotwiki.com/guides/grok-bot-weekly-usage-limit).

Two more catch unattended routines. Cursor's help and the official docs, checked October 29, say an approval raised by work that started without you, such as a routine, expires after about 30 minutes, and the action then does not run; keep routine steps inside your Allow automatically rules or expect to answer quickly. Since 0.75.2 an expired approval leaves a chat line naming what expired, and since 0.71.2 a routine that needs to sign in to a site asks you in chat at that step instead of quietly stopping. And a routine that runs commands on your own Mac or PC needs that computer connected: Cursor staff said in October that the desktop app pauses the local connection when the screen locks, the computer sleeps, or the Grok Bot window has not been the active window for about 10 minutes, and does not resume it on its own when a scheduled job starts. Click into the Grok Bot window a few minutes before such jobs.

A forum report traced this to its root cause: a Cursor staff member (Colin) explained on October 5 that it is a deliberate power-saving behavior in recent desktop versions, that the local helper only restarts once someone is back at the Mac (an unlock, or bringing the Grok Bot window forward), and that a Bot's own request for the machine from another device does not bring the helper back yet. The reporter's watchdog relaunched the app 25 times with the screen locked; the helper came back only twice. Later replies in the same thread describe the identical drop on Windows, and on Mac Studio and Mac mini machines deliberately run as always-on, unattended agent hosts with sleep and App Nap already disabled, so the fix is not a local power setting. There is no official workaround yet beyond keeping the Grok Bot window focused; if a routine depends on local execution, treat an always-locked or always-backgrounded machine as unreliable until Cursor ships the fix. On October 13 another Cursor staff member (deanrie) said they could not confirm that 0.70.2 fixes it and that there is still no setting to turn it off; staff called one user's alternative, running Tailscale on the machine so the Bot can reach it without the app, a valid workaround. Another user had their Bot bring the Grok Bot window forward after starting each job, which staff said amounts to the recommended workaround.

Grok Bot 0.71.2 (October 14) changed the surrounding behaviour without announcing an end to that pause: when your computer sleeps, Bots treat it as disconnected within two minutes and say so right away; after a Wi-Fi, VPN or other network change they can run tasks on it straight away; and if work is meant for one of your computers that is offline, the Bot tells you instead of running it on another computer without asking. In the forum, one user wrote on October 20 that the drops had stopped for them from a version just before 0.72.0 across three Windows PCs, and another had said on October 14 that 0.70.2 fixed it on a Mac mini. Update first, then keep the window-focus workaround for any routine that cannot afford a miss.

Sources: https://docs.x.ai/grok-bot/skills-routines-and-automations, https://docs.x.ai/grok-bot/settings-and-notifications, https://cursor.com/help/grok-bot/routines, https://cursor.com/help/grok-bot/how-to, https://x.ai/changelog/bot#v0.71.2, https://x.ai/changelog/bot#v0.75.2, https://x.ai/changelog/bot#v0.75.5, https://forum.cursor.com/t/grok-bot-0-68-1-on-mac-mini-local-computer-drops-while-idle-and-does-not-self-heal/174109, https://forum.cursor.com/t/grok-bot-0-68-1-macos-mac-shows-disconnected-while-awake-and-in-use-local-computer-doesnt-reconnect-until-app-is-focused/174223, https://forum.cursor.com/t/grok-bot-thinks-my-computer-is-offline-or-sleeping-but-it-is-not/174267, https://forum.cursor.com/t/grok-bot-0-66-0-macos-local-exec-daemon-gets-sigterm-on-an-unattended-locked-mac-and-is-not-restored-when-the-bot-needs-the-machine/173728

## Schedules that never fire

The main forum thread on routines that do not auto-run, opened September 2 and now past 20 replies, turned out to be server-side problems rather than user error. Cursor staff said the reporter's routines had fired at every slot but sat in a queue, starting 10 to 37 minutes late, and some runs finished without posting anything to the chat, so it looked as if nothing ran. Staff also said the platform a routine was created on, and edits to the Bot's instructions, do not affect its schedule.

On September 16 staff said a change rolled out the previous evening (UTC) gives each routine a reserved slot a few minutes out, so the silent skips should stop, although runs can still start a few minutes late at the busiest hours. On September 24 staff said they had added capacity and routines were starting within a few minutes of schedule, against 20 to 40 minutes during US mornings earlier that week; users kept reporting late or missed one-off runs afterwards. Separately, schedule edits or switch-offs made between September 4 and 8 could keep running on the old settings; staff asked people to re-save any routine that still looks wrong. Cursor's status page also recorded dropped routine trigger fires on September 3 to 4, and routines due during the October 3 incident did not run; [Is Grok Bot down?](https://www.grokbotwiki.com/guides/is-grok-bot-down) lists every incident with its times.

1. Open the routine and confirm enabled, schedule, and time zone. Since the October 11 release (0.69.0 to 0.70.2), the Bot sums up what a routine does and who receives the result when you save it, and each run delivers there; read that summary to confirm the routine posts where you expect.
2. Check recent run history for a late start or a run that finished without posting; have the routine always post a one-line result so a quiet run is visible.
3. Re-save the routine if its schedule or on/off state was changed in early September.
4. Run it once manually with a harmless input and watch the computer view.
5. If a run still starts more than about 15 minutes late, report the routine name, scheduled time, and actual start time in the forum thread, as staff requested.

Sources: https://forum.cursor.com/t/grok-bot-routines-dont-auto-run-on-schedule/170358, https://status.x.ai/history?incident=grok-bot%2Fkt27kgrd7pf1, https://docs.x.ai/grok-bot/troubleshooting, https://x.ai/changelog/bot

## Webhook routines with no POST URL

Event routines can be triggered by integrations such as Slack messages or GitHub notifications, and by a webhook. A 29-reply thread began with the Windows 0.47.0 desktop app showing no POST URL and no key for a webhook routine, so nothing external could call it. Cursor staff confirmed it affected Mac and mobile too: newer Bots keep their routines on the server, and the apps were not fetching the webhook fields. Staff said the fix shipped in Grok Bot 0.53.0 for Windows, Mac, and Linux on September 16.

Update the desktop app, click the Bot's name, find Routines on the Details tab, and open the webhook routine; Cursor's help says its Webhook section shows POST to (the URL), key, and header (the full Authorization: Bearer header), each copied with a click. The mobile app does not show them. A 200 response means Grok Bot accepted the call and started a run, not that the Bot finished; any other response means no run started, so check the routine is not paused and the key is current. Do not try to guess a URL, and keep the key out of chat and shared templates.

Not everyone sees those fields. In a 450-view forum thread about the redesigned desktop Details pane, where Cursor staff said on October 9 that the simpler pane was an intentional redesign, one user reported on October 11 that each routine showed only its name, schedule and switch, with no saved prompt or webhook details. Cursor's routines help still describes the Instruction and Webhook fields. If they are missing for you, update the app and add your version to that thread rather than recreating the routine. The 0.75.2 release notes (October 22) say a webhook routine's menu now shows its URL and key, with the key hidden until you reveal it, and Cursor's routines help, rechecked October 25, still lists the Webhook section.

Sources: https://forum.cursor.com/t/grok-bot-macos-unable-to-see-or-edit-bot-instructions-or-skills-on-desktop/173803, https://forum.cursor.com/t/desktop-grok-bot-webhook-routine-shows-no-post-url-crsr-key-windows-0-47-0/171324, https://docs.x.ai/grok-bot/skills-routines-and-automations, https://cursor.com/help/grok-bot/routines, https://x.ai/changelog/bot#v0.75.2

## Write routines that fail loudly

The official guidance recommends a no-data and stale-data policy for every routine: say what should happen when a source is missing. The example is 'If the source data is unavailable, report the failure instead of using old data.' A routine that reports a failure is one you notice; a routine that quietly reuses yesterday's numbers is one you discover weeks later.

Editorial template (replace placeholders and review access before running):

```text
Every weekday at 8:00 AM in my time zone, open the attached tracker and produce a five-line summary of changes since the last run. If the tracker is unreachable, empty, or unchanged, send a one-line message saying so and do not reuse a previous summary. Do not edit the tracker. Return the summary for my review.
```

Sources: https://docs.x.ai/grok-bot/skills-routines-and-automations

## Quick answers

### Which versions fixed routines that stopped quietly?

Going by the release notes: since 0.71.2 (October 14), a routine that needs to sign in to a site asks you in chat at that step instead of quietly stopping. Since 0.75.2 (October 22), a routine that hits a signed-out connector shows that connector's Reconnect card in the chat, at most once a day; pausing and resuming keeps your last choice even when you tap from two devices; a routine's result still reaches you if you send a message before the Bot finishes handing it off; and an approval you don't answer in time leaves a chat line naming what expired. 0.75.5 (October 23) raised the hourly run limits. 0.78.1 (October 27) fixes two more: routines made in a new Bot's first chat run in your time zone instead of UTC, and clicking a webhook routine opens its details, including the webhook URL. Update the app first, then check the routine.

### Why did my routines fail or run hours late on October 8 or 13?

A problem on Cursor's side both times. Staff said that from about 10 AM ET on October 8, during very high demand, scheduled routines were held back, started late or were marked Failed, while messaging Bots directly kept working; that was resolved on October 9. On the morning of October 13 (US time) routines were held back again for a few hours, and staff said they had been going through since about 16:00 UTC. Missed runs are not replayed, so ask the Bot to run urgent ones by hand, and check that any routine you paused or recreated while troubleshooting is switched back on.

### My routine failed with Automation run rate limit exceeded. Did I do something wrong?

Possibly not. Cursor's routines help, rechecked October 25, says routines have hourly limits: your routines can run up to 300 times an hour in total and each routine up to 200 times an hour (0.75.5 raised the total from 100), and a run past either limit fails with that error. The same page says some runs also fail with it because of a limit all Grok Bot routines share, even when yours run less often; Cursor calls that a known issue its engineers are fixing. On October 13 between 10:52 AM and 1:29 PM PT (17:52 to 20:29 UTC) many event-triggered routines failed this way and your own usage did not cause it. Failed runs are not retried automatically, so rerun the routine with Test or send the webhook call again.

### How many routines can a Bot have?

The official docs say a Bot can own up to 50 routines, and the app keeps the 20 most recent run records for each routine. Older runs disappear from history, which can look like the routine never ran.

### Why did my routines pause on their own?

The docs say Grok Bot may ask whether to keep routines running after a long period away, and pause them if there is no response. If you have been away from the app, open it and answer that prompt before assuming a bug.

### My webhook routine shows no POST URL. Is that normal?

It was a known bug, not a configuration mistake, and it is fixed on desktop. Cursor staff said newer Bots keep routines on the server and the apps were not showing the webhook URL, key, or Authorization header on any platform; recreating the routine did not help. On September 16 staff said Grok Bot 0.53.0 fixed it on Windows, Mac, and Linux. Update the desktop app and open the webhook routine from the Bot's Routines list. The mobile app does not show these fields yet, so copy them from desktop.

## Sources

- [Grok Bot changelog: 0.78.1 (routine time zone in a new Bot's first chat, webhook details, Team Bot routines ask in Slack, October 27)](https://x.ai/changelog/bot#v0.78.1)
- [Grok Bot changelog: 0.77.0 (30-minute approval cards, signed-out connectors, plan without routines, October 26)](https://x.ai/changelog/bot#v0.77.0)
- [Skills and routines](https://docs.x.ai/grok-bot/skills-routines-and-automations)
- [Official troubleshooting](https://docs.x.ai/grok-bot/troubleshooting)
- [Grok Bot for Mobile](https://docs.x.ai/grok-bot/mobile)
- [Forum: macOS local-exec daemon gets SIGTERM on an unattended, locked Mac (staff explanation, 310 views)](https://forum.cursor.com/t/grok-bot-0-66-0-macos-local-exec-daemon-gets-sigterm-on-an-unattended-locked-mac-and-is-not-restored-when-the-bot-needs-the-machine/173728)
- [Forum: routines don't auto-run on schedule (staff explanation and September 16 fix)](https://forum.cursor.com/t/grok-bot-routines-dont-auto-run-on-schedule/170358)
- [Forum: webhook routine shows no POST URL (fixed in desktop 0.53.0)](https://forum.cursor.com/t/desktop-grok-bot-webhook-routine-shows-no-post-url-crsr-key-windows-0-47-0/171324)
- [Cursor status: degraded routine triggers, September 3 to 4](https://status.x.ai/history?incident=grok-bot%2Fkt27kgrd7pf1)
- [Cursor help: routines](https://cursor.com/help/grok-bot/routines)
- [Cursor help: how-tos (approval expiry)](https://cursor.com/help/grok-bot/how-to)
- [Forum: all Grok Bot routines failed to run (staff replies, October 8 to 13)](https://forum.cursor.com/t/all-grok-bot-routines-failed-to-run/174125)
- [Cursor status: Grok Bot routines not triggering, October 13](https://status.x.ai/history?incident=grok-bot%2Fbg1b759jsjqf)
- [Settings: Bot timezone](https://docs.x.ai/grok-bot/settings-and-notifications)
- [Grok Bot changelog (routine summary on save, 0.69.0 to 0.70.2)](https://x.ai/changelog/bot)
- [Forum: unable to see or edit Bot instructions on desktop (staff reply, October 9; routine details reported missing October 11)](https://forum.cursor.com/t/grok-bot-macos-unable-to-see-or-edit-bot-instructions-or-skills-on-desktop/173803)
- [Forum: routines failing or running hours late since October 8 (staff reply)](https://forum.cursor.com/t/grok-bot-routines-failing-or-running-hours-late-across-several-bots-since-10-20-am-et-oct-8/174131)
- [Forum: routines firing late, early or not at all on October 8 (staff reply)](https://forum.cursor.com/t/grok-bot-scheduled-routines-firing-late-early-or-not-at-all-all-day-oct-8-primary-backup-both-missed/174142)
- [Forum: Mac shows disconnected until the app is focused (staff reply, October 9)](https://forum.cursor.com/t/grok-bot-0-68-1-macos-mac-shows-disconnected-while-awake-and-in-use-local-computer-doesnt-reconnect-until-app-is-focused/174223)
- [Forum: Bot thinks my computer is offline or sleeping (staff reply, October 10)](https://forum.cursor.com/t/grok-bot-thinks-my-computer-is-offline-or-sleeping-but-it-is-not/174267)
- [Cursor status: Grok Bot routines delayed, October 19](https://status.x.ai/history?incident=grok-bot%2F48bg6xqptq72)
- [Forum: Mac mini local computer drops while idle (user reports through October 24)](https://forum.cursor.com/t/grok-bot-0-68-1-on-mac-mini-local-computer-drops-while-idle-and-does-not-self-heal/174109)
- [Grok Bot changelog 0.71.2 (October 14): routines ask for sign-in instead of quietly stopping](https://x.ai/changelog/bot#v0.71.2)
- [Grok Bot changelog 0.75.2 (October 22): Reconnect cards, pause and resume, webhook key](https://x.ai/changelog/bot#v0.75.2)
- [Grok Bot changelog 0.75.5 (October 23): run limits raised, routine sends wait as drafts](https://x.ai/changelog/bot#v0.75.5)

---

# Grok Bot sign-in or authentication error on Windows: fixes

> Authentication error after updating, logging out and clearing cache? Update Grok Bot's Computer, check Legacy Privacy Mode and SSO. What Cursor staff said.

- Canonical page: https://www.grokbotwiki.com/guides/grok-bot-sign-in-error-windows
- Sources checked: 2026-10-29
- Evidence: Official troubleshooting (last updated by Cursor October 22), X Subscription sign-in and sign-in domain docs (last updated October 5) and Cursor's plans and how-to help rechecked October 25, 2026 · Grok Bot changelog through 0.75.5 (October 23) and forum staff replies checked October 25 · changelog entry 0.78.1 (October 27) read October 29 · fixes as described in release notes, not tested by us · user reports attributed, not reproduced. Suggested workflows have not been independently tested.
- Publisher: Grok Bot Wiki, an independent guide not affiliated with SpaceXSI, xAI or X.

## The official sign-in checks

Grok Bot signs you in through the browser and then returns to the app. The troubleshooting page, last updated October 22, covers the ways that hand-off fails.

Update first if you can. The 0.75.2 release notes (October 22) say browser sign-in now waits up to 20 minutes and offers Copy link, Reopen link resumes the same sign-in instead of starting over, the app asks you to check your connection when sign-in can't connect instead of saying it stopped waiting for your browser, the desktop app connects directly unless you have turned on a system proxy, which fixes loading behind some corporate proxies, and a new or reinstalled app skips onboarding for an account that already finished it. 0.71.2 (October 14) says accounts without Grok Bot access finish setup and see just the access notice instead of setup or load errors, and that Restart to Update goes away when an update is withdrawn, with download retries backing off. These are fixes as described in the notes, not a guarantee for every account.

1. Keep the Grok Bot app open for the entire browser sign-in.
2. Confirm the browser page says sign-in succeeded before switching back.
3. If the app did not pick it up, return to it manually and choose Sign in on the welcome screen again; if you are already in the app, use Sign In with Cursor from Settings.
4. Verify in the browser that the account you signed into actually has Grok Bot access on its plan.
5. If your organization uses SSO, complete the organization login rather than signing in with a different personal account; the troubleshooting page calls this out as a distinct failure mode from a stuck browser hand-off.
6. If you have a seat on a self-serve Grok Business plan, Cursor's plans help says to sign out of Grok Bot and sign back in with Sign in with Grok using the Grok account that holds the seat. Since 0.75.5, if that seat doesn't cover Grok Bot yet, the usage limit message says to ask your Grok Business admin to connect your team.

Sources: https://docs.x.ai/grok-bot/troubleshooting, https://docs.x.ai/grok-bot/get-started, https://cursor.com/help/grok-bot/plans, https://x.ai/changelog/bot#v0.71.2, https://x.ai/changelog/bot#v0.75.2, https://x.ai/changelog/bot#v0.75.5

## The setting most people miss

Grok Bot requires cloud data storage. The getting-started page says accounts using Legacy Privacy Mode must move to a supported Cursor data setting before use. On a team, only an administrator can change it. If you have had Cursor for a long time and privacy mode was on, this is the most likely cause of an authentication loop that no local fix touches. A Cursor staff answer on September 9, about a Mac that kept showing Can't reach your computer, adds that Grok Bot needs an explicitly saved Privacy Mode choice before it can connect to its computer.

Check that the account still has access, too. On October 8 a Cursor staff member answered a Mac user whose app said Grok Bot is having trouble connecting, and whose Recover and Reset both failed: the account's one-week trial had ended a month earlier, and the app showed the lost access as a connection error, which staff called misleading and are tracking. The fix was to sign in at cursor.com with the same account, choose a plan that includes Grok Bot or link SuperGrok, then fully quit and reopen the app. Cursor's plans help, rechecked October 25, says that on The X Subscription Grok Bot is included on Premium, Super and Ultra, for individuals and team seats, but not on Plus or Free, and 0.71.2 says an account without access now sees just the access notice rather than setup or load errors.

Your network can matter as well. On October 12 a Cursor staff member (Colin) told a Mac user whose desktop app could not reach the Bot's computer while the phone app worked that, between October 10 and early October 12, the desktop app's connection was going through a VPN or proxy route Cursor's servers were not accepting; reinstalling and signing in again could not change that. If the phone works and the desktop does not, try the desktop without the VPN or proxy before resetting anything. The 0.75.2 release notes say the desktop app now connects directly unless you've turned on a system proxy, which fixes loading behind some corporate proxies.

Version matters too. Cursor's help says Grok Bot requires an update when your version is more than 14 days old and a newer one is out, showing Update required, and since 0.65.0 automatic updates are on by default. The x.ai/bot download list describes the Windows build as Windows 10 and 11 (x64); see [our platforms guide](https://www.grokbotwiki.com/guides/grok-bot-platforms) for the right installer.

Sources: https://docs.x.ai/grok-bot/get-started, https://docs.x.ai/grok-bot/troubleshooting, https://forum.cursor.com/t/grok-bot-macos-persistent-cant-reach-your-computer/171170, https://forum.cursor.com/t/grok-bot-completely-unusable-recovery-and-reset-both-fail/174022, https://forum.cursor.com/t/grok-bot-0-68-1-macos-cant-reach-computer-delete-fails-update-does-nothing/173950, https://cursor.com/help/grok-bot/how-to, https://cursor.com/help/grok-bot/plans, https://x.ai/bot, https://x.ai/changelog/bot#v0.71.2, https://x.ai/changelog/bot#v0.75.2

## What the Windows threads found

The Windows 0.44.0 thread, opened September 9 with 36 replies and more than a thousand views, collects reports where update, logout and login, and cache clearing all failed. Cursor staff split it into two cases. Where the app still looks signed in but sending fails with an authentication error, updating Grok Bot's Computer resolved it for most people, and staff reset some computers from their side. Where the browser sign-in never completes, staff checked the session on the backend; in one case it was being declined based on where the computer was connecting from, because Cursor is not available in every region. A separate thread describes Windows sending messages that never get replies after a reset, which is a computer-health issue rather than sign-in; [our not-responding guide](https://www.grokbotwiki.com/guides/grok-bot-not-responding) covers that. One user reported a fully black window for days; the October 11 changelog (0.69.0 to 0.70.2) says a blank window after an update now relaunches and a crash loop offers to reload or quit, and that switching accounts now lands within seconds even when another computer is asleep, so install the latest build before anything else.

If your case matches, post your app version, plan, sign-in method, and timestamp in the existing thread. Buying a different plan or reinstalling repeatedly did not resolve the reported cases. One sign-in dead end does have a release-note fix: 0.78.1 (October 27) says buying a plan during desktop sign-in now returns you to the approval screen, so the app finishes signing in. Before that, check [Is Grok Bot down?](https://www.grokbotwiki.com/guides/is-grok-bot-down): a cursor.com sign-in incident looks the same from your side.

A related but distinct case surfaced October 16: a thread (377 views as of October 25) reported local tool execution permanently refused with "Local tools are turned off. The user has set local tool access to 'Never'", even with Execution on Local Computer set to Always allow, and only on one account while other accounts on the same Mac worked normally. The reporter traced it to their X and Grok logins being on one account while Cursor was signed into a different one, and merging the accounts fixed it for them. Several new X Premium subscribers on Mac and Windows then reported the same message without any second account. On October 18 a Cursor staff member (Colin) explained that the message is misleading: for some newer accounts the app doesn't finish linking your computer to your account, and until it does the computer is treated as Never whatever Settings says, so restarting, reinstalling, toggling the setting or signing out and back in don't help. His workaround: sign in at grok.com with the same account you use in Grok Bot, open Settings from the account menu, go to Privacy, click Edit, choose a privacy option and save (saving is what matters, even if you keep the same option), wait about a minute, then ask the Bot again, and if it still refuses, quit Grok Bot completely and reopen it. He said it has also cleared on its own after about a day for some people, that it is a known issue Cursor is tracking, and that checking all your logins point to the same account is still worth doing. One user said the steps worked; two others, on October 19 and 20, said they did not.

The official place to check the setting has also moved. The troubleshooting page, last updated October 22, says to open Settings → Computer → Your computer and find Execution on this computer for the desktop (Execution on Local Computer until the desktop is listed), and to keep local access off unless a task needs files or commands on the computer in front of you.

- [ ] You are on 0.75.2 or later, which changed the sign-in wait, connection message and proxy handling.
- [ ] Legacy Privacy Mode is off, or your admin has changed the data setting.
- [ ] The signed-in account's plan shows Grok Bot access, and a trial has not quietly ended.
- [ ] You are on the latest build from Settings → Updates → Check for Updates.
- [ ] If you look signed in but sending fails, you tried Update Bot's Computer (Settings → Computer, under Bot's computer) before anything destructive.
- [ ] If the phone app works but the desktop does not, you tried the desktop without a VPN or proxy.
- [ ] If your account uses SSO, you signed in through the organization login, not a personal account.
- [ ] You have your version, plan, and timestamp ready to report.
- [ ] If your company filters sign-in traffic, IT has allowed accounts.spacex.ai, accounts.x.ai and the other listed hosts before October 30, 2026.

Sources: https://x.ai/changelog/bot#v0.78.1, https://forum.cursor.com/t/grok-bot-windows-0-44-0-authentication-error-persists-after-update-logout-login-and-cache-clear/171115, https://forum.cursor.com/t/grok-bot-sent-messages-but-never-replies-after-reset-windows/172007, https://forum.cursor.com/t/still-cant-get-into-grok-bot-on-computer-or-app/169184, https://x.ai/changelog/bot, https://docs.x.ai/grok-bot/troubleshooting, https://forum.cursor.com/t/grok-bot-cant-run-local-tools-on-my-mac-setting-stuck-on-never-this-account-only-grok-bot-mac/174997

## Bots or plan missing after switching to The X Subscription

A forum thread opened October 21, with about 790 views by October 25, collects reports from people whose Bots vanished, or whose app said their plan does not include Grok Bot, after they bought or switched to The X Subscription or tried to unify their X, Grok and Cursor accounts. Users describe the Mac app refusing to sign in, a Grok Bot app stuck in a sign-in loop, the message That Grok account is already linked to another Cursor account, Cursor session expired, and, for several users, Can't spin up this bot when creating a replacement in Grok.

A Cursor staff member (mohitjain) replied on October 21 that the Bots are not gone: during the switch they can end up on a different account from your plan, so one side shows the plan with no Bots and the other shows the Bots but asks you to subscribe. For one user he said the account-combine step had left the Bots on one account and the plan on the other, that putting them back needs a fix on Cursor's side, and that nothing the user did caused it. On October 20 another staff member (Colin) wrote that switching is opt-in for existing subscribers and permanent once done, and asked anyone with a wrong charge, missing Bots or a plan that didn't carry over to email support@x.ai with their Cursor account email and the X or Grok account they linked. Users were still posting new cases with support ticket numbers on October 25, and no staff reply in the thread had announced a general fix.

Recent releases touch merges but do not claim to fix this split. 0.71.2 shows Your accounts are being merged in Settings while a paid merge is still moving data, with Contact Support if it runs long, and makes merges that move many Bots finish in one go; 0.75.2 says the remaining account keeps its Grok Bot email inbox and connector settings after a merge, and that linking an already unified Grok account offers to merge into it instead of failing; 0.75.5 says you keep managing the Bots you created after a merge.

1. Fully sign out of Grok Bot everywhere, including the apps and grok.com, then sign back in using the same method you used when you created the Bots, as staff advised.
2. If they are still missing, note which side you land on: a plan with no Bots, or Bots with a subscribe prompt.
3. Email support@x.ai with the email on your account and the X or Grok account you linked, and keep to one ticket; several users said later tickets were closed as duplicates.
4. Until it is sorted, do not reset the Bot's computer, delete anything or buy a second subscription; staff said that can make recovery harder. Several users also said support told them not to retry the unify flow.

Sources: https://forum.cursor.com/t/all-my-grok-bot-disappear/175510, https://forum.cursor.com/t/introducing-the-x-subscription/174450, https://x.ai/changelog/bot#v0.71.2, https://x.ai/changelog/bot#v0.75.2, https://x.ai/changelog/bot#v0.75.5

## Quick answers

### Why does the sign-in page now show Grok or xAI branding?

SpaceXSI's X Subscription docs (the sign-in page was last updated October 5, 2026, and reread by us October 25) say Grok Bot now uses the shared xAI sign-in path, with no separate Grok Bot login, and the page may show Grok or xAI branding. Signing in only authenticates you: it does not link or combine your X, Grok and Cursor accounts or switch your plan. If you have more than one account, check you picked the one that holds your plan.

### What changes on October 30, 2026?

SpaceXSI's sign-in domains page, reread October 25 and still dated October 5, says Cursor sign-in moves from authenticator.cursor.sh to accounts.spacex.ai and accounts.x.ai on October 30, 2026. Until then authenticator.cursor.sh remains the sign-in page. Existing sessions stay signed in, it is not a forced logout, and SSO identity-provider settings such as Okta tiles and ACS URLs do not need to change. If your company uses a firewall or proxy allowlist such as Zscaler, IT should add the new hosts before October 30, or sign-in will fail after it: preferably the wildcards *.spacex.ai, *.x.ai, *.grok.com, *.grokusercontent.com and *.grokipedia.com, or at least accounts.x.ai, accounts.spacex.ai, auth.x.ai, auth.grok.com, auth.grokusercontent.com, auth.grokipedia.com and grok.com, while keeping *.cursor.sh, *.cursor-cdn.com, *.cursorapi.com and *.cursorvm.com allowed. Update bookmarks that point to authenticator.cursor.sh.

### My Bots disappeared, or the app says my plan doesn't include Grok Bot, after I switched to The X Subscription. Are they gone?

Cursor staff say no. On October 21 a staff member wrote that during the switch Bots can end up on a different account from the plan, so one side shows the plan with no Bots and the other shows the Bots with a subscribe prompt. Fully sign out of Grok Bot everywhere, including grok.com, and sign back in with the same method you used to create the Bots. If that does not bring them back, email support@x.ai with your account email; do not reset the Bot's computer, delete anything or buy a second subscription meanwhile. For accounts where the combine step split Bots and plan, staff said putting them back needs a fix on Cursor's side that they are tracking. Users in that thread were still waiting on October 25.

### Why does sign-in never complete?

The official docs say to keep the app open while the browser sign-in finishes, confirm the browser reports success, return to the app manually if it does not switch back, and choose Sign in on the welcome screen again, or Sign In with Cursor from Settings if you are already in the app. If your organization uses SSO, complete that organization login rather than a personal account. If the account uses Cursor's Legacy Privacy Mode, Grok Bot will not work until the data setting is changed.

### I updated, logged out, and cleared the cache. Still an authentication error. Now what?

That exact sequence is the title of a 36-reply Windows thread. Cursor staff said that for most people there the app stayed signed in and only sending failed, and updating Grok Bot's Computer (now Settings → Computer → Update Bot's Computer) fixed it while keeping Bots and data. When the login itself never completes, staff checked accounts on the backend; in one case the session was declined because Cursor is not available in every region. Check Legacy Privacy Mode and your plan first, then add your version and timestamp to that thread.

## Sources

- [Grok Bot changelog: 0.78.1 (buying a plan during desktop sign-in returns to the approval screen, October 27)](https://x.ai/changelog/bot#v0.78.1)
- [Official troubleshooting](https://docs.x.ai/grok-bot/troubleshooting)
- [Getting started and eligibility](https://docs.x.ai/grok-bot/get-started)
- [Forum: Windows 0.44.0 authentication error persists](https://forum.cursor.com/t/grok-bot-windows-0-44-0-authentication-error-persists-after-update-logout-login-and-cache-clear/171115)
- [Forum: sent messages but never replies after reset (Windows)](https://forum.cursor.com/t/grok-bot-sent-messages-but-never-replies-after-reset-windows/172007)
- [Forum: black window, cannot get in](https://forum.cursor.com/t/still-cant-get-into-grok-bot-on-computer-or-app/169184)
- [Forum: persistent Can't reach your computer until a Privacy Mode choice is saved (staff answer, September 9)](https://forum.cursor.com/t/grok-bot-macos-persistent-cant-reach-your-computer/171170)
- [Cursor help: how-tos (required updates)](https://cursor.com/help/grok-bot/how-to)
- [Grok Bot downloads (x.ai/bot)](https://x.ai/bot)
- [Forum: trouble connecting and Reset fails after a trial ended (staff reply, October 8)](https://forum.cursor.com/t/grok-bot-completely-unusable-recovery-and-reset-both-fail/174022)
- [Forum: desktop app could not connect through a VPN or proxy route while the phone worked (staff reply, October 12)](https://forum.cursor.com/t/grok-bot-0-68-1-macos-cant-reach-computer-delete-fails-update-does-nothing/173950)
- [Grok Bot changelog (blank-window and crash-loop fixes, October 11)](https://x.ai/changelog/bot)
- [Grok Bot sign-in on The X Subscription (docs.x.ai, updated October 5)](https://docs.x.ai/x-subscription/grok-bot-sign-in)
- [Which domains Cursor sign-in needs (docs.x.ai)](https://docs.x.ai/x-subscription/sign-in-domains)
- [Forum: local tools stuck on Never for some newer accounts (Mac and Windows, staff workaround October 18, 377 views as of October 25)](https://forum.cursor.com/t/grok-bot-cant-run-local-tools-on-my-mac-setting-stuck-on-never-this-account-only-grok-bot-mac/174997)
- [Forum: all my Grok Bots disappeared after the X Subscription switch (788 views, staff replies October 21)](https://forum.cursor.com/t/all-my-grok-bot-disappear/175510)
- [Forum: Introducing The X Subscription (staff reply on opt-in switching and support, October 20)](https://forum.cursor.com/t/introducing-the-x-subscription/174450)
- [Cursor help: plans and billing (which plans include Grok Bot, Grok Business seats)](https://cursor.com/help/grok-bot/plans)
- [Grok Bot changelog 0.71.2 (October 14): access notice, account merges, withdrawn updates](https://x.ai/changelog/bot#v0.71.2)
- [Grok Bot changelog 0.75.2 (October 22): sign-in connection message, 20-minute browser sign-in, corporate proxies](https://x.ai/changelog/bot#v0.75.2)
- [Grok Bot changelog 0.75.5 (October 23): Grok Business seat message, Bots kept after a merge](https://x.ai/changelog/bot#v0.75.5)