Grok Bot Ships Through Cursor Tiers, Not xAI Plans

Grok Bot, xAI’s new AI-teammate product, entered beta on August 11, 2026 — and the most revealing thing about it is the gate. Eligibility does not run through an xAI plan alone: per xAI’s own documentation, you get in with SuperGrok Heavy, Cursor Ultra, or Cursor Teams Premium, and you sign in with a Cursor account. For a product wearing xAI’s brand, nearly everything underneath it — identity, storage, privacy settings, retention — resolves to Cursor.

That matters because of what sits behind it. SpaceX acquired xAI outright on February 2, 2026 — that deal is closed. But SpaceX has only agreed to acquire Anysphere, the company behind Cursor: an all-stock transaction that press outlets reported at $60 billion, announced June 16, 2026, and still pending regulatory approval at the time of writing. Grok Bot’s entitlement structure is, in our reading, the clearest public evidence so far of that pending deal already shaping how xAI ships product.

This analysis walks through what launched and who gets access, the Cursor tier ladder the product is gated on, the identity and data-governance plumbing xAI’s own docs describe, the precise legal status of the two SpaceX deals people keep conflating, and what teams should verify before switching Grok Bot on. Every price and quote below comes from the vendors’ own pages or from named press reporting, each labeled as such.

xAI’s Grok Bot page pitches it as “A new kind of colleague” — an AI teammate you message on desktop or iOS, that takes projects start to end, keeps context on how you work, and comes back when your approval is needed. The product mechanics of the launch — the cloud computer, routines, approvals — are covered in our companion piece on the Grok Bot launch. This post is about something narrower and, for anyone watching the corporate chessboard, more telling: who is allowed in, and whose infrastructure the door is built on.

The eligibility list on docs.x.ai’s get-started page reads, in the vendor’s own words: “An eligible plan: SuperGrok Heavy, Cursor Ultra, Cursor Teams Premium (sign in with your Cursor account).” That is the whole gate. The docs’ eligible-plan list names no standalone Grok Bot plan and no enterprise option. Two of the three qualifying plans are Cursor subscriptions, and the parenthetical applies to everyone — the account you sign in with is a Cursor account.

Platform support at launch: macOS (Apple silicon or Intel) and Windows (x64 or Arm64) desktop apps, plus an iOS app listed separately. The docs are explicit that “Grok Bot is not currently available as a Linux desktop app.”

To understand what “gated to Cursor Ultra” means, you need Cursor’s own ladder. Its pricing page embeds a machine-readable structured-data block — a JSON-LD Offer array — in its HTML, and that block lists five prices: Hobby at $0, Pro at $20, Pro+ at $60, Ultra at $200, and Teams at $40 per user per month for the Standard team tier. The rendered page adds the positioning: Pro+ carries “3x Pro limits on Agent,” Ultra carries “20x Pro limits on Agent” and priority access to new features, and Cursor’s own FAQ says, “We recommend Pro+ for daily agent users, and Ultra for agent power users.”

Grok Bot, in other words, is gated to the very top of Cursor’s individual ladder — the $200 tier Cursor itself positions for “agent power users” — plus the premium variant of its team plan. Nothing below Ultra qualifies.

Now the wrinkle that makes this a story about sourcing as much as pricing. Of the two Cursor tiers that unlock Grok Bot, only one price is corroborated by both companies. Cursor Ultra’s $200/month appears on x.ai/bot and in cursor.com/pricing’s structured data — the two vendor pages agree on that one figure. The $120/seat/month price for Cursor Premium Teams appears only on x.ai’s page: on cursor.com/pricing, Premium is a toggle on the Teams plan with no visible number, and the structured data prices only Teams Standard at $40. On the pages we fetched, Cursor itself publishes no seat price for the tier xAI is selling Grok Bot through.

A price that exists on the reseller’s page but not the owner’s is not automatically wrong — vendors gate prices behind sales conversations all the time. But it is exactly the kind of asymmetry you would expect while two companies are mid-integration: xAI is quoting, packaging and selling Cursor’s top tiers as Grok Bot’s entry points, ahead of Cursor’s own public price list catching up.

Pricing is suggestive; plumbing is conclusive. The strongest evidence for this post’s thesis is not the shared $200 figure — it is what xAI’s own security and privacy documentation says about whose systems Grok Bot actually runs on.

That sentence is xAI’s, not ours, and the docs keep going. The get-started page states, “Grok Bot uses your Cursor account.” The security doc states that “Grok Bot requires data storage and does not support Legacy Privacy Mode,” that privacy and data-sharing choices are managed through Cursor account settings, and that “Training opt-out follows the applicable Cursor account and privacy settings.” For contractual detail, it points readers to Cursor’s own privacy policy and security pages — cursor.com/privacy and cursor.com/security. And on the way out: “Backend retention and account deletion follow the applicable Cursor terms.”

