Grok Bot Launched From a Cursor Domain. That's Not a Mistake.

What happened

SpaceXAI (Elon Musk’s AI company, operating under that name since it merged with SpaceX earlier this year) launched Grok Bot in beta on August 11. The pitch: give it a task and it works on its own, on its own cloud computer, signing into the tools and apps you already use, an inbox, a CRM (the software a sales or support team uses to track customers and deals), a ticket tracker, and finishing the job before checking back in with you.

The confusing part is who gets it first. Beta access isn’t a new purchase. It’s bundled into SuperGrok Heavy, SpaceXAI’s own top consumer tier, and separately into Cursor Ultra and Cursor Teams Premium, the priciest plans of Cursor, the coding assistant most BuilderWithin readers know as its own company. Even the download link in xAI’s announcement points to a cursor.com address.

That’s not a scraping error. Cursor’s parent company, Anysphere, is in the process of becoming part of SpaceX. CNBC reported that SpaceX signed a binding agreement in June to buy Anysphere for $60 billion, paid in SpaceX shares rather than cash, exercising an option it had secured back in April. Elon Musk said on an earnings call that regulatory clearance was “almost all” done and that closing should happen “quite soon.” Multiple outlets have reported the deal is expected to close by the end of this month.

Grok Bot is being described as the first product to ship out of that pending combination. According to reporting from The Information, the product started life inside Cursor under the internal code name “Sand,” which is still visible in its download URL. People described as familiar with the plans told The Information the Cursor brand will likely be phased out on new products over the coming months, though Cursor has no immediate plans to rename its existing coding assistant. None of this has been confirmed directly by SpaceX or Cursor leadership. It’s reporting, not an official statement, and the companies themselves haven’t laid out a public timeline for what changes and when.

Why it matters

Two separate things are colliding here, and it’s worth pulling them apart.

The first is ownership. If you build workflows, docs, or training material around Cursor today, that roadmap now sits inside a much larger company’s strategy, not an independent startup’s. Pricing, plan structure, and even the name itself are things reported as still being decided rather than settled. That’s a different kind of risk than a normal feature update: it’s about whether the tool you depend on stays recognizable, not whether one release is good.

The second is what Grok Bot actually asks of you. The beta explicitly signs into “platforms with no clean API or MCP” (the standard, purpose-built connections most software uses to talk to another service). In plain terms, that’s xAI’s way of saying Grok Bot may use your actual saved logins on sites that don’t offer that safer, narrower connection. That’s a real permission surface: an agent with standing access to your email, CRM, or ticketing system can take an action in one of those accounts, sending a message, closing a ticket, updating a record, before you’ve reviewed it, if it misjudges where a task’s boundary is. xAI says Bots “only come back when something needs your approval,” but that approval boundary is the agent’s own judgment call, not a hard technical limit you can inspect in advance.

Who should care

This is most relevant if you’re already paying for Cursor Ultra, Cursor Teams Premium, or SuperGrok Heavy and are about to see a new “Grok Bot” option show up in your account. It also matters if your team has built process, documentation, or onboarding around Cursor’s current name and pricing, since both are reported to be in flux. It matters less if you’re on a lower Cursor tier that doesn’t include the beta, or if you don’t use SpaceXAI products at all.

What builders should do next

Before you connect Grok Bot to anything, check exactly which accounts and services you’d be granting it access to. The product description explicitly targets tools without that safer, purpose-built connection, so assume it’s signing in with your real credentials rather than a limited permission you can cut off later, unless SpaceXAI’s own documentation says otherwise for that specific integration.

Run one bounded test before trusting it with anything that has side effects you can’t undo. Give it a single task with an obvious stopping point, for example, “draft a reply to this one email thread, but don’t send it.” Then check two things: did the draft correctly reflect the thread (correctness), and did it actually stop and wait for your approval instead of sending automatically (failure recovery). Only expand what you hand it once both hold up on a task you can fully verify by hand.

Finally, don’t treat “Cursor” as a fixed reference point in your own materials right now. If your documentation, training, or client-facing content names the tool directly, keep an eye on SpaceXAI’s and Cursor’s own channels over the coming weeks rather than assuming today’s name and plan structure will still apply the next time you check.

End of article