Grok Bot Explained: The Cloud AI Teammates Included with Cursor Plans

Grok Bot is a separate desktop and mobile app from Cursor and xAI together (SpaceXAI, the company most of us still call xAI), included with paid Cursor and SuperGrok plans. It runs on macOS, Windows, Linux, iPhone, iPad, and Android, and it gives you a roster of cloud "AI teammates" called Bots that work on a persistent cloud computer while your laptop is closed. Nothing about it lives inside the editor: you sign in with your Cursor account, the Bot computer runs in Cursor's cloud, and usage is metered on that account.

This page sits inside the Cursor guide because your Cursor subscription is how you pay for it. Nothing about Grok Bot lives inside the editor, and I'll say that a few more times below because the marketing makes it easy to assume otherwise.

What Grok Bot Is

xAI launched Grok Bot in beta on 11 August 2026 and describes it as AI teammates you can give real work to. A Bot is a durable teammate with a name, a job, its own conversation and its own working context, and it can sign in to your tools and use them the way you would. You talk to it in a message thread on the desktop or mobile app, the same way you'd message a colleague.

You can have roughly 50 Bots on one account, put 2 to 6 Bots in a group chat, and let Bots hand work to each other while you're away. Skills are reusable instruction sets shared across Bots, and routines run one Bot on a schedule or on an event such as a Slack message or a GitHub notification. A Bot can also watch you do a browser workflow once, up to 10 minutes, and draft a skill from it.

My take so far is that the product is aimed at the work around your code rather than the code itself. xAI's own use-case list has no pure coding job on it. The closest entries are a bug reproduction Bot that turns reports into reliable reproduction packs and a website builder that builds, buys the domain and deploys.

Voice, Tesla and Other Recent Additions

Grok Bot changes weekly, so these are the additions since launch that change how you would use it, checked on 30 September 2026.

• Voice: you can dictate a message, start a live voice chat on desktop, iPhone and Android, and play voice memos a Bot sends back. In my testing each Bot can also have its own voice, which makes a roster of Bots easier to tell apart on a call.
• Drafts you approve: when a Bot prepares an email or a Slack message, the conversation shows an editable draft with Send and Discard buttons, so nothing goes out until you press Send.
• Tesla: Tesla announced Grok Bot in its cars on 22 September, Yahoo Autos reported, starting with SuperGrok Heavy subscribers, so a driver can hand a Bot errands, email and calendar work by voice. Tesla's Grok support page lists what the car needs: an AMD processor, software 2025.26 or later, and Premium Connectivity or Wi-Fi.
• Team Bots: a shared Bot for a whole team, in public beta since 28 September, covered in the plans section below.
• Passwords: xAI's security docs say Grok Bot is not a general-purpose password manager. For passwords, passkeys and 2FA it hands you the computer, and on Enterprise a Team Setup script can install a password manager on the Bot's computer for passkeys.

How the Cloud Computer Works

Every Bot on your account uses the same computer, and xAI's overview page describes it as a persistent cloud VM, and Cursor's Teams docs call it a dedicated Firecracker microVM. That machine has a browser, a command line, a filesystem and a durable /workspace folder for files you want to keep. Bot computers run in Cursor's cloud infrastructure, which is the second half of the Cursor tie.

Browser cookies and signed-in sessions are shared across the computer, so signing in for one Bot makes that session available to your other Bots. Between users the isolation is strict, with each user's computer dedicated and hardware-isolated. Inside your own account, though, a login or a file placed on that machine is visible to every Bot you create.

• The computer stays on when you close the Grok Bot app or shut the laptop.
• Durable project files belong in /workspace, and everything else is replaceable.
• Update, Recover and Reset are the three recovery options, and a reset can discard unsaved work.
• Save each Bot's instructions somewhere outside the computer too, so a reset never costs you the setup.

Web traffic normally leaves from the cloud computer. The Route egress through this desktop setting sends it through your own desktop instead, so sites see your desktop's IP address and the Bot can reach networks that desktop can reach. It applies to one desktop at a time, and an Enterprise admin can switch it off for the whole team.

What Cursor Plans Include

There is no separate Grok Bot login. You sign in with your Cursor account, SSO included, and paid Grok Bot access comes with usage that resets weekly. That usage is metered on your Cursor account rather than on Grok or X, and if on-demand spend is enabled, extra Bot usage can continue on the account's shared on-demand balance.

After three rounds of expanded eligibility in August 2026, both xAI's current setup guide and Cursor's overview now list every paid individual Cursor plan, Cursor Teams, and individual SuperGrok plans.

