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. It runs tasks on a cloud computer and signs into tools you already use, including email, customer-management software, and ticket trackers. xAI presents it as completing work before checking back with you.
Beta access comes with existing paid subscriptions. xAI lists SuperGrok, SuperGrok Plus and Heavy; Cursor Pro, Pro+ and Ultra; and Cursor Teams Standard and Premium. That includes several tiers of Cursor, the coding assistant many builders know as a separate company. Even the download link in xAI’s announcement points to a cursor.com address.
The launch arrives during SpaceX’s proposed acquisition of Cursor’s parent company, Anysphere. 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.
Why it matters
The proposed deal concerns Cursor’s future ownership. Grok Bot’s account access affects what an agent can do in your tools.
The first is ownership. If you build workflows, docs, or training material around Cursor today, the reported acquisition could place that roadmap inside a much larger company’s strategy if it closes. 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 targets “platforms with no clean API or MCP.” APIs and MCP offer purpose-built connections for software or agents to use another service.
Grok Bot may instead use a signed-in account. Its access then depends on that account’s permissions. An agent with account access may send a message, close a ticket, or update a record before you review it. A mistaken interpretation of the task can therefore affect real work.
xAI says Bots “only come back when something needs your approval.” Check the available account controls before treating that behavior as a guarantee.
Who should care
This is most relevant if you’re already paying for one of the eligible SuperGrok or Cursor plans 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. Check the named plan list before assuming the beta is excluded from your subscription.
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. For each integration, check how it signs in, which actions the account permits, and how to revoke its session or credentials.
Start with a draft-only task in a test account before granting production access. 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.” Check whether the draft reflects the thread and whether the bot waits for approval instead of sending automatically. Use that result to decide whether the tested task is suitable. Keep account permissions narrow when expanding access.
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