Grok Bot: What It Is, Who Gets It and How It Works

Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. gives you Bots you keep around: AI teammates with a name, a job and context that builds up over time. Each Bot works on a persistent cloud computer with a browser, filesystem and terminal, so a task finishes inside your real tools instead of ending as a chat draft. You work with a Bot by messaging it, as you would brief a colleague: give it the task, the relevant context and access to the tools it needs.

Because the work runs on that cloud computer, closing the app, your laptop or your phone doesn't stop a background turn or a routine. Files, browser sessions and sign-ins persist between tasks, so a Bot can pick up next week where it stopped today.

Every Bot on your account shares that one computer, with its files, browser sessions and app logins. Each Bot gets its own screen and runs one computer-use task on it at a time. Cursor calls those screens work surfaces, not security boundaries, and says to treat anything on the computer as available to every Bot you run. A teammate's shared Bot, which Cursor used to call a Team Bot, usually works on your computer too when you chat with it. Each user's computer is dedicated and hardware-isolated, and one user can't reach another's.

Each name refers to a different kind of thing. Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. is a product: a standing teammate with a computer and a job. Grok 4.7Cursor and SpaceXAI's current lead Cursor model, in the weekly pool at $2 per million input tokens and $6 per million output, with a 256k context window and a 500k variant; above 256k input tokens it bills at 2x the standard rate. Press Enter for the full definition., Grok 4.6A Cursor and SpaceXAI model for complex coding and knowledge work, still in the Cursor model pool and succeeded by Grok 4.7; it is a selectable model and is separate from the Grok Bot product. Press Enter for the full definition. and Grok 4.5 are models, which you can pick for an Agent request in Cursor. A Cursor Cloud Agent is a coding agent that runs in an isolated cloud VM with a full development environment. The Grok chat app from xAI is a separate app with its own limits.

Unlike Agent in the editor, Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. has no model picker, and it doesn't show which model handled a request. Each task goes to whichever backend model is most likely to produce the best outcome. That model may come from xAI or from a third-party provider on Cursor's sub-processor list, and it can change between requests. The word Grok in the product name doesn't tell you which model ran.

Cloud AgentsAgents that run in a Cursor-managed virtual machine, check out the repo, do the work and open a pull request, then shut down, with no load on your laptop. Press Enter for the full definition. differ in scope. A Cloud Agent is built around code, with cloned repos, dependencies and pull requests in the repos it changes. A Bot works across business tools, browsers and files, and when part of a job turns into coding, it can hand that part to a Cloud Agent. Cursor's security docs list Cloud Agent launches among the delegation actions Auto Review checks before they run, so while Auto Review is on, the handoff is itself a reviewed step. The Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. vs Cloud Agents comparison helps you pick between them for a given job.

A Bot takes on multi-step work across apps and websites, keeps you updated in the conversation and comes back when something needs your approval. Cursor's examples of good Bot jobs are specific roles: Talent Scout, Expense Manager and Bug Reproduction. Its docs contrast them with a General Helper, which neither guides the Bot nor makes its saved context reusable. Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. use cases covers starter roles and their prompts.

Use a connected app when one exists, because Cursor says an app is more reliable than clicking through a website. Connected apps also keep their logins off the computer. The OAuth tokens live on Cursor's connector backend, and the Bot uses the app's tools without holding them. The browser covers the gaps, though a site can still block automation, expire a session or ask for a human step. When that happens, the Bot hands the step to you rather than working around it.

Cursor's own example of a first handoff spans a few tools, has a clear finish line and stops at drafts for you to approve.

Approvals keep consequential actions under your control. An action that needs approval appears in the conversation with the proposed operation and its inputs, and you answer with Allow once, Always allow or Deny. Behind those prompts sits Auto Review, an independent review model that checks risky actions such as shell commands, app calls, computer use and Cloud Agent launches before they run. It is on by default, but a member can turn it off unless an Enterprise admin enforces it.

Cursor positions Auto Review as a complement to explicit boundaries and least privilege, and notes that it doesn't review every side effect. Memory writes are one example. An approval applies to the proposed action alone, and it doesn't extend to work the Bot already completed. The approvals guide covers the cards, rules and expiry.

