Grok Bot Works Next to Cursor

Grok Bot earns a slot when you can hand a bounded coding job to a Bot on a shared cloud Linux computer. You leave Cursor on Tab, Agent, and your local files, then come back to a result you can review. The decision this page settles is which jobs leave the editor and which stay with a local agent such as Claude Code or Codex.

What the Shared Computer Does

xAI describes Grok Bot as AI teammates that finish work on a persistent cloud computer. The computer is assigned per user and shared between every Bot on that account. Bots share its files, browser sessions, and logins, so one Bot can continue work another Bot already saved.

That machine has a browser, a terminal, and a shared workspace at /workspace. Each Bot gets its own screen on the same computer. Several Bots can run in parallel, and one Bot can run only one computer-use task on its screen at a time. Those screens are separate work surfaces, and they still share one security boundary.

• The computer stays on when you close the Grok Bot app or your laptop.
• Browser cookies and signed-in sessions persist across Bots on your account.
• Treat a login or file placed on the computer as available to every Bot you create.

I would keep durable project files in /workspace and treat temporary directories and uncommitted package installs as replaceable. xAI's computer docs say a recover or reset can discard recent unsaved work.

How Grok Bot Sits Next to Cursor

Grok Bot sits beside the Cursor editor. Tab and Agent stay in Cursor for local files, diffs, and short edits. You give the Bot a job in the Grok Bot app after signing in with the same Cursor account.

Cursor's Grok Bot plans page says access is included on every paid individual Cursor plan and on self-serve Teams. Sign in to Grok Bot with that same account. You can also grant usage by linking an individual SuperGrok, SuperGrok Plus, SuperGrok Heavy, or X Premium+ subscription. Linking grants usage on that xAI subscription and leaves the Cursor plan untouched.

Confirm the plan on the signed-in account you will use. xAI's 26 August 2026 announcement lists SuperGrok plus Cursor Pro and Teams. The same vendor's get-started and FAQ pages still start the eligibility list at SuperGrok Plus and Cursor Pro+. SuperGrok Lite is excluded on Cursor's plans page. Enterprise access is managed with your account team.

Surface	Stays in Cursor	Goes to Grok Bot
Files	Local project checkout on disk	Cloud /workspace on the VM
Edits	Tab, Agent, diffs	Bot task on the VM
Browser	Your laptop browser	Browser on the VM
Usage	Editor model pools	Weekly Bot allowance

xAI's August announcement says Grok Bot comes with its own usage, separate from Grok and Cursor plan usage. Cursor meters that Bot usage on the Cursor account, with a weekly included bucket and optional on-demand spend when the bucket runs out. Watch the plan screen during the first week. xAI still withholds the published size of that allowance.

Which Jobs Leave the Editor

Hand a job to Grok Bot when the work can finish on that cloud computer and you can review a deliverable later. Keep the job in Cursor Agent when you need the visual diff against the files already open on disk. Reach for Claude Code or Codex when the Bot would need your local browser, a private address, or a checkout that never leaves the laptop.

Job Type	Better Surface	Why It Fits
Bounded background task	Grok Bot	Runs after you close the laptop
Multi-file edit in view	Cursor Agent	Diff stays on local files
Localhost or private URL	Claude Code or Codex	Cloud browser cannot see it
Typed next-edit while you write	Cursor Tab	No handoff, no weekly Bot spend

My take: Grok Bot is one extra surface on a paid Cursor plan. I still keep a terminal agent next to it because of the weekly cap and the missing local browser. The split of tasks is still settling, and that pairing is the current answer on our AI coding tools ranking.

Start a First Bot Job

Official setup lives on xAI's get-started page. Install the Grok Bot desktop app for macOS or Windows, sign in with the Cursor account you already pay for, create one Bot with a short name and one primary job, then send a first task that names the outcome, the sources, the constraints, and the review point.

Grok Bot requires cloud data storage, so accounts on Legacy Privacy Mode have to move to a supported Cursor data setting before the product can start. Linux desktop stays unavailable during the initial launch window. iOS works at launch, while Android and iPad stay unsupported.

Investigate the failing auth test in this repo snapshot.
Name the file and assertion that fail.
Propose the smallest patch and do not change production config.
Stop for review before you edit any file outside the test and the one module it calls.

When the Bot hits a password, passkey, two-factor prompt, CAPTCHA, or payment check, take over the computer from the conversation, complete only that step, and hand control back. Avoid pasting secrets into chat and prefer a connector from Settings, then Plugins, when xAI lists one for the service.

Keep Usage and Approvals Visible

Paid access includes weekly usage that resets on a weekly cadence. Cursor's plans page says extra Bot usage can continue on shared on-demand spend if on-demand is enabled. A long first run can consume most of a trial credit in one go, and used trial credit stays spent.

Put sending, publishing, deleting, purchasing, and production changes behind approval. xAI's approval docs say those consequential actions can stop for a human. Write the same boundary into the Bot description so a later routine cannot widen the job quietly.

• Check the plan screen before a long agent job.
• Keep one Bot per role instead of one catch-all teammate.
• Do not use a second Bot as isolation, because every Bot shares the same computer.

The Smallest Handoff That Works

Adopt one Bot and one recurring job that can finish on the cloud computer. Leave Tab, Agent, and the checkout in Cursor. Skip a roster of Bots, routines, and extra connectors until that first job returns a reviewable result without blowing the weekly bucket.

Keep Claude Code or Codex for local browser control and anything that must touch a machine you own. Grok Bot changes which jobs you still need that local agent for, and the editor stays the place for Tab, Agent, and the checkout.

FAQ

Do I get Grok Bot on Cursor Pro?

Cursor's Grok Bot plans page includes every paid individual Cursor plan, including Pro, plus self-serve Teams. xAI's get-started and FAQ pages still start the eligibility list at SuperGrok Plus and Cursor Pro+. Open the Grok Bot plan screen on your signed-in account before you treat access as settled.

Does Grok Bot stop when I close the laptop?

Bot work keeps running on the cloud computer when you close the laptop. Closing the Grok Bot app, your laptop, or the iPhone app leaves a background turn or a routine in place.

Can Grok Bot use the browser on my computer?

The Bot browser lives on the cloud computer. Chrome or Safari on your laptop is a different browser. A service that only listens on localhost stays out of reach unless you enable local-computer commands and approve them. Keep Claude Code or Codex for that local browser and computer-use work.

Do my Bots share one computer?

Every Bot on your account uses one persistent cloud computer assigned to the user. A single Bot does not get its own machine. Files, browser sessions, and command-line credentials on that machine are visible to the whole roster. Do not treat a second Bot as a security boundary.

Should I replace Claude Code or Codex?

Keep one local terminal agent for checkout and localhost work. Grok Bot covers bounded jobs that can finish on the shared cloud computer. Claude Code or Codex still covers work that must touch your checkout, your local browser, or a private address the cloud VM cannot see.

Where do I talk to a Bot?

Use the Grok Bot desktop app on macOS or Windows, or the iOS companion app. Sign in with the same Cursor account you already pay for. Linux desktop, Android, and iPad stay unsupported at initial launch.

Where to Go Next

• Cursor guide for the editor, models, and plan names this handoff sits on.
• Best AI coding tools for how Grok Bot moved Cursor to the top of the ranking.
• Cursor Origin hosted codebases when the job needs a Cursor-hosted remote.
• Cursor Automations for scheduled cloud agents that stay inside Cursor.

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