Last verified

SpaceXAI · Grok Bot

Grok Bot: a hosted computer with agents on it

SpaceXAI's autonomous agent platform — not its coding agent, which is a separate product with a confusingly similar name.

Grok Bot is a set of persistent agents that share one cloud computer, sign into your tools and keep working when your laptop is shut. It is not a coding agent — that is a different product from the same vendor. It has no price of its own, arrives bundled with a Cursor or Grok subscription, and we have not run it ourselves.

Cheapest way in Free, then $20/mo
Free tier Yes
Ways to buy it 9
Oldest check 2026-09-20
§ 01 / WHAT IT IS

What Grok Bot is.

Start with the name, because three products share it and two of them are not this one. Grok is the chatbot. Grok Build is the coding agent — a terminal program you install with one command and run inside a project directory. Grok Bot, the subject of this page, is neither: it is a platform for standing agents that live on a cloud computer the vendor runs for you. If you arrived here looking for something that edits your repository from a terminal, the product you want is the middle one, and this page is not about it.

What Grok Bot actually gives you is a machine. Each account gets one persistent cloud computer with a browser, a filesystem and logins, and the bots you create all work on that same machine — each with its own screen, its own role and its own memory of how you like things done. You sign them into your tools once and they use those tools the way a person would, including services that have no integration to speak of. Work continues while your laptop is closed, routines fire on a schedule, and bots hand tasks between themselves. The vendor's own list of roles is a reasonable guide to the intended buyer: sales outbound, talent scouting, paid media, expenses, account health, chief of staff. Bug reproduction is one of eight, and it is the only one a developer would recognise.

The commercial shape is unusual enough to need saying out loud. The product is SpaceXAI's, but the subscription is billed by Anysphere — the company behind Cursor — sign-in is a Cursor account whichever door you came through, and Grok Bot's own terms of use are published on Cursor's site rather than SpaceXAI's. So a reader who buys a Grok subscription to get Grok Bot ends up with a Cursor account, a Cursor meter and a Cursor refund policy. None of that is hidden, but it is spread across two companies' documentation, and the pricing page here puts it back together.

We have not run it. Every route in requires an account and a card, and signing into a paid product to review it is not something this desk does — so everything on these pages is documented evidence: the vendor's pricing pages, its product documentation, the plan sheet its own docs call canonical, and the terms of use that took effect seventeen days before this page was written. Where two of those sources disagree, and they do, we print both with links rather than picking the flattering one.

§ 02 / WHAT IT COSTS

What it costs.

Full pricing →

Nine ways in, and the thing none of them buys is Grok Bot: every one is a subscription to a different product that includes it. The rule that catches people is that the two families of subscription do not add up — hold one of each and you get the larger, not the sum.

Route Bought as Price
Cursor Pro Subscription $20/mo
Cursor Pro+ Subscription $60/mo
Cursor Ultra Subscription $200/mo
SuperGrok Subscription $30/mo
SuperGrok Plus Subscription $100/mo
SuperGrok Heavy Subscription $300/mo
Cursor Teams Standard Per seat $40/seat/mo
Cursor Teams Premium Per seat $120/seat/mo
Cursor Enterprise Per seat Contact sales
§ 03 / WHEN NOT TO

When it is the wrong tool.

Structural reasons, not complaints about quality. Each of these is a property of how the product is built or sold, and none of them will be fixed by the next release.

