Last verified

SpaceXSI · Grok Bot

Grok Bot: a hosted computer with agents on it

SpaceXSI'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, comes with Premium and above on The X Subscription, spends the pool that plan shares with Cursor and Grok, and we have not run it ourselves.

Cheapest way in Free, then $30/mo
Free tier Yes
Ways to buy it 5
Oldest check 2026-10-29
§ 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 changed on 12 October 2026 and is worth saying out loud. The product is SpaceXSI's. It is now sold as part of The X Subscription — one plan for Grok, Grok Bot, Cursor and X — whose merchant of record is X Subscription Corp, while prepaid top-ups are sold by Anysphere, the company behind Cursor. Sign-in goes through the shared xAI sign-in, and the admin and team documentation still lives on Cursor's site. Readers who reached Grok Bot through a Cursor plan or a linked SuperGrok subscription before October keep that arrangement, with a Cursor meter and Cursor's refund policy. None of that is hidden, but it is spread across three 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 and subscription documentation, the plan sheet its own docs call canonical, and the bundled subscription terms dated 7 October 2026. 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 →

Five ways in, and the thing none of them buys is Grok Bot: every one is a tier of The X Subscription that includes it. The rule that catches people is the pool — Grok Bot spends the same weekly allowance as Cursor and the Grok apps, so a tier is only as large as everything else you do with it.

Route Bought as Price
Premium Subscription $30/mo $25/mo billed annually
Super Subscription $100/mo $84/mo billed annually
Ultra Subscription $200/mo $167/mo billed annually
Teams Per seat $30/seat/mo
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 older strict privacy setting — Privacy Mode (Legacy) — is not supported: accounts on it are asked to switch before starting, and for teams it blocks Grok Bot entirely. Training opt-out has no control of its own either; it follows the account's privacy settings. With Privacy Mode on, the documentation says customer data is not used for training and that the system defaults to not training when the setting cannot be verified.
You need a hard ceiling on what it can spend Two published facts sit badly together. There is no Grok Bot spend cap of its own — the documentation says so in as many words — so the only ceiling is the subscription's monthly additional-usage limit, which covers everything paid on the account at once. And the included pool is shared: a routine that loops overnight spends the same allowance your Cursor agent and the Grok apps live on, so the first sign of it may be an editor that has run out on Tuesday. For an agent that works unattended on a schedule, start with approval rules and a set cap 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.
You were going to start on the cheapest plan The X Subscription has two tiers below the ones that include Grok Bot. Plus, the cheapest paid tier, carries Grok Chat, Voice, Imagine, Build and Cursor's agent, and the vendor's feature matrix marks Grok Bot as not included on it; Free does not include it either. Premium is the first tier with Grok Bot, and every Teams seat starts there too — Plus is not sold to teams.
§ 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 a subscription and nothing else — different products, different documentation, different availability. Grok Build is on every tier of The X Subscription including Free; Grok Bot starts at Premium.
Q · 02 Who actually bills me for it? +
Since October 2026, X Subscription Corp, which sells The X Subscription and is its merchant of record. Prepaid top-ups for usage past the pool are sold by Anysphere, the company behind Cursor, and are non-refundable except where the law requires. If you still reach Grok Bot through a legacy Cursor plan, Anysphere bills that plan; a linked SuperGrok or X Premium subscription is billed by xAI or X. If you bought through a phone app store, Apple or Google is involved again.
Q · 03 Do I need a Cursor account to use it? +
Not as a separate step on The X Subscription. Grok Bot uses the shared xAI sign-in, and the subscription's workspace holds Grok and Cursor together under one bill. The old route was different: before October every way in ended at a Cursor account, and a linked SuperGrok subscription was attached to it permanently. Teams seats still sign in with the team's Cursor account.
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? +
Yes, now. The product page says Grok Bot is generally available for Enterprise and for teams on the Teams plan, and the documentation describes an admin switch that turns it on for everyone or for named groups. In September three vendor pages gave three different answers, including a waitlist line in the August launch post; the product page and the documentation now agree.
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 and subscription documentation, the plan sheet its docs call canonical, and the bundled subscription terms — 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.