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

Grok Bot is a desktop and mobile app from Cursor and xAI that gives you persistent AI teammates for browser, file, and connected-app work. Your Bots share a cloud computer that keeps working while your laptop is closed. Each Bot has its own instructions and conversation, but its files and signed-in browser sessions are shared with your other Bots.

I see its strongest role in the work around coding: reproducing bugs, checking vendor dashboards, collecting research, and handling recurring chores. Access is bundled with qualifying subscriptions, including the current Premium, Super, and Ultra plans; it is not included with every paid plan.

What Is Grok Bot?

Grok Bot combines persistent conversations with a cloud computer and tools that let an agent act on a task. xAI launched the product in beta on August 11, 2026. 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. Examples include a bug reproduction Bot that turns reports into reliable reproduction packs and a website builder that builds, buys the domain and deploys.

Team Bots let a whole team work with a shared Bot. That is separate from giving your own Bots different roles or putting them in a group chat.

Which Jobs Should You Give Grok Bot?

I would give Grok Bot browser and inbox work, including bug reproduction, vendor-dashboard checks, research, and scheduled chores. I would keep repository edits, tests, and pull requests with a dedicated coding agent such as Claude Code, Codex, or the Cloud Agents that ship with Cursor itself.

Delegation is one way to connect the two workflows. 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	Proposed pull requests with screenshots and logs to review
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.

How Does Grok Bot’s Cloud Computer Work?

Grok Bot runs your Bots on one persistent cloud computer per account, with a browser, terminal, and shared files. xAI's overview page describes this shared workspace, and Cursor's Teams docs call it a dedicated Firecracker microVM. It includes 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.

Which Plans Include Grok Bot?

On the current X Subscription, Premium, Super, and Ultra include Grok Bot; Free and Plus do not. Legacy paid Cursor plans and qualifying linked Grok accounts have separate eligibility rules. Check the plans and billing guide for your account before subscribing.

The distinction also affects usage. Current plans share a weekly pool across Cursor, Grok, and Grok Bot, with prepaid credits for additional usage. Legacy accounts retain weekly Grok Bot allowances and optional on-demand billing. Linked legacy grants do not stack with a Cursor allowance.

The AI coding tools ranking ranks Claude Code first and Cursor second. The Grok Bot bundle adds useful work beyond Cursor’s editor. I still value that combination, but the useful question is whether you will use the Bot enough to justify the eligible plan. The Cursor guide covers current plan prices.

What Access Does Grok Bot Have to Your Computer?

Grok Bot can access local commands and files only through its separately configured local-computer access; by default, local execution asks for approval each time. Installing its desktop app does not give it unrestricted control of your laptop or make it another Cursor Agent mode.

• Local-command execution is a separate permission: Ask every time is the default, with Always allow and Never allow alternatives where team policy permits.
• Grok Bot requires data storage and does not support Legacy Privacy Mode.

I would keep local execution disabled until a specific job needs it.

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.

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.

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

When Grok Bot prepares an email or Slack message through its draft workflow, the conversation shows an editable draft with Send and Discard buttons. Other tool and browser actions follow their configured approval rules.

Check the usage screen before a long job and after the first few runs. The account's plan determines whether additional work uses prepaid credits or legacy on-demand billing. Set an additional-spend limit and inspect actual consumption before scheduling overnight work.

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.

FAQ

Is Grok Bot part of the Cursor editor?

Grok Bot is a separate desktop and mobile app. It shares account and service connections with Cursor, while its Bots normally work on a persistent cloud computer.

Does Grok Bot run on my own computer?

Grok Bot agents normally run in the cloud. Local commands require a separate execution setting, whose default is Ask every time. Team policy can restrict the available choices.

Do all my Bots share one cloud computer?

Every Grok Bot agent 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?

Grok Bot shares weekly usage with Cursor and Grok on the current X Subscription. Legacy Cursor plans and account links follow separate allowance and billing rules.

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 Grok Bot agent can use its cloud terminal or delegate a coding task to Cursor Cloud Agents when access is configured. I prefer a dedicated coding agent for repository changes because the diff, tests, and review are easier to follow. Any proposed pull request still needs review.

Is there a free trial for Grok Bot?

Grok Bot has a free trial that Cursor's plans page describes 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 a small, clearly defined job before you let it run overnight.

Which model does Grok Bot use for its Bots?

Cursor selects Grok Bot’s models 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: our overall ranking, with Claude Code first and Cursor second.
• 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 October 16, 2026.