Guide

Grok Bot and Cursor: how they work together

Last checked

Grok Bot is closely tied to Cursor: it’s included with every paid individual Cursor plan and Cursor Teams, you sign in with your Cursor account, and the computers your Bots use run in Cursor’s cloud. It’s a separate app from the Cursor code editor, though. Your Bots can start Cursor Cloud Agents for coding work, and you can open those runs in Cursor.

How Grok Bot and Cursor fit together

According to the official docs:

  • Same account. You choose Sign in (or Sign In with Cursor in Settings), and Grok Bot uses your Cursor account, including your organization’s SSO.
  • Same cloud. xAI’s FAQ says “the computers Bots work on run in Cursor’s cloud.” That’s why Grok Bot has its own row on status.cursor.com.
  • Same plans. Grok Bot is included with Cursor Pro, Pro+ and Ultra, and with self-serve Cursor Teams. On The X Subscription, which bundles Grok, Cursor and X, it’s included on Premium, Super and Ultra.
  • Same privacy settings. Grok Bot follows your Cursor account’s data settings. It needs cloud storage, so Cursor’s Legacy Privacy Mode isn’t supported.
  • Separate app. Grok Bot has its own desktop app (macOS, Windows, Linux) and mobile apps. It isn’t a panel inside the Cursor editor.

Get Grok Bot with your Cursor plan

  1. Make sure you’re on a paid Cursor plan or a Cursor Teams seat. (On a free Cursor account, you can use the Grok Bot trial or link SuperGrok.)
  2. Download Grok Bot from x.ai/bot.
  3. Choose Sign in and use the same Cursor account.
  4. If your organization uses SSO, finish the normal organization sign-in. Don’t switch to a personal account.

On legacy Cursor plans, usage scales with the plan: Pro gets weekly usage, Pro+ more and Ultra the most. Before you switch to The X Subscription, check Grok Bot usage on your Cursor dashboard. Afterward, it’s at grok.com/dashboard. Our pricing guide has the details.

What Grok Bot adds for coding work

The Grok Bot changelog lists several ways Bots work with Cursor and code:

  • Start Cursor Cloud Agents. Bots can launch Cloud Agents for coding tasks. A Cloud Agent’s open button lets you choose Open in Web or Open in Cursor (September 1, 2026).
  • Run a Project. Ask a Bot for a Project and it starts a Cloud Agent that plans the work and runs its own agents (September 18, 2026).
  • Stop means stop. Telling a Bot to stop also stops the Bots it handed work to and the Cloud Agents it started (September 17, 2026).
  • Connect your repos. When a Bot needs a repository, a card lets you connect GitHub, GitLab, Bitbucket or Azure DevOps (September 11, 2026).
  • Work in GitHub. Bots can handle releases, tags, labels, sub-issues, discussions and branches, and submit a pull request review (September 17 and October 22, 2026).
  • Use a terminal. Every Bot’s cloud computer has a terminal and files, so it can run command-line tools.

A simple coding setup that works

  1. Make one coding Bot with a clear job: “You fix bugs in repo X. Reproduce first, open a pull request, never push to main, and never merge without my OK.”
  2. Connect the one repo it needs, not your whole account, if you can.
  3. Ask for a reproduction and a plan first. Let it start a Cloud Agent for the actual change.
  4. Review in Cursor. Open the Cloud Agent run in Cursor, or review the pull request on GitHub.
  5. Add a review Bot later so a second Bot checks each pull request before you do.

Limits to know

  • One computer for all your Bots. Repo credentials and logins on it are shared by every Bot on your account. Don’t use separate Bots as a security boundary.
  • Your laptop is separate. A Bot runs commands on your own computer only if you allow it under Execution on this computer (Ask every time by default).
  • Third-party models in Cursor aren’t part of the included usage on The X Subscription and are billed separately.
  • Cursor Agent: a local-only builder that runs the cursor-agent CLI on your laptop.
  • PR Reviewer: starts with what can break and what’s untested.
  • Code Team Spawn: stays idle until you need a coding team.
  • Terminal Boss: runs terminal coding agents (Grok Build, Claude Code, Codex, Cursor CLI and more).
  • Security Audit Bot: a private security report on code you own.

See all coding Grok Bot templates and how to install them safely.

Get the free setup guide

Set your coding Bots up with safe defaults from day one. Our free 18-page setup guide shows you how. Get the free guide

FAQ

Is Grok Bot part of Cursor?

Grok Bot uses your Cursor account, runs in Cursor’s cloud and is included with paid Cursor plans. It’s its own app, not a feature inside the Cursor editor.

Does Cursor Pro include Grok Bot?

Yes. Every paid individual Cursor plan (Pro, Pro+ and Ultra) and self-serve Cursor Teams include Grok Bot access.

Does Grok Bot use my Cursor usage?

On The X Subscription, Grok Bot, Grok and Cursor share one weekly pool. On legacy Cursor plans, Grok Bot has its own weekly usage limit on your Cursor account, with optional on-demand usage after that.

Can a Bot open its work in Cursor?

Yes. When a Bot starts a Cloud Agent, you can open that run in the web or in Cursor.

Where do I check if Grok Bot is down?

On status.cursor.com, under the Grok Bot row. See Is Grok Bot down?

Swarm School is an independent site. We’re not affiliated with xAI or Cursor.

Sources

Swarm School is independent and not affiliated with Grok Bot’s makers. Features change; check the official docs for current details.

Get the free 18-page setup guide.

The 9 setups most Grok Bot users skip, with a copy-paste prompt for each. Free PDF.

Send me the free PDF