What is Grok Bot? SpaceXAI's AI teammates explained

Grok Bot gives you named AI teammates, called Bots, that share one cloud computer and keep working when you close your laptop. SpaceXAI announced it on 11 August 2026 and the launch post calls it a beta; Cursor runs the hosting, the documentation and the billing, so it is bought as part of a Cursor plan rather than on its own. If you want the short version of who it is for: it suits someone who wants an agent to log into real web apps on their behalf and does not mind that the machine it uses belongs to Cursor and sits in the United States.

It is also not the Grok AI chatbot. That is a separate app from the same Google Play developer, and the two are easy to confuse by name alone.

#What is a Bot, exactly?

A Bot is a persistent assistant with a name, a job and context that accumulates. Cursor's overview describes working with one by messaging it: you give it a task, the context and the access it needs, and it handles multi-step work across apps and websites, reporting progress in the conversation and asking for approval when it needs it. Bots can run in parallel, message each other and pass tasks between them.

The part that makes this different from a chat window is the computer. Each Bot works on a persistent cloud computer with a browser, a filesystem and a terminal, and all of your Bots share it, including its files, browser sessions and app logins. Cursor's overview says the computer "belongs to your account, not to an individual Bot", which is why a handoff between two Bots does not mean repeating a setup. SpaceXAI's launch post puts the same idea more plainly: "Bots share a computer of their own in the cloud, so jobs do not stall when you step away."

Two consequences follow from one shared machine, and only one of them is the selling point. A Bot inherits every login any other Bot established, which is convenient and also means there is no separation between them. If that matters for your use, it is a design constraint rather than a setting.

Where an app has no usable API, the Bots use the browser like a person would. The launch post gives that as the reason for the computer: Bots can sign in and operate across apps, inboxes and websites, including those without a clean API or MCP connection.

#Who makes Grok Bot, SpaceXAI or Cursor?

Both, and the split is worth knowing before you file a support ticket.

The announcement lives on x.ai, whose footer reads "© 2026 SpaceXAI LLC". On Google Play the developer behind the Grok Bot app, ai.x.grok.bot, is listed as "SpaceX Super Intelligence", and the same developer publishes the separate Grok AI app, ai.x.grok. Cursor is where the product actually lives: the documentation is on cursor.com/docs/grok-bot, the help pages on cursor.com/help/grok-bot, the Bot computers run in Cursor's cloud, and the plans that include it are Cursor plans. Cursor's pricing page adds a third name, saying subscriptions "are only sold directly through X Subscription Corp."

So three corporate names appear across the pages that describe one product. Nothing about that is irregular, but it does mean documentation questions go to Cursor rather than to SpaceXAI.

#Which plans include Grok Bot, and what does it cost?

There is no standalone Grok Bot price. Cursor's Grok Bot plans page says "Grok Bot is included on Premium, Super, and Ultra", and that Plus and Free do not include it. Matching those tier names against Cursor's pricing page gives the figures below.

Plan	Price on Cursor's pricing page	Grok Bot included
Free	$0/month	No
Plus	$8/month	No
Premium	$30/month	Yes, the cheapest tier that includes it
Super	$100/month	Yes
Ultra	$200/month	Yes, with the highest weekly usage
Teams	$30+/user/month	Yes, for every member
Enterprise	Custom	Access is set up with your account executive

The pricing page lists Grok Bot as an AI feature under Premium, which agrees with the help page.

Two details matter more than the headline number. On a self-serve Cursor Teams plan the help page says every member gets Grok Bot on their account, with "No Premium seat or admin request required", so a team does not have to hand out individual seats for it. And the free trial is not a free month: the help page describes it as "a usage credit rather than a set number of days, though a 7-day window also applies", measured in agent steps and tokens rather than messages. A "Cancel Trial" control appears on free-plan accounts, and using it ends the trial immediately, removes any remaining credit, and the trial cannot be claimed again.

One wrinkle if you read about Grok Bot when it launched. The August announcement named Cursor Pro, Pro+ and Ultra, plus Teams Standard and Premium. Cursor's current help page calls Pro, Pro+ and Ultra "legacy Cursor plans", and Cursor's pricing page lists no Pro or Pro+ tier at all. The tier names in this article are the current ones; if you are on an older plan that still says Pro, the help page says those legacy plans include Grok Bot too.

#What happens when you link a SuperGrok or X Premium+ account?

You get usage, you do not get a plan, and you cannot take it back.

