On September 3, xAI announced Grok Bot for Enterprise — an org-wide rollout of its cloud-based computer-use agent, complete with access controls, network controls, and audit trails, plus a two-week free trial for “all Grok and Cursor enterprise customers,” who can invite their whole organization “including people without an existing seat.” Cursor CEO Michael Truell confirmed the tie-up the same day on X: “Grok Bot for enterprise is out today. We’re making it free for all Grok and Cursor enterprise customers for the next two weeks… Deploying Bot has felt like onboarding thousands of capable teammates.”
That’s a real, dated, primary-sourced announcement. It’s also a good moment to check something this blog flagged as unresolved three weeks ago: whether Cursor is quietly becoming a distribution channel for xAI’s agent product, or whether the two brands are staying genuinely separate under their shared corporate parent, SpaceXAI.
From a gated premium perk to bundled-everywhere-plus-enterprise#
Grok Bot isn’t new. xAI launched it on August 11 — three days before SpaceX’s $60 billion acquisition of Cursor’s parent company, Anysphere, formally closed — as a general-purpose autonomous agent that runs “on its own computer in the cloud” and can use any app or website the way a person would. At launch, this blog noted it was gated behind SuperGrok Heavy, Cursor Ultra, and Cursor Teams Premium — the top-tier plans on both sides of the newly merged company.
That gate has been dropping steadily since. By August 26, Grok Bot was folded into every paid individual Cursor plan, not just Ultra. As of September 3, per Cursor’s own documentation, it’s “included with every paid individual Cursor plan and with the Cursor Teams plan” outright, plus a new Enterprise tier with its own admin controls, private-network support, and a “recommended rollout baseline.” In under a month, Grok Bot went from a premium-tier bonus to a default feature bundled across Cursor’s entire paid lineup.
The capability itself#
Whatever you call it, the underlying product is genuinely capable on paper. Per xAI’s own materials, each Bot works in its own isolated cloud environment, has no access to anything by default until a user explicitly grants it, learns a workflow from a single demonstration plus corrections, and can message and share context with other Bots. Bots keep running after you close your laptop — the same “survives past your session” property that makes Claude Code’s background agents and Anthropic’s Managed Agents useful for real overnight work. xAI’s own use-case list leans heavily non-coding: sales webinar monitoring, overnight recruiting prospecting, marketing Q&A distribution, and finance teams claiming “tens of thousands of dollars” in vendor-spend savings. Engineering shows up as one bullet among several — “PR monitoring, overnight audits” — not the headline. xAI also claims “millions of bots created” since launch and names Legora, Supermicro, and ServiceTitan as customers. None of that adoption data is independently verified; it’s xAI’s own account of its own product, and it should be read that way.
The tell is in the documentation, not the press release#
Here’s the part worth sitting with. xAI’s own announcement is unambiguous about ownership — this is xAI’s platform, and Cursor enterprise customers are one beneficiary group among several getting a limited-time freebie. Cursor’s own documentation page for the same product reads differently. It opens: “Grok Bot gives you Bots you can keep around: AI teammates with names, jobs, and context that compounds over time. Each Bot works on a persistent cloud computer with a browser, filesystem, and terminal, so tasks finish in your real tools instead of as chat drafts.” Nowhere in that page does xAI get named as the builder. It’s presented as a Cursor capability, full stop — included with a Cursor plan, run from a Cursor dashboard, described in Cursor’s own product voice.
That’s a genuine shift from three weeks ago. When this blog covered the original August 11 launch, the evidence pointed the other way: Cursor’s community forum used the exact title “Introducing Grok Bot,” xAI’s own post made no claim about Cursor’s branding disappearing, and Cursor had just shipped an entirely separate, Cursor-branded product (Origin, a GitHub competitor) four days after the acquisition closed. The conclusion then was that Cursor was continuing to operate as a distinct product line under its new parent, not dissolving into the Grok brand. The documentation now tells a subtler, messier story: Cursor isn’t disappearing into Grok — but the specific capability that makes Cursor look autonomous is quietly being re-labeled as Cursor’s own, with no visible credit to the company that actually built it.
Why this matters more than a branding footnote#
This blog’s running argument about Cursor has never been that it’s a bad product — it’s that Cursor’s core architecture is an IDE-anchored, human-in-the-loop coding assistant, and every attempt to bolt genuine autonomy onto that architecture (Background Agents, Composer 2, the SDK’s sandboxed cloud VMs) has relocated the ceiling rather than removed it. Grok Bot is the clearest version of that pattern yet, because it isn’t even a coding-specific agent — it’s a general computer-use bot, built by a sibling company under the same corporate parent, imported wholesale and relabeled with Cursor’s own product voice.
Compare that to how Anthropic ships autonomy: Claude Code’s background agents, Agent Teams, Managed Agents, and scheduled Routines are built by the same organization that trains the underlying model, running on the same terminal-native, headless architecture whether you’re at your laptop or asleep. There’s no second company’s product to import and rebrand, and no documentation page quietly omitting who actually built the thing doing the work. Cursor now has an answer to “what happens when you close the laptop” — it just isn’t an answer Cursor’s own engineering built.
Sources: xAI — Grok Bot for Enterprise (primary, Sept 3, 2026); xAI — Introducing Grok Bot (primary, Aug 11, 2026); Cursor — Grok Bot documentation (primary); Michael Truell, X post, Sept 3, 2026; this blog’s prior coverage, Cursor Launches Origin (Aug 19, 2026, includes original Grok Bot sourcing and the Sand/branding-phase-out fact-check).