The onboarding flow is Cursor-hosted too. The docs send new users to the Grok Bot access page at cursor.com/bot/onboarding to download the desktop app, and the privacy-settings page a new user must review before the product will start is a cursor.com/dashboard URL. Organizations that require single sign-on complete their normal organization sign-in flow, per the same get-started page.

Add it up: the account, the auth flow, the download page, the privacy-mode gate, the SSO path, the training opt-out, and the retention and deletion terms are all Cursor’s — contractually and technically — while the product ships under xAI’s brand and, as covered above, most of its published price points are stated by xAI. One more operational detail from the same doc rewards attention: “Deleting a Bot does not remove shared-computer files or browser sessions.” Even the residue a departed Bot leaves behind lives under Cursor’s retention rules.

Here is the corporate context, kept deliberately short because the details live in our earlier coverage. Deal one is closed: on February 2, 2026, xAI’s own newsroom announced that “SpaceX announced today that it has acquired xAI.” The merged entity brands itself SpaceXAI — we unpacked that in our analysis of the SpaceXAI rebrand. SpaceX owning xAI is settled fact, on xAI’s own pages.

Deal two is not. On June 16, 2026, SpaceX announced a formal agreement to acquire Anysphere, the company behind Cursor, in an all-stock transaction that CNBC and Forbes both reported at $60 billion. CNBC, citing a SpaceX SEC filing, reported that the company expected the merger to close in the third quarter of 2026 and that it remained subject to regulatory approvals. Neither the $60 billion figure nor the closing timeline appears on any x.ai or cursor.com page we fetched — the deal’s terms live in press reporting and, via CNBC’s citation, a SpaceX SEC filing. The full deal mechanics are in our June breakdown of the SpaceX–Anysphere agreement.

The distinction is the whole point. SpaceX owns xAI; it has only agreed to acquire Cursor’s maker. Every “Grok Bot runs on Cursor” fact in the sections above therefore describes integration happening ahead of a closing, not after one.

None of this requires the deal to have closed, and none of it proves anything improper — companies strike distribution and technology partnerships ahead of mergers all the time. What makes Grok Bot notable is the depth and the direction of the dependency. This is not a co-marketing bundle or an API integration. xAI’s flagship new product cannot be purchased, signed into, configured for privacy, or deleted except through the other company’s accounts, dashboards and terms. The split is clean: xAI holds the brand and states most of the prices; Cursor holds the identity layer, the data, and the contract.

It is also not the first Cursor-shaped move in Grok’s recent history — Grok 4.5 added Cursor data in supplemental training, which we examined in our piece on the Grok–Cursor data flywheel. Grok Bot extends the dependency from training data to product entitlement — a meaningfully deeper coupling, because entitlements are wired into billing, identity and legal terms.

Why would Cursor be the rail? The commercial logic is visible in the reporting around the deal. Per CNBC, Cursor crossed $1 billion in annualized revenue as of a November 2025 release; Forbes separately reported the company had reached $3 billion in annualized revenue by late April 2026. Forbes framed the deal’s rationale as building a vertically integrated AI stack running from chips and training infrastructure through frontier models to the application layer. Gating Grok Bot on Cursor’s top tiers slots an xAI product directly into that application layer — using the subscription machinery of a company SpaceX has agreed, but not yet completed, buying.

Looking forward: if the merger closes in the third quarter as the SEC filing cited by CNBC anticipated, expect the entitlement story to consolidate — one account system, one ladder, and Grok Bot as the anchor product of the combined top tier. If it does not close, the unwind is genuinely messy: a shipped product whose authentication, retention and deletion terms live on the counterparty’s stack. Press accounts of the agreement’s termination provisions differ on the exact figures, so we won’t print one — but the existence of meaningful break terms underlines how committed both sides already are at the product layer.

Launch-day documentation written across two companies’ domains shows its seams, and the seams are instructive. Three stood out in our read of the vendor pages this analysis rests on.

Two more gaps are worth logging as open questions rather than defects. First, none of the four xAI pages we checked — x.ai/bot, the Grok Bot overview, the get-started page and the approvals-security-and-privacy page — names the model that powers Grok Bot; treat that as unstated, not as any particular model. Second, the docs’ eligible-plan list names no enterprise plan, which for an agent product aimed at team workflows is a conspicuous absence — larger organizations evaluating rollout have no published path on the pages we fetched.

If the analysis above is right, then evaluating Grok Bot is really evaluating two vendors mid-merger — and your checklist should reflect that. Here is how we would slice the decision by buyer profile.

For team-scale rollouts, the governance surface — admin controls, org-wide privacy settings, seat management — is Cursor’s, so the homework overlaps heavily with evaluating Cursor itself; our guide to Cursor Organizations and enterprise AI-coding governance covers that layer in depth. And if you want a second set of eyes on the whole dependency map — entitlements, data terms, exit costs — this is exactly the kind of pre-adoption diligence our AI transformation engagements are built around.