Cursor's plans page is unusually direct about this. Linking is "a usage grant, not a Cursor plan". "A SuperGrok or X Premium+ link is permanent once created", and you cannot unlink it or move it to another Cursor account. It also does not stack: "A Cursor plan and a SuperGrok or X Premium+ link do not add together", and Grok Bot uses whichever of the two grants more weekly usage.

The practical advice is dull and important. Sign in with the Cursor account you actually intend to keep before you create the link, because the documentation describes no way to undo it. If you are on a Cursor Teams seat, the help page says you do not need a separate SuperGrok link and that one would not add to the seat's allowance anyway, so there is nothing to gain by creating it.

#How do you give a Bot a skill or a routine?

Two paths, and neither involves a file you write.

The first is to ask. Cursor's working-with page gives the example of telling a Bot to save the process you just used as a named skill. The second is demonstration, called Teach a task: you perform a browser workflow and the Bot drafts a skill from it. There is a hard limit worth knowing before you plan around it, which is that "Teaching records visible computer interaction for up to ten minutes". The page also notes it does not record microphone audio.

Routines are the scheduling half. A routine can run on a schedule, and it can also start from an event: the page gives "start a routine from an event, such as a Slack message or a GitHub notification". For connected services the page names "services like Gmail, Notion, and Slack".

Group chats are capped. When you create one, you "select two to six Bots".

What is absent from these pages is any mention of a portable skill format. Neither the overview nor the working-with page refers to SKILL.md or to MCP servers, so a skill you wrote for another agent is not documented as working here. If you are comparing agents on that basis, our Cursor hub covers the coding agent's own extension model, which is a different thing from Grok Bot's.

#Where does your data go, and what can a Bot do unsupervised?

Three answers from Cursor's Grok Bot security FAQ, and one of them is a limit rather than a feature.

On location: the Bot computers run "In the United States today". The same page says Cursor's "US-only data residency" programme "does not apply to Grok Bot by default", and directs teams that need a written residency commitment to their account team. If you are buying this for a team with a residency obligation, that sentence is the one to take to your lawyers before the demo rather than after.

On credentials: "Connector tokens stay on Cursor's backend." For things a Bot should never see, values entered in a Secure Form "are filled without the model seeing them". Steps a form cannot handle, such as a single sign-on flow or a passkey, "are handed to the member", which is to say you do them yourself.

On supervision: Auto Review is the gate. It "can let an action proceed, require approval, or deny it", and with enforcement on it evaluates shell commands, app calls, computer use and delegation. The honest caveat is on the same page: it "doesn't review every side effect, such as memory writes and most settings changes". So Auto Review is a check on the actions a Bot takes outward, not a complete record of everything it changes.

For the wider question of what an agent on your own hardware can reach instead, what is OpenClaw covers the self-hosted end of this market, and the OpenClaw hub keeps its current facts.

#Who is Grok Bot actually for?

Someone who wants agents that can use real web applications, who is already paying Cursor or willing to, and who is comfortable with a vendor-hosted machine in the United States.

It is a poor fit in three cases. If you need the agent on your own hardware, the computer is always Cursor-hosted and that is not configurable. If you need data residency outside the United States, the security FAQ says the programme does not cover Grok Bot by default. And if your plan was to bring skills across from another agent, nothing in the documentation promises that.

Availability is still uneven, which fits the beta label. Cursor's mobile help page says "Grok Bot is available on iOS and Android". It refers to a desktop version, telling you to "Use desktop Grok Bot to update, recover, or reset the computer", without naming operating systems on that page; the launch post describes desktop and iOS availability and offers a macOS download. The Grok Bot hub is where we keep its verified facts as they change.

#What we could not confirm

Per-Bot limits on routines, and how long run records are kept. Cursor's working-with page documents routines and their triggers but states no cap on routines per Bot and nothing about retained run history. We have left both out rather than estimate them.

Windows and Linux support. The mobile help page names iOS and Android and refers to a desktop app without naming its operating systems, and the launch post mentions desktop alongside a macOS download. We say desktop exists and that macOS is offered, and make no claim about Windows or Linux.

Whether a web version exists. The mobile page mentions signing in with a Cursor account used on desktop or web without saying that Grok Bot itself runs in a browser, so we do not claim either way.

The Google Play listing for the Grok Bot app itself. The app page returned no readable content when we fetched it, so the publisher in this article comes from the developer page that lists both apps, which names "SpaceX Super Intelligence".

Prices for the SuperGrok tiers. This article prices the Cursor plans because those are the ones Cursor's pricing page lists. We did not verify what SuperGrok, SuperGrok Plus, SuperGrok Heavy or X Premium+ cost, and the plans page treats a link from them as a usage grant rather than a priced route into Grok Bot.