2026-08-27 · Guide
Cursor Pro+ and Grok Bot: What the $60 Plan Includes
The upgrade control from Cursor Pro to Cursor Pro+ sits in billing like a switch, and that is the mistake this page exists to catch.
You already pay twenty dollars for the editor. A coworker said Grok Bot is included in Cursor now, and on Pro it is. The slider looks like the flag you forgot to enable. It is not a flag. It is a different SKU at sixty dollars a month, checked on 23 September 2026 against cursor.com/pricing, and the only thing that SKU adds for Grok Bot is a higher weekly usage tier.
This page is one invoice line: grok bot cursor pro plus. It is not a ranking of every door (the cheapest way into Grok Bot). It is not why sign-in runs through a Cursor identity (why Grok Bot needs a Cursor account). Stay here if you are about to move from Pro at twenty to Pro+ at sixty, and you need to know what the sixty dollars attached to the bot and what it did not. Confirm the live invoice before you install.
Treat Pro+ as an eligibility stamp, not as a Grok Bot product of its own
Cursor Pro+ is a Cursor plan. Grok Bot is a separate product whose access check reads that plan. The Grok Bot FAQ and Cursor's plans page list Pro+ among the included plans, next to Cursor Pro, Cursor Ultra, and every member of a self-serve Cursor Teams plan, with an individual SuperGrok, SuperGrok Plus, SuperGrok Heavy or X Premium+ subscription as a link, plus a one-time trial. Eligibility first widened on 21 August 2026 (xAI announcement). Launch-week posts that still describe an Ultra-only door are describing a list that no longer exists.
Pro+ does not mint a private Bot SKU with extra knobs. You receive the same Grok Bot every other eligible plan receives: a named agent on a managed cloud computer, with a screen per bot. What a Grok bot is is that object. Paying Pro+ raises the weekly usage on a permission that Cursor Pro at twenty already grants. You do not have to open the editor. The account is the entitlement record. People still hunt for a picker, a cap, and a private machine inside Grok Bot. Those controls are not on this stamp.
If you already hold Cursor Pro, Cursor Ultra, a Cursor Teams seat, or a linked SuperGrok subscription, you already have a door. This page is for the person whose invoice says Pro and wonders what sixty adds, or still says Hobby.
Read the invoice line before you treat the sixty-dollar door as open
The installer does not know what you pay. Sign-in does. If the invoice still says Hobby, the bot will not activate, no matter how cleanly the binary landed.
Cursor Pro and Cursor Pro+ share a word, and now they share Grok Bot too. They split on weekly usage. Confirm the spelling on cursor.com/pricing the morning you pay, then confirm the same spelling on the invoice and inside the app. Do not infer eligibility from a Slack screenshot or from this page.
Privacy Mode (Legacy) blocks Grok Bot entirely. A correct Pro+ invoice will not save you if that mode is on.
| Invoice line you actually have | Grok Bot on that line | What to do next |
|---|---|---|
| Cursor Hobby | Not included | Spend the trial, or step to Pro |
| Cursor Pro at $20 | Included. Cheapest paid door, lowest weekly usage | The slider to Pro+ is a usage change, not a feature flag |
| Cursor Pro+ at $60 | Included. More weekly usage than Pro, below Ultra | Confirm the app shows this entitlement, then install |
| Cursor Ultra at $200 | Included. Highest weekly usage | You already have a door |
| A self-serve Cursor Teams seat | Included | Company door. Not this SKU |
A self-serve Cursor Teams seat is a team SKU, not an individual door. Do not open a dummy team to reach a bot Pro already includes. If your company already pays those seats, you are done.
Keep Cursor Pro at twenty in view, because it already opens the bot
Hobby does not include Grok Bot. Cursor Pro at twenty dollars a month includes Grok Bot. People who search grok bot cursor pro plus are often already on Pro, and they are trying to decide whether Pro's weekly usage is enough or whether sixty buys something the bot needs.
Sixty buys usage, not a different bot. Cursor's plans page puts Pro's weekly usage below Pro+, and Pro+ below Ultra, and prints no size for any of them. The 21 August widening did not add Pro; a later plans update did. If the bot will not start and you pay twenty, check the account screen and Privacy Mode (Legacy) before you blame the plan.
Pro sounds like the main paid plan. For the editor, it is, and for Grok Bot it is now the cheapest included Cursor rung. Treat Pro and Pro+ as one bot at two usage tiers, the way SuperGrok and SuperGrok Plus share a name and split on linked usage.
There is no documented Bot subset on Pro: the same product, less weekly usage. Shop the SKU in front of you. Cross-product order belongs on the cheapest way into Grok Bot.
Spell out what Pro+ includes for Bot: the right to run and a higher tier
For Grok Bot, Cursor Pro+ includes eligibility and a weekly usage tier above Pro. Those two lines are the whole include list.
After the access check passes, you get the product every eligible plan gets. One persistent cloud computer, assigned to your user account, not to a bot (computer and apps). Each bot gets a screen on that computer. Screens are work surfaces, not security boundaries. Subscriptions include a weekly usage allowance. Overflow is on-demand, billed from model and token cost. No published dollar figure for that allowance exists on the pages this site treats as fact, so this page will not invent one.
Hosted MCP sign-in tokens stay with Cursor's backend, not on the computer. That is true on Pro+ because it is true of the product, not because this SKU bought a special vault.
You get a client if your device is supported: macOS (Apple silicon and Intel), Windows (x64 and Arm64), iPhone on iOS 18 or later. There are Linux desktop and Android apps as of September 2026, and the iOS app also runs on iPad (iPadOS 18 or later). The agent computer is a managed Linux VM in the cloud, not a Linux desktop app. Paying sixty does not mint one.
Lead Scout will run on Pro+ the same way it runs on Ultra. Chief of Staff Briefing will too. They run on Pro as well. The SKU only changes how much weekly usage they share.
Name the four extras this invoice does not attach to Grok Bot
People flip the slider and then hunt in settings for the rest of the purchase. The rest is not there. Pro+ does not attach a spend cap, a model picker, a dedicated computer, or the old Pro price. A second bot is a second screen, not a second VM. "Do not use separate Bots as a security boundary" is the vendor line (approvals, security, and privacy).
Two product-wide absences belong in the same drawer. Individual accounts and self-serve Teams still have no audit view of Bot actions; Enterprise has audit logs and Action Recording. Claude Code, SKILL.md, and CLAUDE.md compatibility belong to Grok Build, never to Grok Bot. Grok Bot versus Grok Build is the fork. Do not buy Pro+ because you wanted Build's skill loader.
| Thing you might think sixty dollars attached | What Pro+ actually attached for Grok Bot |
|---|---|
| A Bot-specific spend cap | None. Weekly allowance, unpublished as a dollar figure, then on-demand overflow up to the account's monthly limit |
| A model picker | None, for members or admins |
| A computer per bot, or a computer that is yours alone among bots | One account computer. Screens are not security boundaries |
| Bot itself, which you thought Pro lacked | Pro already had it. A different SKU at $60 buys a higher weekly tier |
| An audit log of Bot actions | Not on this plan or any individual plan. Enterprise only |
| SKILL.md / CLAUDE.md inside Grok Bot | That is Grok Build. Wrong product |
How token burn works without a per-bot cap is the operations page for the ceiling the SKU never printed.
Leave Hobby and SuperGrok Lite off this page, they never become Pro+
Hobby is not a cheaper Pro+. SuperGrok Lite is not one either. Both are excluded rungs. They do not mature into this SKU at the next renewal.
An individual SuperGrok, SuperGrok Plus, SuperGrok Heavy or X Premium+ subscription can be linked from the Grok Bot plan screen. If you already live on xAI at one of those tiers, you do not need Pro+ to open the bot. If you do not, do not buy Plus as a substitute for this page. Twenty on Pro opens the same bot. Plus is the right cart when Plus is the house you wanted anyway.
If you hold both a Cursor subscription and a SuperGrok subscription, Grok Bot uses whichever has more usage. You do not stack two bot products, and the link is permanent. Buying Plus on top of Pro+ for safety is two invoices for one computer.
SuperGrok Heavy is eligible. Its price is not on x.ai/pricing as a figure this page will print. Leave Heavy out of a Pro+ decision. You cannot compare an unpublished number to sixty.
The metered sample, if you still have it, is the Grok Bot free trial. Use that page when the question is how to spend the meter. Use this page when the question is what you just bought if the door is Pro+.
Follow Arun as he treats the Pro-to-Pro+ slider as a toggle
Arun is a backend engineer at a twelve-person company. He pays Cursor Pro at twenty dollars himself. The company does not buy Cursor Teams. He does not pay SuperGrok. He works on a MacBook, and he has a Linux workstation at home that runs the Linux desktop app since September 2026.
On Monday a coworker posts in Slack: Grok Bot is in Cursor now, just enable it. Arun opens billing, sees a control that moves him from Pro to Pro+, and treats it like every other beta flag he has flipped. He flips it.
The next invoice is sixty dollars, not twenty. The bot opens, as it would have on Pro. He creates two bots on the first evening: one he plans to connect to GitHub, one he plans to connect to Gmail, because he wants review comments and inbox drafts in separate sandboxes. He looks for a per-bot spend cap in Pro+ settings before anything runs overnight. He looks for a model picker because the editor let him choose. Neither control exists; the nearest is the account's On-demand monthly limit.
| Move Arun considers | What he pays | What he gets for Grok Bot | When this move is honest |
|---|---|---|---|
| Stay on Pro at $20 | $20 | Grok Bot at Pro's weekly usage. The coworker was right | He has not yet run out of Pro's weekly usage on a job that repeats |
| Flip the slider now | $60 list, $40 more than the Pro seat he already pays | A higher weekly tier. Same bot product. No cap, no picker, no private VM | A repeating job already ran dry on Pro's weekly usage, and he watched the packet get used |
| Run Pro for a week, then decide | $20 this month | The real product at the lowest weekly tier, not a sample | He has not seen a packet yet, and he can name one reversible job |
The toggle story fails in three places. The control is priced, and it bought usage he had not measured. Two bots did not give him two computers: cookies, sessions, files, and CLI credentials are shared, and deleting the Gmail bot later will not remove the Gmail session. Pro+ did not add a cap or a picker because he paid more than twenty. Those extras are not on Ultra or Teams either.
He has not connected Gmail yet. He should not, until he has read shared computer security and Grok Bot and Gmail. Inbox Triage waits until he intends to keep the account. He has a repeating Tuesday job: a one-page brief of what shipped in three public libraries his team depends on. That job can run without GitHub login, mail, or a routine.
Draft the first standing job before the increment posts to the card
Do not flip the slider, and do not start the first run, until the first job is written down outside the product. Checkout is faster than drafting. The computer starts spending when it starts working. Arun writes the brief first.
He pastes this and does not expand it:
Name: Tuesday Library Brief
Job: One question, public sources, one page
You answer one question I name about a public library, changelog, or
docs site, using public pages only. Every material claim has a URL. If
a source will not open, write blocked and stop. Do not keep browsing
after the page is done.
Boundary: Never send email, never post, never purchase, never create
accounts, never sign into sites, never use cookies from other bots.
Never push, merge, comment on, or open a pull request.
Deliver: one page plus a source table. No appendix of extra links. No
routine. No second question unless I paste it.
That charter is the SKU test. If Pro cannot finish it, Pro+ will not magically finish it either. More weekly usage is not a smarter model, and there is no model picker on any paid door to try one after a mushy packet. Is Grok Bot worth it is the verdict page after a packet exists. Do not buy this SKU for a job you have not named.
Do not schedule the Tuesday job during the first week. A routine assigns a workflow to one bot, with a maximum of fifty per bot and twenty recent run records kept. Deleting the bot deletes the routines. Nothing is team-level. On a paid door you intend to keep, put the clock on after you have watched a run finish, not as part of flipping the slider.
Open the installer only after the account screen prints an eligible plan
Download is a separate page: how to download Grok Bot. This SKU page only owns the order. Confirm the entitlement, then get the binary. The installer will happily land on a Hobby disk. Sign-in is the gate.
Official desktop path: x.ai/bot. Official phone path: the iOS App Store search for Grok Bot, on an iPhone running iOS 18 or later. Do not follow a GitHub release or an unofficial Linux wrapper.
Supported clients are macOS, Windows and Linux on desktop, plus iPhone (iOS 18 or later) and Android (9 or later) companion apps; the iOS app also runs on iPad (iPadOS 18 or later). Supported platforms is the device grid. Arun's Linux workstation can install the Linux desktop app (.deb, .rpm or AppImage). iPhone can pause and resume. Editing and testing a routine still need the desktop app; the phone can now show run history and delete a routine. Do not debug a new Pro+ seat from a phone you cannot inspect.
If the account screen still says Hobby, stop. You are not eligible. Do not keep reinstalling. The login failed pattern is often this plan mismatch, not a corrupt download.
Price the move as a forty-dollar increment if you already pay twenty
If you pay Cursor nothing today, Pro costs twenty and already opens the bot; Pro+ costs sixty. If you already pay Pro at twenty, the increment on that seat is forty. Shop the increment when you are already on Pro. Neither number is a Bot usage budget. The forty buys a higher weekly tier, not a door.
Do not jump to Ultra at two hundred because launch-week posts called it the real plan. Ultra is eligible, with the highest weekly usage. It is not this SKU, and it is not a better bot. Buy Ultra for Cursor, if you were buying Ultra for Cursor. Do not open a Teams plan as a team of one to reach a bot Pro already includes. Teams wins when seats already exist.
Do not skip Pro to start properly on Pro+. Pro at twenty already runs the bot, so a week on it is the honest sample. On Hobby, the trial is the sample, and how to spend the meter is the Grok Bot free trial. If you already sit on Pro+, you already bought the tier.
Grok Bot cost is what happens after the door is open: frequency multiplies, browser work varies, a five-minute schedule is a different bill from a weekly brief. Pro+ does not change that arithmetic. It only gives the arithmetic more weekly room.
Refuse the private-computer story that people attach to any SKU above twenty
The most expensive story attached to this SKU is not the forty-dollar increment. It is the belief that paying more than Pro bought a machine of your own, among your own bots.
It did not. The computer is assigned to the user account, not to an individual bot. Every bot you create on the Pro+ seat shares cookies, signed-in sessions, files, and CLI credentials. Deleting a bot does not remove those. That is why Arun's two-bot plan was not isolation. A GitHub session and a Gmail session on the same computer are one incident waiting for the wrong tab.
Hosted MCP tokens stay with Cursor's backend. Browser logins still sit on the machine.
Least privilege bots is the discipline after the door opens: one job, one grant, a boundary the bot can fail. Pro+ does not enforce that. No eligible plan does. An approval controls the proposed action. It does not reverse work already completed. There is still no audit view on individual plans, so you keep the ledger.
If you need two computers, you need two eligible accounts. That is two invoices, at whatever the live Pro, Pro+ or Teams price is on the day you check. Named bots on one Pro+ seat are not a third isolation mode.
Prove the entitlement with a check that can fail on today's invoice
These checks can come back false. If they do, you are not on Pro+, or Pro+ is not doing what you thought, and you should not keep spending as if the door were open.
| Check | Pass | Fail |
|---|---|---|
| Invoice and account screen both say Cursor Pro+, not Pro, not Hobby | You are on this SKU | The change has not posted. Do not reinstall to force it |
| Grok Bot FAQ still lists Cursor Pro+ as eligible today | The stamp still exists | This page is stale. Shop the FAQ |
| cursor.com/pricing still shows Pro+ as a live SKU | You know what you are paying | Do not use sixty from memory |
| Privacy Mode (Legacy) is off | The stamp can be used | The SKU is correct and the bot is still blocked |
| A named bot can finish one public-source brief without a login | The computer works on this seat | Do not connect Gmail or GitHub to debug a bad brief |
| Settings shows the account's On-demand monthly limit and no per-bot cap | You are looking at the real product | If you found a per-bot cap, confirm it is Grok Bot, not another Cursor meter. Do not invent a dollar figure |
If the FAQ and this page disagree, the FAQ wins. If your account screen and the FAQ disagree, shop the entitlement on the screen. Dates on this page are 25 to 27 August 2026, with plan facts rechecked on 23 September 2026. Treat every third-party number, including the sixty in the title, as something you re-read on the vendor page the morning you pay.
Answer the slider-as-toggle objection without pretending the invoice is a flag
The strongest case against this page is simple: in the Cursor billing UI, the move from Pro to Pro+ is a slider. Sliders are toggles. Calling it a different SKU is pedantry. Flip it, receive Bot, keep thinking in editor terms, and stop reading invoices like contracts.
Grant the UI. The control looks like a switch. If flipping it also produced a spend cap, a model picker, and a private computer, the toggle story would be a complete description. That is not what the docs describe. Eligibility is a boolean, and Pro already sets it. The Bot feature sheet on the other side is the same for every eligible plan except weekly usage, and it excludes a per-bot cap and a picker. The computer is per account. The invoice is sixty, not twenty. A toggle that changes the price, the plan name, and the weekly tier, and nothing else on the Bot feature sheet, is a SKU.
The objection wins in one narrow case. Arun has no repeating job. Pro already runs the bot. Curiosity is a week on Pro, not Pro+. Stay on twenty. Run the library brief there. Stay there if the packet is mush.
The objection loses the moment a repeating job runs Pro's weekly usage dry. Then he is buying a tier that does not include a per-bot ceiling, a picker, or a second machine. Pretending the slider is a flag is how he connects Gmail on night one and looks for a cap on night two.
Claude Cowork and ChatGPT Work are different products. Confirm those vendors' current pages if the repeating job already lives there. Worth sits on the packet, on is Grok Bot worth it, after the door is understood.
Put the irreversible verb in the charter, because the Pro+ invoice will not print it
The shopping task ends when the account screen shows Pro+. Everything after that is operations.
Pro+ will not write the stop line. You write the verb the bot must never take, in the charter, before the first login that can survive a deleted bot. For Arun, that verb is send, pay, push, merge, and sign in. The Tuesday brief does not need those verbs. Standup Scribe does not need them either. Mail and GitHub wait.
Approval rules and reversibility is the control surface after you connect anything that can act. The safety checklist is the first read if you are about to put a session on the shared machine. Usage shape is Grok Bot cost. Isolation is shared computer security.
The sixty-dollar tier stays cheap when the irreversible verb stays human. That is not a line item on the Pro+ invoice.
Keep reading: the cheapest way into Grok Bot, the Grok Bot free trial, how to download Grok Bot.
Frequently Asked Questions
Does Cursor Pro at 20 dollars a month include Grok Bot?
Yes, as of the 23 September 2026 check. Every paid Cursor plan includes Grok Bot: Pro at twenty dollars, Pro+ at sixty, and Ultra at two hundred, which differ only in weekly usage. Cursor Pro is now the cheapest paid path. Cursor Hobby, the free plan, does not include it. An individual SuperGrok, SuperGrok Plus, SuperGrok Heavy or X Premium+ subscription can be linked instead, on the xAI line rather than this SKU. If the bot will not start and you pay twenty, check the account screen and Privacy Mode (Legacy). Confirm the live invoice and Cursor's plans page before you treat a coworker screenshot as eligibility.
What does Cursor Pro+ include for Grok Bot besides eligibility?
Eligibility and a weekly usage tier above Pro are the include list. After the access check passes, you get the same Grok Bot every eligible plan gets: one persistent cloud computer per account, a screen per bot, a weekly usage allowance with no published dollar figure, and on-demand overflow billed from model and token cost. You do not get a per-bot spend cap, a model picker, a dedicated computer, or an audit view of Bot actions. You also do not keep paying twenty. Confirm those absences against the FAQ and the teams and enterprises docs, because this answer is dated with the rest of the page.
If I already pay for Cursor Pro, is upgrading to Pro+ just flipping a toggle?
The billing control looks like a toggle. The invoice is a different SKU at sixty dollars a month, which is a forty dollar increment on a Pro seat you already pay. Flipping it keeps the same Grok Bot product you already have on Pro and raises the weekly usage tier. It does not switch on a cap, a picker, or a private machine, and it does not leave you on twenty. If you are only curious, stay on Pro; it already runs the bot. If a repeating job runs Pro's weekly usage dry, buy the SKU as a tier, not as a flag, and write the first charter before the increment posts.
Does Pro+ add a spend cap, a model picker, or a computer of my own?
No. There is no Grok Bot-specific spend cap yet on any documented plan; the account-level On-demand monthly limit is the only ceiling. There is no model picker for members or admins. All bots on the account share one cloud computer, and screens are not security boundaries. Deleting a bot does not remove shared files or sessions. Paying sixty instead of twenty buys a higher weekly tier, not a second VM. If you need two computers, you need two eligible accounts, which is two invoices. Confirm live vendor pages before you quote those invoices to anyone else.