On 28 September 2026 xAI opened Team Bots in public beta on Teams and Enterprise plans. The owner sets up one Bot and publishes it to the team, each teammate's conversations with it stay private, and the usage counts against that teammate's own Grok Bot allowance rather than the owner's. A personal Bot posts to Slack as you, with a "Sent using Cursor" label, while a Team Bot can have its own Slack app and posts as itself.

Date	Who Got Access	Where It Was Announced
11 Aug 2026	SuperGrok Heavy, Cursor Ultra, Cursor Teams Premium (beta)	xAI news post and the Cursor forum
21 Aug 2026	SuperGrok Plus, Cursor Pro+, all Cursor Teams	xAI's "more plans" post (since rewritten for the 26 August widening) and the Grok Bot account on X
26 Aug 2026	All SuperGrok, Cursor Pro and Cursor Teams plans	xAI "more plans" post and Cursor's plans page

The matrix below was checked on 30 September 2026. Prices are the ones printed on the vendor pricing pages, and where a page did not print one I've left the cell blank rather than guess.

Plan	Price Printed on the Vendor Page	Grok Bot Access
Cursor Pro	$20/month	Included, with weekly usage that resets
Cursor Pro+	$60/month	Included with higher weekly usage limits
Cursor Ultra	$200/month	Included with the highest weekly usage limits
Cursor Teams Standard	$40/user/month	Included, follows the Teams allowance
Cursor Teams Premium	$120/user/month	Included, higher usage allowance
Cursor Enterprise	Custom	Admin enablement through dashboard
SuperGrok	$30/month	Included once you link your Grok account
SuperGrok Plus	$100/month	Included once you link your Grok account
SuperGrok Heavy	Not printed on the fetched page	Highest linked usage
X Premium+	Not printed on the fetched page	Linked usage, per Cursor's plans page only
SuperGrok Lite, SuperGrok Team, SuperGrok Enterprise	Varies	Excluded

SuperGrok and X Premium+ holders link their Grok account from the Grok Bot plan screen, and Cursor is careful to call that a usage grant rather than a Cursor plan. Your Cursor plan stays exactly what it was. X Premium+ shows up only on Cursor's plans page, so treat that row as Cursor's word until xAI prints it too.

The tools hub ranks Cursor first partly because paid plans now include Grok Bot, and I stand by that even though the two products barely touch. A $20 plan that bundles a cloud teammate is a better deal than the same editor without one.

What Grok Bot Is Not

This is the section I wish the launch posts had led with. The Cursor changelog since 1 August has no Grok Bot entry and no editor-side feature, and Grok Bot appears there only as an external product link. Tab and Agent carry on exactly as before, and so do the files on your disk.

• It has no editor integration, and none is documented on either vendor's site today.
• It does not drive the Chrome or Safari on your laptop. The browser it uses lives on the cloud computer.
• It cannot see a service that only listens on your localhost unless you enable local commands and approve each one.
• The desktop app supports macOS, Windows, and Linux. xAI's mobile guide links iPhone and Android downloads; Cursor's overview has not added Android yet.
• It requires cloud data storage, so a Cursor account on Legacy Privacy Mode has to change that setting first.

The local-command path deserves its own warning. Running a command on the Mac or Windows machine in front of you needs per-command approval, and Cursor's Teams docs let an admin disable it for the whole org. That is the right default, and I'd leave it off until a job needs it.

Which Jobs to Hand a Bot

Hand a Bot the work that lives in web apps and inboxes. Repo edits, tests and pull requests stay with a coding agent that has the checkout open, whether that is Claude Code, Codex, or the Cloud Agents that ship with Cursor itself.

The one bridge between the two worlds is delegation. Cursor's Teams docs say a Bot can hand a coding task to Cursor Cloud Agents under your existing team controls, and that toggle defaults to on. So a routine that watches a GitHub notification can triage the issue on the cloud computer and then spawn a Cloud Agent to write the fix.

Tool	Where the Agent Runs	What It Hands Back
Grok Bot	One persistent cloud VM per user, shared by every Bot	Finished work inside the actual apps, or a delegated Cloud Agent task
Cursor Cloud Agents	Isolated Cursor VM with the repo cloned	Merge-ready pull requests with screenshots and logs
Claude Code	Your terminal, IDE or desktop, plus cloud routines	Local edits, commits and pull requests
Codex cloud	Isolated cloud environment per repo	A diff, then a pull request when you ask for one

My take is that Grok Bot competes with your inbox and your browser tabs, and the coding agents compete with each other. I'd keep Claude Code for anything that touches a checkout, and give the Bot the reproduction packs, the vendor dashboards and the scheduled chores that eat a Monday morning.

Start a First Bot Job