You wanted a coding agent This is the most common way to end up on the wrong page. Grok Bot is a general-purpose work agent; the vendor's coding agent is Grok Build, a separate product with its own documentation, its own install command and — unlike Grok Bot — inclusion on every tier including the free one. If the job is editing a repository from a terminal, that is the product, and the tools we have taken apart in depth are Claude Code, Codex and opencode.
The data cannot leave a particular country The documentation is unambiguous: Grok Bot computers run in the United States today. Residency commitments are a conversation with an account team rather than a setting, and they are not the default on any self-serve plan. For anyone working under a residency obligation, that ends the evaluation before the features matter.
Your privacy posture depends on the strict mode Grok Bot requires cloud data storage, so the strictest of the parent product's privacy modes is not supported — and for teams already on it, Grok Bot stays switched off entirely. Training opt-out follows the parent account's settings rather than having its own control. Worth noting alongside that: on the vendor's own Grok feature matrix, the no-training guarantee is a business and enterprise line item and does not appear on any of the individual tiers that grant Grok Bot.
You need a hard ceiling on what it can spend Three published facts stack badly here. There is no Grok Bot spend cap separate from the account-wide one. The monthly limit that does exist is, in the vendor's words, not a hard stop — a run already under way finishes past it. And the product's own terms make the customer solely responsible for every action a bot takes, whether or not it was intended, anticipated or authorised. For an agent that works unattended on a schedule, those three sentences belong together, and they are the reason to start with approval rules rather than add them later.
You were going to isolate work by giving each bot its own bot It does not work that way, and the documentation says so in a sentence worth quoting to whoever proposes it: the computer is assigned per user, not per bot, and separate bots should not be used as a security boundary. Every bot on an account shares one machine — its files, its browser sessions and its logins. Isolation exists between people, not between roles.
Your company buys software on the Grok business plan On the vendor's published feature matrix, Grok Bot appears on the individual Grok tiers and is marked absent from the Business and Enterprise tiers alongside them — the one row in that table where the business plans get less than the personal ones. The enterprise path that does include it runs through Cursor, which is a different contract, a different dashboard and a different sales conversation.
§ 04 / HOW IT COMPARES

Nothing to set it beside, yet.

All comparisons →
!
No head-to-head covers this tool yet. The pairs we hold in /compare/ are between coding agents, and the tools this one actually competes with — general work agents that operate a computer — are not covered there either. Building a pair here to fill the gap would put a second URL on a query /compare/ owns, so the honest move is to say the comparison does not exist rather than invent one.
§ 05 / ALTERNATIVES

If not this.

See the list →

Four different reasons take readers off this product, and they lead to four different shortlists — a coding agent is not a substitute for a work agent, and neither is a browser automation tool.

Frequently asked.

What people search next.

Q · 01 Is Grok Bot the same thing as Grok Build? +
No. Grok Build is the coding agent: a terminal program you install locally and run in a project, also usable headlessly or through the agent client protocol. Grok Bot is the hosted agent platform this page describes. They share a brand and nothing else — different products, different documentation, different availability. Grok Build is on every tier including the free one; Grok Bot is on none of the free ones.
Q · 02 Who actually bills me for it? +
Anysphere, the company behind Cursor. The product is SpaceXAI's and the marketing lives on its site, but sign-in is a Cursor account no matter which subscription granted you access, the usage meter sits on that account, the Grok Bot terms of use are published on Cursor's site, and refunds follow Cursor's policy. If you bought through a phone app store, a third company is involved again.
Q · 03 Can I use it without a Cursor account? +
No. Even the route that starts with a Grok subscription ends at a Cursor account — the documentation describes linking the Grok account to it, and the link is permanent once made. There is no standalone sign-up.
Q · 04 Does it work on Linux and Android? +
Yes, and this is a case where two of the vendor's own pages disagree. The marketing page says desktop means macOS or Windows and names only the iOS app for phones. The documentation lists macOS, Windows, Linux as three package formats, iOS and Android. Both were live on the same day; the documentation is the more specific of the two and the one we would act on.
Q · 05 Is it available to enterprises? +
Three vendor pages give three answers, all currently live. The launch post from August says enterprise users can join a waitlist. The product page says it is generally available for enterprise. The documentation says enterprise access is rolling out and varies by organisation. The practical reading is the third one, and the first has simply not been updated since launch.
Q · 06 Have you tested it? +
No. Every way in requires a paid account, and opening one to review a product is not something we do. These pages are built from the vendor's pricing pages, product documentation, the plan sheet its docs call canonical, and the terms of use — all read on the date stamped at the top, with contradictions published rather than resolved. Where we have run a tool ourselves, the page says so and links the runs; this one does not, so it does not.