Grok Bot

Grok Bot is a persistent AI agent product introduced by SpaceXAI on August 11, 2026. A user creates named agents called Bots and assigns them work through a desktop or iPhone app. The Bots can use a shared cloud computer, connected services, stored working context, and scheduled routines, allowing cloud tasks to continue after the user's local computer is closed.^[1][2][3]

Grok Bot is distinct from Grok, the chat assistant and model family associated with xAI, and from Cursor, the AI-assisted code editor. Grok Bot uses Cursor accounts, billing, privacy settings, and infrastructure, but Cursor describes it as a separate product surface with its own data flows.^[2][13][15]

Status and access

SpaceXAI launched Grok Bot as an early-beta product. Cursor's help center says the beta wording sets expectations for an early product, while also saying that Grok Bot is not subject to Cursor's Beta Services terms. Independent launch coverage by MacRumors corroborated the product's August 11 release and its cloud, multi-agent, and routine features, but did not independently test them.^[1][2][14]

Access terms changed during the first weeks after launch. As documented on August 28, 2026, access was included with paid individual Cursor plans and self-serve Cursor Teams plans. A person could also grant usage to a Cursor account by linking an eligible individual SuperGrok, SuperGrok Plus, or SuperGrok Heavy subscription. Enterprise access required organizational enablement. Grok Bot usage was metered on the Cursor account, with included usage resetting weekly and eligible accounts able to use shared on-demand spend after the allowance was exhausted if on-demand usage was enabled.^[4]

Cursor also offered a free trial as a usage credit with a seven-day outer window. The credit was consumed by agent steps and tokens rather than message count, so one long run could use most or all of it. Prices, allowances, trial terms, and eligible plans are changeable service terms rather than fixed product specifications.^[4]

Scroll sideways for more →

The iPhone app accesses the same Bots, conversations, routines, plugins, and cloud computer as the desktop app. It supports messaging, approvals, observation, and takeover of computer actions. Editing, testing, or deleting routines and updating the cloud computer remained desktop operations in the reviewed release.^[11][17]

Architecture

Official documentation defines one Bot as a persistent, named agent with a role, conversation, working context, and selected memories. A user can run multiple Bots, place them in group chats, and have them pass context or responsibility between threads.^[3][8]

The execution environment is account-scoped. All of one user's Bots share one persistent cloud computer, including its files, browser sessions, command-line credentials, and app logins. Each Bot receives a separate screen so Bots can work in parallel, but the screens are not separate security boundaries. A login or file placed on the computer can be available to every Bot on the account.^[3][5][9]

The cloud computer includes a browser, filesystem, and terminal. It is separate from the Mac or Windows computer in front of the user. Running commands on that local computer is an optional, separately controlled capability whose default setting is to ask for approval each time. Denying local execution does not prevent use of the cloud computer.^[5][9]

Plugins and external services

Grok Bot can reach external services through plugins, Model Context Protocol connections, or browser interaction. A user installs a supported plugin from the in-app marketplace or a Connect card, then completes the provider's authorization flow in a browser. Installed connections are account-wide rather than isolated to one Bot, and team administrators may restrict which marketplace plugins are available.^[5][6]

If a site has no plugin, a Bot can use the cloud browser. The user is expected to take over for passwords, passkeys, two-factor codes, CAPTCHAs, and other sensitive sign-in steps. Browser access is not equivalent to a supported API integration: interfaces, permissions, authentication requirements, and available data can change independently.^[2][5][9]

The public Grok Bot documentation reviewed through August 28, 2026 did not document a developer API for programmatically creating or controlling Bots. It documented plugins, MCP connections, and browser interaction as the mechanisms for reaching external services.^[3][5][6]

Skills and routines

A skill stores reusable instructions for how to perform a type of task. A routine assigns one Bot to run a workflow on a schedule or a supported event. Routines execute on the cloud computer, so they can run without the desktop application remaining open.^[7]

SpaceXAI recommends testing a workflow once before scheduling it. A routine test performs real work rather than a simulation, so external writes or messages can occur during testing. The documentation also recommends explicit behavior for missing or stale source data, idempotent retries, and approval checkpoints before sending messages, making purchases, deleting data, publishing content, or changing production systems.^[7][9]

Teach-by-demonstration was described as a gradual rollout. Where available, a Bot can observe a limited visible walkthrough and turn it into a draft skill. The recording does not include microphone input, and the resulting draft should be reviewed and tested. This feature does not demonstrate that a Bot can infer arbitrary workflows reliably or run them indefinitely without supervision.^[7]

Memory, files, and recovery

A Bot can retain stable preferences, project context, and selected memories between conversations. Official guidance says memory is not an authoritative source for changing or consequential facts; a Bot should reopen a current source before acting on such information. Duplicating a Bot copies its profile and enabled skills or routines, but not its conversation history, learned memories, or attachments.^[8]

