Grok Bot vs Cursor Cloud Agents: Which Should You Use?

The unit of work differs. A 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 durable teammate with a name, a job and its own conversation, and Cursor says it takes on multi-step work across apps and websites. A Cloud Agent runs one coding task in an isolated VM, which holds a cloned repository, installed dependencies, secrets and network access. Both keep working while your laptop is closed.

The feature lists overlap more than the names suggest. 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. can use computers to control the desktop and browser, support MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. Press Enter for the full definition. servers and work across several repositories. 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 a terminal and a filesystem as well as its browser. A feature-by-feature comparison won't settle the choice, so ask what the finished work should look like and who reviews it.

Our rule of thumb: if the job ends in a code change someone will merge, start with a Cloud Agent. If it recurs across business tools under one owner, start with 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..

Both run on Firecracker microVMs, but each product scopes the VM differently. 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 each user one dedicated computer, and every Bot that user runs shares its files, browser sessions and command-line credentials. Each Bot has its own screen, but the docs treat screens as work surfaces rather than security boundaries. A Cloud Agent gets its own VM for the run, and one agent cannot see another agent's code, environment or state.

How long state lasts differs too. A 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. keeps its memory, files, browser sessions and preferences across sessions, and one Bot can pick up a file another saved. The computer keeps files and browser data on a durable disk, and idle computers hibernate without being deleted. Under the Data Processing Agreement, data is deleted or returned within 30 days of written direction once the service ends. Grok Bot has no per-organization retention policy.

On the Cloud Agent side, each kind of data has its own retention rule:

• The runtime workspace is recycled automatically after the run goes idle, and follow-up prompts refresh the timer.
• VM snapshots, including cloned code, follow a rolling 30 days of inactivity and are then deleted. They can't be deleted on demand.
• Conversation state is kept indefinitely by default so runs can be resumed, and the Delete Agent API removes a transcript and artifacts on demand.
• Enterprise teams can cap conversation retention with retention policies.

A Cloud Agent hands code back through source control. It clones the repository, works on a separate branch, pushes it and opens a pull request for a person to review before anything merges. Cursor's Cloud Agent security page says pull requests open ready for review unless you ask for a draft. Screenshots, videos and logs show how the agent verified the change. The built-in Cursor Cloud MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. Press Enter for the full definition. exposes transcripts, run events, environment details and setup logs, and you can take over the agent's remote desktop to try the software without checking out the branch.

A 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. returns work in the conversation and on its computer. Cursor suggests naming the artifact and its acceptance criteria up front: a document with source links, a spreadsheet with defined columns, a folder of screenshots and logs, or an unsent draft. For consequential work, Cursor also suggests asking the Bot to separate facts found in source systems, assumptions, completed actions, actions waiting for approval and open questions.

Git gives a code change a diff, branch protection and a merge gate. A reconciliation or a brief has no diff to review. For that kind of work, 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. docs ask for results a person can check on their own, with source links, timestamps and an action log.

They guard different things. Cloud Agent security is built around repositories. An admin installs the Cursor GitHub or GitLab App and grants it only the repositories you choose. Each user then connects their own Git account, and an agent can reach only repositories the triggering user could already reach.

A 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 access by default and works with the accounts and apps the member signs it into. Its controls center on approvals, the network policy and keeping credentials away from the model.

Autonomy is where the risk models differ most. 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. auto-run terminal commands, and Cursor's Cloud Agent security page names the risk: planted instructions could try to make the agent send code to an external host. Its answer is egress limits, redacted secrets, .cursorignore, the pull request review and signed commits.

On 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. side, Auto Review checks risky actions before they run and can let one proceed, require approval or deny it. Auto Review is on by default, and only an Enterprise admin can stop members from turning it off. The network policy, per-action approvals and per-user isolation sit beneath it. Its security page says these controls reduce injection risk but don't eliminate it.

Plan level matters on 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. side, since Network Controls, Auto-review enforcement, audit logs and Action Recording are Enterprise only. The full list is in the Grok Bot security overview. Cloud Agent secret types and egress modes are on Cloud Agent security and network.

Neither works with Privacy Mode (Legacy)A Cursor data setting that blocks Grok Bot because the product requires cloud data storage. Press Enter for the full definition.. Cursor's Cloud Agent security page says legacy 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. isn't supported because agents store code and environment data in the cloud while they run. 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.'s Teams docs go further: the legacy setting blocks it entirely.

