We run the Grok Bot teams directory. The product facts below are from vendor docs we read on 2026-08-24. The recipes and the installer prompts are ours. Ellelion LLC is not affiliated with xAI.
What is each product?
Grok Bot and Cursor Cloud Agents can both be on a Cursor plan. They are not the same product. Grok Bot is xAI's teammate with a browser and connectors. A Cloud Agent is Cursor's isolated development VM. Cursor's docs still note the old name: Background Agents.
Cloud agents use the same agent fundamentals but run in isolated VMs in the cloud with full development environments instead of on your local machine.
xAI's get-started page lists Cursor Pro+, Cursor Ultra, and Cursor Teams Standard or Premium among the plans that can open Grok Bot. Cursor Pro without the plus is absent from that list. Cloud Agents, on the troubleshooting page we read, require a paid Cursor plan and a connected source-control account.
What comes back?
A Cloud Agent clones the repo, works on a separate branch, and pushes for handoff. Cursor documents merge-ready pull requests, screenshots, videos, and logs. You can take over the agent's remote desktop, then hand control back.
A Grok Bot comes back with whatever you asked it to leave in the apps: a draft email, a review list, a Notion note. It does not open a pull request unless you also pointed a coding agent at the repo. The combination we like is written on What is Grok Bot?: a Bot gathers evidence, a coding agent changes the repo, a person merges.
Which one fits?
| Criterion | Grok Bot | Cursor Cloud Agent |
|---|---|---|
| Isolation | One computer per account, shared by every Bot | One isolated VM per agent |
| Default output | Work inside signed-in apps and files on that computer | A branch and a pull request |
| Needs source control first | No | Yes. An admin connects GitHub, GitLab, Bitbucket, or Azure DevOps |
| Parallel runs | Many Bots, one shared computer | As many agents as you start, each on its own VM |
| Best when | The job is mail, CRM, ads, or a standing watch | The job is code in a connected repository |
Cursor bills Cloud Agents at API pricing for the selected model and asks for a spend limit. xAI's Grok Bot get-started page lists plan names, not a dollar figure. Do not treat those as the same invoice.
Questions people ask
If I have Cursor Ultra, do I pick Grok Bot or a Cloud Agent?
You can have both. Ultra is on xAI's Grok Bot eligibility list. Cloud Agents still need a paid Cursor plan and a connected repo. Pick by output: apps and drafts for Grok Bot, a pull request for a Cloud Agent.
Does a second Grok Bot isolate code the way a Cloud Agent VM does?
No. Cursor documents one isolated VM per Cloud Agent. xAI documents one computer per Grok Bot account. A second Bot is a second conversation. It is not a second machine.
Can a Grok Bot replace a Cloud Agent on a multi-repo change?
Cursor's Cloud Agent docs describe multi-repo work, coordinated changes, and pull requests in the repos it touches. Grok Bot is not documented as a git handoff tool. Keep repo edits on a coding agent.
Related: What is Grok Bot?, Grok Bot vs Devin, Who can use Grok Bot, Grok Bot alternatives.
Verified on 2026-08-24 against docs.x.ai/grok-bot/get-started, docs.x.ai/grok-bot/overview, cursor.com/docs/cloud-agent. Recheck the live pages before you change a plan or a vendor.