The shared computer uses /workspace for project files intended to persist. Browser state, supported sign-ins, and synchronized durable files are designed to survive normal update and recovery operations, while temporary directories, installed packages, local-only files, and unsaved application state may not. Conversation history is stored separately from the computer filesystem.^[5][12]

Cursor recommends Update or Recover before Reset. Recovery can rehydrate durable synchronized data but cannot restore work that existed only on a failed computer or had not synchronized. Reset is a last resort and may lose recent work. These mechanisms are continuity features, not a guarantee of complete backup or zero data loss.^[2][12]

Deleting a Bot removes its active profile, conversation, and routines, but does not automatically remove files, browser sessions, or logins from the account's shared computer. Those must be removed or revoked separately, and backend retention follows the applicable account terms.^[8][9]

Permissions, secrets, and privacy

Grok Bot presents approvals before selected consequential actions. Official guidance recommends explicit boundaries for external messages, publication, purchases or financial transfers, deletion or overwriting, permission changes, production changes, and acceptance of legal terms. An approval governs the proposed next action; it does not undo an action that has already occurred.^[9]

Auto Review can apply model-based rules to tool calls and computer actions. A Require Approval rule takes precedence over an Always Allow rule, but the review system is not a substitute for least privilege or narrowly scoped access. Because all Bots share one computer, separate Bots should not be used to isolate credentials, customer data, or projects that require different trust boundaries.^[9]

Passwords and verification codes should not be pasted into conversation messages or ordinary files. For supported connections, Grok Bot can display a secure secret request whose value is masked, excluded from the transcript, and not shown to the model. The feature is not a general password manager. Other sensitive authentication and payment-confirmation steps require the user to take control of the computer.^[9][10]

Grok Bot requires cloud data storage and does not support Legacy Privacy Mode. Cursor states that the editor's Privacy Mode should not be assumed to govern Grok Bot because the products have different data flows. Storage location, retention, contractual coverage, and deletion processes depend on account type and how data was created. A public Bot share link copies configuration rather than the owner's computer or logins, but configuration containing secrets or internal information can still expose that information.^[9][13]

Limitations

Most public evidence about Grok Bot at launch consisted of SpaceXAI and Cursor documentation, internal use cases, product demonstrations, and testimonials. These sources explain intended operation but do not establish a general task-completion rate, productivity gain, security guarantee, or reliability level. The reviewed independent launch article summarized company claims and did not provide a hands-on evaluation.^[1][14]

The product depends on external websites, plugins, account permissions, authentication flows, model judgments, and a persistent cloud environment. A changed website, expired authorization, missing data, ambiguous approval, or unsynchronized file can interrupt or alter a run. Memory can become stale, browser automation can fail, and a model-based reviewer can make mistakes. Consequential workflows therefore require current source checks, limited permissions, observable logs or drafts, and human review appropriate to the action.^[5][7][8][9]

References

1. ^SpaceXAI. "Introducing Grok Bot." August 11, 2026. x.ai/...introducing-grok-bot
2. ^Cursor. "Getting started with Grok Bot." Accessed August 28, 2026. cursor.com/...getting-started
3. ^SpaceXAI Docs. "Grok Bot." Updated August 11, 2026. docs.x.ai/...overview
4. ^Cursor. "Plans and billing." Accessed August 28, 2026. cursor.com/...plans
5. ^SpaceXAI Docs. "Use the computer and apps." Accessed August 28, 2026. docs.x.ai/...computer-and-apps
6. ^Cursor. "Connect plugins." Accessed August 28, 2026. cursor.com/...connect-plugins
7. ^SpaceXAI Docs. "Skills and routines." Accessed August 28, 2026. docs.x.ai/...skills-routines-and-automations
8. ^SpaceXAI Docs. "Create and manage Bots." Accessed August 28, 2026. docs.x.ai/...bots
9. ^SpaceXAI Docs. "Approvals, security, and privacy." Updated August 22, 2026. docs.x.ai/...approvals-security-and-privacy
10. ^Cursor. "Store secrets securely." Accessed August 28, 2026. cursor.com/...secrets
11. ^Cursor. "Grok Bot on mobile." Accessed August 28, 2026. cursor.com/...mobile
12. ^Cursor. "Recover Grok Bot computer data." Accessed August 28, 2026. cursor.com/...computer-recovery
13. ^Cursor. "Privacy and data." Accessed August 28, 2026. prod.cursor.com/...privacy
14. ^Juli Clover. "Grok Bot Brings Always-On AI Agents to macOS and iOS." MacRumors, August 11, 2026. macrumors.com/...grok-bot-macos-ios
15. ^SpaceXAI Docs. "Welcome to Grok." Accessed August 28, 2026. docs.x.ai/...overview
16. ^SpaceXAI Docs. "Get started." Updated August 20, 2026. docs.x.ai/...get-started
17. ^SpaceXAI Docs. "Grok Bot for iOS." Updated August 20, 2026. docs.x.ai/...mobile