There is no separate Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. subscription to buy. Premium, Super and Ultra on The X SubscriptionThe subscription Cursor is sold through: one plan for Grok, Cursor and X, with Free, Plus, Premium, Super and Ultra tiers, per-seat Teams, a weekly included pool for Cursor models shared with Grok, and third-party models billed at API list price from prepaid credit. Press Enter for the full definition. include it for individuals and team seats, while Plus and Free don't. Among legacy Cursor plans, every paid individual plan has it, as does Cursor Teams.

A legacy Cursor account can also get Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. usage by linking an individual SuperGrok, SuperGrok Plus, SuperGrok Heavy or X Premium+ subscription. SuperGrok Lite and Grok Enterprise can't link. A seat on a self-serve Grok Business plan also includes Grok Bot: sign out, then sign back in with Sign in with Grok using the Grok account that holds the seat. Included usage resets weekly. The Grok Bot pricing guide covers tiers, on-demand limits, stacking rules and refunds.

That list follows Cursor's Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. plans page, which the Teams docs call the canonical plan and usage matrix. Three docs pages (the Grok Bot overview, Get started and the availability table in the Teams docs) still say every paid individual Cursor plan includes Grok Bot. Plus is a paid plan on The X SubscriptionThe subscription Cursor is sold through: one plan for Grok, Cursor and X, with Free, Plus, Premium, Super and Ultra tiers, per-seat Teams, a weekly included pool for Cursor models shared with Grok, and third-party models billed at API list price from prepaid credit. Press Enter for the full definition., and the plans page excludes it.

Some older guides still list Cursor Pro and Pro+ as excluded. Cursor's plans page now lists both legacy plans as included.

On a team, the plan type decides how access works. Access is separate from the admin controls, and several of those controls are Enterprise only.

Check your privacy setting before a rollout. Cursor's get-started guide says Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. needs cloud data storage, and an account on Privacy Mode (Legacy)A Cursor data setting that blocks Grok Bot because the product requires cloud data storage. Press Enter for the full definition. gets a prompt to switch to Privacy ModeCursor's setting that guarantees code data is not used for training by Cursor or its model providers, and that an admin can enforce org-wide; data-retention terms are a separate, contractual layer. Press Enter for the full definition. before starting. On a team, the Teams docs say that legacy setting blocks Grok Bot entirely. Admins planning a rollout can start with Grok Bot for Teams and Enterprise.

The desktop app runs on macOS, Windows and Linux, and the phone app on iPhone and Android. The apps handle chat, review and approvals, while the work happens on the hosted computer, which runs Linux in Cursor's cloud.

You may still read that Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. has no Linux desktop app and no Android app. Both now exist, and Cursor's get-started guide says a phone reaches the same Bots, conversations, routines and cloud computer you use on desktop.

On models, there is little to configure. Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. has no per-user or per-request model selection, and nobody can be routed toward or away from a particular model. The Cursor model allowlist or blocklist your team sets doesn't apply to it either. Usage and spending screens record the activity as Grok Bot usage, not by model, and Cursor's help center says routing a task to Opus 5.5 doesn't change what you pay per token. Cursor's sub-processor list sets which providers may process your data, and the set of models changes over time.

A Bot keeps stable preferences, role context, important facts and summaries of its prior work. That memory lets it keep its role over time without going back through every past message. Each Bot has its own conversations and memory. The exception, per Cursor's memory help, is a few facts about you, such as your name and time zone, which all your Bots share. Other context moves between Bots through the shared computer's files and browser sessions, or through a direct handoff.

Don't treat memory as an authoritative source. Cursor's guidance is to keep changing facts in the source system, such as the CRM or the spreadsheet, and to ask the Bot to cite or reopen current data for consequential decisions. Correct stale assumptions directly, and back safety boundaries with approvals and Auto-review rules instead of memory alone.

Deleting a Bot removes its profile, conversations, memory and routines, and it can't be undone. Shared facts that Bot saved, such as your time zone, disappear from your other Bots too. Files and sign-ins on the shared computer aren't isolated per Bot and can stay behind, so clean those up separately. If you might want the work later, Hide from sidebar takes the Bot out of your list without deleting its work or pausing its routines. The Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. memory guide covers how to view, correct and forget what a Bot has saved.

Each Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. guide answers a single question. Start with the group that matches what you are doing: using Bots yourself, or rolling Grok Bot out to a team. If you are new, set up Grok Bot first and come back to the rest as questions come up.

Use Grok Bot

Admins and security reviewers need a different set. These guides cover deployment, identity, networking and the controls that only Enterprise teams get, starting with the security overview.

Roll it out at work