Install the desktop app for macOS, Windows or Linux, sign in with the Cursor account you already pay for, and create one Bot with a short name and one job. Send a first message that names the outcome, the sources, the constraints and the point where you want it to stop for review. The prompt below is the bug reproduction job from xAI's own use-case list, trimmed to my shape.

Take the three newest bug reports in our Linear triage view.
For each one, reproduce it in the staging app in your browser and record the exact steps, the expected result and what actually happened.
Save one markdown file per bug in /workspace/repro/ with screenshots attached.
Do not comment on the Linear issues or open any pull request. Stop and message me when the three files are ready.

You can attach up to 6 files per message on desktop, with documents capped at 25 MB and video at 200 MB. Type / to pick a skill and @ to pull another Bot into the thread, and use Stop now if the job drifts. When the Bot hits a password, a 2FA prompt or a CAPTCHA, xAI's guidance is that the Bot should hand you control of the computer, so complete only that step and hand control back.

Keep Usage and Approvals Visible

Paid access includes usage that resets weekly, and neither vendor prints the size of that pool on its public pages. Watch the plan screen during the first week and treat a trial credit as spent the moment a long job starts. Cursor's plans page says extra Bot usage can continue on shared on-demand spend, which is convenient right up until the invoice arrives.

xAI tells you to keep sending messages, publishing, purchases and transfers, deleting or overwriting data, permission changes, production changes and legal terms behind explicit approval boundaries you set for each Bot, and its Auto Review can enforce them. Desktop offers Allow once, Deny or Always allow, and the mobile app lets you approve or deny a step when you are away from your desk. Auto Review rules can force an approval or always-allow a class of action for a Bot.

One line from xAI's security page is worth pinning above your desk. An approval controls the proposed action, and it does not reverse work already completed. Write the boundary into the Bot's instructions as well, so a later routine can't widen the job while you're asleep.

• Check the plan screen before you hand over anything that could run for hours.
• Keep one Bot per role instead of one catch-all teammate that learns every login.
• Never use a second Bot as isolation, because every Bot shares the same computer and cookies.
• Leave local-computer commands off until you have a job that genuinely needs them.

FAQ

Is Grok Bot part of the Cursor editor?

No. It is a separate desktop and mobile app from Cursor and xAI together, and nothing about it lives inside the editor. The Cursor tie is your account, Cursor's cloud, and billing: you sign in with your Cursor account, the Bot computer runs in Cursor's cloud, and usage is metered on the Cursor account. No editor integration is documented anywhere on either vendor's site.

Does Grok Bot run on my own computer?

No, every Bot works on a persistent cloud VM, which Cursor's Teams docs describe as a dedicated Firecracker microVM. Running a command on the Mac or Windows machine in front of you needs per-command approval, and Teams admins can switch that off for the whole org.

Do all my Bots share one cloud computer?

Yes, every Bot on your account uses the same computer, including its files, browser cookies and signed-in sessions. Between different users the isolation is strict and hardware-level. xAI's computer docs say separate Bots are not separate security boundaries.

Does Grok Bot eat my Cursor or Grok usage?

No, Grok Bot has its own usage pool that resets weekly, and Cursor meters it on your Cursor account rather than on Grok or X. If your account has on-demand spend enabled, extra Bot usage can continue on that shared on-demand balance.

Is there a Linux desktop or Android app?

Yes, the Grok Bot desktop app now runs on Linux alongside macOS and Windows. xAI's mobile guide covers iPhone and iPad on iOS or iPadOS 18 or later, and Android 9 or later, and links both app stores. Cursor's overview still lists only iPhone, so use the current download links for your device.

Can a Bot write code in my repo?

A Bot can delegate a coding task to Cursor Cloud Agents, which clone the repo in a Cursor VM and hand back a merge-ready pull request. The Bot itself is built for work that lives in web apps and inboxes, and it does not have your checkout open.

Is there a free trial for Grok Bot?

Yes, Cursor's plans page describes the trial as a usage credit inside a 7-day window. A long first job can burn most of that credit in one go, so give the first Bot something bounded before you let it run overnight.

Which model does Grok Bot use for its Bots?

Cursor manages model selection on your behalf, and the Teams docs say there is no customer-facing model picker. You choose the Bot's name, job and instructions, and the model behind it is not something you configure today.

Where to Go Next

• Best AI coding tools: the ranking where Cursor sits first, with the Grok Bot bundle as one of the reasons.
• Cursor guide: the editor, the models and the plan names your Grok Bot access hangs off.
• Cursor Origin hosted codebases: the option when a job needs a Cursor-hosted remote rather than a Bot.
• Cursor Automations: scheduled cloud agents that stay inside Cursor and hand back pull requests.

Plan eligibility, usage metering, platform support and computer limits were checked against the cited xAI and Cursor pages on September 30, 2026.