Both work under standard 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.. 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. run in it, and Cursor never trains on the code they access or on the prompts and responses their runs generate. 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. follows the team's privacy mode for each member, and Privacy Mode keeps customer data out of training.

Model control is the clearest split. 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. offer a curated selection of models, and you can choose the context window size for supported ones. 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 for members or admins. Each request goes to an xAI model or to a third-party model whose provider is on Cursor's sub-processor list.

The model behind 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. can change from one request to the next, and usage views record it as Grok Bot usage, not by model. The team model allowlist doesn't govern Grok Bot either.

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. come with Premium and higher, Teams, Enterprise and legacy paid plans. Free and Plus don't include them.

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 included on 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., on every paid individual legacy Cursor plan and Cursor Teams, but not on Plus or Free. Legacy Cursor accounts can also link an individual SuperGrok or X Premium+ subscription, or use a self-serve Grok Business seat. For Enterprise, the plans page says to consult your account executive, and the Teams docs say an admin turns it on from the dashboard.

The list above comes from 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. plans page, the canonical matrix according to Cursor's Teams docs. The overview, Get started and the Teams docs' own availability table still say every paid individual Cursor plan includes Grok Bot, though Plus doesn't.

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. use your plan's usage at the selected model's rate. A larger context window can raise token use, and Cursor asks you to set a spend limit the first time you use them.

Included 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 resets weekly. 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., Grok Bot and 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. share one weekly pool with the rest of Cursor and the Grok apps. Prepaid creditBalance bought by top-up or Auto Top-up on The X Subscription that pays for third-party models from the first request, and for Cursor models beyond the weekly pool, at the same per-model rates. Press Enter for the full definition. pays for extra usage, up to a monthly additional usage limit you set.

On legacy plans, extra 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 can continue on on-demand if it's enabled, and it counts toward the On-demand monthly limit. That limit isn't a hard stop mid-run. A separate Grok Bot spend cap isn't available, though account-level on-demand controls apply.

Per-task costs are hard to compare on paper: you see a Cloud Agent's model before the run, while 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. routes each request itself. Measure one real workflow on your own account instead. Tiers and usage detail are on Grok Bot pricing.

Choose from the final artifact and who owns it. A task that ends at a branch or pull request belongs with a Cloud Agent. A role that should wake up tomorrow with the same apps, preferences and recurring responsibility belongs with 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..

• Choose 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. for research, reconciliation, source-linked briefs, recurring preparation and supervised actions across apps and websites.
• Choose 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. for feature work, test repair, multi-repo changes and anything that should come back through Git.
• Choose both when a standing Bot prepares or detects a task, delegates the repository work, then folds the reviewed result back into its report.
• Hold off on either when your plan doesn't include it, or when the workflow needs a control your plan lacks, such as 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.'s Enterprise-only network policy or audit logs.

A product-performance workflow shows the split. In Cursor's product performance role, a Bot reviews dashboards and traces after a release and returns the highest-confidence hotspot with evidence. If the next step is a patch, that bounded finding can go to a Cloud Agent with the repository and an acceptance test. The Bot then links the resulting pull request in its report.

Start with one handoff. Get each side producing results you would accept on their own before you chain them, because a two-product workflow that fails in the middle is harder to debug than either product alone.

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. can delegate coding tasks to 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.. The Cloud Agents switch on the Grok Bot page of the Cursor dashboard is on by default and applies to the whole team. Delegated work runs on separate computers under your existing Cloud Agent controls, and admins can turn spawning off. Auto Review counts a Cloud Agent launch as delegation and reviews it like other risky actions.

1. 1Have the Bot gather current evidence and state the problem without changing anything.
2. 2Review the proposed coding task and its acceptance check.
3. 3Let the Bot launch a Cloud Agent for that repository task.
4. 4Review the Cloud Agent's branch, artifacts and pull request through your normal code process.
5. 5Return the approved result to the Bot's conversation for the wider report or the next supervised action.

Keep the two approval systems separate. Approving a Bot's delegation is not approval to merge the returned code. A pull request with passing checks doesn't authorize the Bot to message a customer about it either, so keep that message behind the Bot's own approval.