What Is Grok Bot?
Grok Bot is xAI's app for always-on AI teammates that share a cloud computer and work across your apps. How it differs from @grok, Grok Build, and Cursor.
Grok Bot is an app from xAI (which now publishes as SpaceXAI) for creating AI teammates, called Bots, that do multi-step work in your real tools. Each Bot has a name and a job. All of your Bots share one always-on cloud computer with a browser, a filesystem, and a terminal, so they can sign in to websites and apps, keep working after you close your laptop, run routines on a schedule, and message each other to hand off work. You talk to them the way you'd text a coworker.
It isn't a coding agent, and it isn't the @grok chatbot. xAI's own examples are mostly business operations: sales outbound, inbox triage, recruiting, invoices, refunds, and CRM hygiene. Bug fixes are one example among many.
Who runs it: xAI makes Grok Bot, but it runs on Cursor's infrastructure. You sign in with a Cursor account, the cloud computers run in Cursor's cloud, and usage is billed through Cursor.
Where it runs: xAI's docs list macOS, Windows, Linux, iPhone/iPad, and Android as of September 21, 2026. Some of xAI's and Cursor's own pages still list fewer platforms (details below).
Who can use it: Access is included with paid individual Cursor plans and Cursor Teams, or you can link an individual SuperGrok, SuperGrok Plus, SuperGrok Heavy, or X Premium+ subscription. Enterprise access goes through your Cursor account team.
Grok Bot vs @grok vs Grok Build vs Cursor cloud agents
These four names get mixed up constantly, including in search results. They're different products.
| Name | What it is | Who it's for | Where the work happens |
|---|---|---|---|
| Grok Bot | Named AI teammates that do multi-step work across apps and websites | Anyone handing off operational work: sales, ops, support, recruiting, finance, and some engineering | One persistent cloud computer per user, shared by all their Bots, hosted by Cursor |
| @grok / Grok | xAI's chat assistant on grok.com, the Grok apps, and X, where you can tag @grok in a post | People who want answers, images, writing help, and web/X search | A chat conversation. Grok has its own features, such as Automations, that aren't Grok Bot. |
| Grok Build | xAI's coding agent and terminal app, with plan mode, skills, plugins, and hooks | Developers working in a codebase | Your machine and repositories. xAI says it's now powered by Grok 4.7. |
| Cursor Cloud Agents | Cursor's coding agents that run in isolated cloud VMs with a cloned repository | Engineering teams | A per-task dev environment that works on a branch and pushes changes back |
If you searched "grok bot" hoping to chat with Grok on X, you want @grok or grok.com. If you want an agent to change code in a repository, you want Grok Build or a coding agent like Cursor's. Grok Bot is for handing off jobs that span several business tools.
Grok Build: xAI's terminal coding agent, its current model, free access, and privacy controls
entityHow Grok Bot works
The shared computer
This is the detail most write-ups skip, and it matters.
All of your Bots use one cloud computer. They share its files, browser cookies and signed-in sessions, and command-line credentials. Sign in to a site for one Bot and every Bot can use that session. Each Bot gets its own screen on the computer, so several can work at once, but one Bot can run only one computer-use task at a time.
xAI's docs are blunt about what this means: the screens are "not separate security boundaries," and you shouldn't use separate Bots as a security boundary. Between users, isolation is strict: xAI's teams docs say each user gets a dedicated Firecracker microVM.
Your local Mac or PC is separate. A Bot only runs commands on your own machine if you allow it, and the default is to ask every time.
Supported platforms
Official sources don't agree yet. The x.ai/bot product page FAQ still says desktop means macOS or Windows and mobile means iOS. Cursor's own Grok Bot docs page lists macOS, Windows, Linux, and iOS, with no Android. xAI's docs are the most recently dated and specific, and the Android app is live on Google Play under the SpaceXAI developer name. Pages that say Android or Linux isn't supported are out of date.
The Bots themselves don't run on your device. The apps are clients for chatting, reviewing, and approving. The work happens in Cursor's cloud.
Who can access Grok Bot
As of September 26, 2026, per Cursor's Grok Bot plans page and xAI's docs:
- Cursor: included with every paid individual Cursor plan (Pro, Pro+, Ultra) and self-serve Cursor Teams. Higher plans get more weekly usage.
- Grok or X subscribers: link an individual SuperGrok, SuperGrok Plus, SuperGrok Heavy, or X Premium+ account to get a Grok Bot usage grant on a Cursor account. SuperGrok Lite, SuperGrok Team, and SuperGrok Enterprise don't qualify.
- Enterprise: available through your Cursor account team. xAI announced enterprise availability on September 3, 2026.
- Usage: included usage resets weekly. After that, on-demand usage is billed through Cursor if you've turned it on. Cursor also describes a free trial that works as a usage credit.
xAI describes Grok Bot usage as separate from your regular Grok and Cursor usage. Cursor says Grok Bot usage on a self-serve Teams seat draws from that seat's allowance, and on-demand spend counts toward your account-level Cursor limit. A Cursor plan and a SuperGrok link don't stack.
The plan list has widened since the August 11 launch, so check the date on anything you read about who can get it or what it costs.
Grok Bot pricing: every qualifying plan, weekly and on-demand usage, SuperGrok and X Premium+ linking, and the free trial
costGrok Bot and Cursor
Grok Bot is an xAI product, but much of it runs on Cursor:
- You sign in with a Cursor account. Grok Bot uses Cursor authentication, privacy settings, and training opt-out.
- The cloud computers are Cursor-hosted. Grok Bot doesn't support on-premises or bring-your-own-image deployment.
- Usage is metered and billed on your Cursor account, even when the grant comes from a linked SuperGrok subscription.
- Team admins manage it from the Cursor dashboard, and it inherits your team's Cursor connector (MCP) policy.
- Cursor chooses the model (see the Grok 4.7 section).
How it differs from a Cursor Cloud Agent. Cursor Cloud Agents are coding agents. Each one runs in an isolated VM with a cloned repository and a dev environment, works on a branch, and pushes changes for review. You start them from Cursor, Slack, GitHub, Linear, or an API. Grok Bot is a roster of long-lived teammates with memory, sharing one computer, working across business apps and websites.
The two connect. xAI's teams and enterprise docs say a Bot can delegate coding tasks to Cursor Cloud Agents, which run on separate computers under your team's Cloud Agent controls. Teams can turn this off.
Grok Bot and Grok 4.7
xAI released Grok 4.7 on September 21, 2026. Its announcement says xAI "trained Grok 4.7 to natively understand the Grok Bot harness, making it better at conversational tasks and general knowledge work."
That doesn't tell you Grok Bot runs Grok 4.7.
So the default model in Grok Bot isn't publicly confirmed. It may not be a single model, and it may not always be a Grok model.
Documented limitations
These come from xAI's and Cursor's Grok Bot documentation. We haven't hit any of them ourselves.
- Bots aren't isolated from each other. They share files, logins, browser sessions, and connectors. Deleting a Bot doesn't remove files or sign-ins it left on the computer.
- Websites can stop a Bot. A site may block automation, expire a session, show a CAPTCHA, or require a human. The Bot is supposed to hand that step to you, not work around it.
- One computer-use task per Bot at a time.
- No model choice. There's no model picker. Enterprise model allowlists are honored by default, but the docs say enforcement isn't guaranteed.
- Legacy Privacy Mode blocks it. Grok Bot needs cloud data storage, so teams on Cursor's Legacy Privacy Mode can't use it.
- US hosting only, with no residency commitment. Grok Bot computers run in the United States, and Cursor's US-only data residency program doesn't apply to Grok Bot by default.
- Cursor-hosted only. No on-premises or bring-your-own-image option.
- No separate spend cap for teams. Account-level on-demand limits apply. A Bot already working can finish past your monthly on-demand limit.
- Approvals don't undo anything. Approving or denying controls the next action, not work already done.
- Prompt injection is reduced, not solved. xAI's security docs say layered controls reduce the risk from malicious web content but don't eliminate it.
- Some features are still rolling out. Teach a task may not be available on every account. Hardware security keys aren't supported on Linux yet.
Where it fits for builders and operators
How approval gates, tool access, and memory fit into an applied agent architecture
conceptWhat a production coding-agent workflow needs, for tasks that belong with a coding agent rather than Grok Bot
workflowChange log
- August 11, 2026 — xAI launches Grok Bot in beta for eligible SuperGrok and Cursor subscribers on desktop and iOS, with an enterprise waitlist.
- August 26, 2026 — xAI says Grok Bot is now included with SuperGrok, Cursor Pro, and all Cursor Teams plans.
- August 29, 2026 — X connector and X plugin added. Paid Grok Bot users get free X API credits to start.
- September 3, 2026 — Grok Bot for Enterprise, with access, network, and audit controls.
- September 21, 2026 — xAI releases Grok 4.7, trained on the Grok Bot harness. xAI's Grok Bot docs, last updated the same day, list macOS, Windows, Linux, iOS, and Android.
- As of September 26, 2026 — Cursor's plans page also lists X Premium+ as a qualifying link. The x.ai/bot FAQ and Cursor's docs page still list fewer platforms than xAI's docs.
How we label public facts, community reports, and inference on this site
conceptSources & Documentation
- xAI: Introducing Grok Bot (August 11, 2026) — Launch, AI-teammate positioning, shared cloud computer, routines, multi-Bot coordination, and internal use cases.
- xAI: Grok Bot is now included with more plans (August 26, 2026) — Plan expansion, separate usage, and example jobs including support refunds, inbox management, and office operations.
- xAI: Grok Bot now works with X (August 29, 2026) — X connector, X plugin, and X API credits.
- xAI: Grok Bot for Enterprise (September 3, 2026) — Enterprise availability and governance controls.
- xAI: Introducing Grok 4.7 (September 21, 2026) — Grok Bot harness training and the model's listed availability.
- xAI: Grok Bot product page — Positioning, access FAQ, and a platform FAQ that lists fewer platforms than the docs.
- xAI Docs: Grok Bot overview — How Bots work, the shared computer, platforms, and access. Last updated September 21, 2026.
- xAI Docs: Grok Bot FAQ — Full platform list, website blocking, approvals, privacy, skills vs routines, and Teach a task.
- xAI Docs: Use the computer and apps — Shared computer, per-Bot screens, takeover, connectors, and local-computer separation.
- xAI Docs: Approvals, security, and privacy — Auto Review, Ask first rules, the shared-computer boundary, and Legacy Privacy Mode.
- xAI Docs: Grok Bot security — Model selection, US hosting, Cursor-hosted deployment, and prompt injection.
- xAI Docs: Grok Bot for teams and enterprises — Architecture, Firecracker microVMs, Cloud Agent delegation, connector policy, and no separate spend cap.
- Cursor Help: Grok Bot plans and billing — Plan access, SuperGrok and X Premium+ links, weekly and on-demand usage, and the trial credit.
- Cursor Help: Link SuperGrok for Grok Bot — Qualifying and non-qualifying Grok tiers.
- Cursor Docs: Grok Bot — Cursor's copy of the overview. Its platform list omits Android.
- Cursor Docs: Cloud Agents — How Cursor's repository-based cloud coding agents work.
- xAI: Grok Build — Disambiguation only: xAI's coding agent.
- Grok — Disambiguation only: xAI's chat assistant.
- Google Play: Grok Bot — Android app published by SpaceXAI.