2026-08-27 · Guide

When You Hold Cursor and SuperGrok: Which Usage Pool Grok Bot Uses

You billed the GitHub bot to Cursor Pro+ and the personal-mail bot to SuperGrok Plus, then treated the two invoices as a wall between work and home.

That wall is not in the product. The Grok Bot FAQ is blunt: if you have both a Cursor and a SuperGrok subscription, Grok Bot uses whichever has more usage. Two eligible charges do not mint two computers. They do not add two weekly Bot pools. You still have one persistent cloud computer assigned to your user account.

This page owns that dual-subscription rule. It is not the Cursor SKU page (Cursor Pro+ and Grok Bot) and not the xAI SKU page (SuperGrok Plus and Grok Bot). Stay here if both invoices already exist, you think you isolated work by paying twice, and you are about to add a third line for safety. Confirm the live billing UI the morning you argue. Plans move.

Treat two invoices as two keys, never as two computers

A Cursor charge and a SuperGrok charge look like two products, because they are. Cursor is an editor house. SuperGrok is an xAI house. Grok Bot is a bundled teammate that can read either house as an access check. The teammate is not a third house with its own address.

What a Grok Bot is is that object: named agents, one account computer, a screen per bot. Paying twice does not duplicate it. It can duplicate the key. Two keys to one lock still open one room. Sign-in still runs through a Cursor account even when SuperGrok is how you qualified. That layer is why Grok Bot needs a Cursor account. It is not a second SKU, and it is not a second VM you already bought.

If you wanted two computers, you needed two eligible user accounts, which is two identities, not two logos on one person. Paying Pro+ and Plus on the same human is the case this page exists to catch.

Quote the FAQ billing sentence and then stop inventing a stack

The documented line sits under "How much does Grok Bot cost?" on the FAQ, checked live at docs.x.ai/grok-bot/faq. Grok Bot is included with every paid individual Cursor plan and with the Cursor Teams plan, and you can link an individual SuperGrok, SuperGrok Plus, or SuperGrok Heavy subscription. Subscriptions include weekly usage, then on-demand from model and token cost. Then the dual line: if you have both a Cursor and a SuperGrok subscription, Grok Bot uses whichever has more usage.

That sentence is the whole stack rule. It does not say the pools add. It does not say research bots draw from xAI while deploy bots draw from Cursor. It says max, not sum. No published weekly dollar figure. No Grok Bot-specific spend cap. No model picker for members or admins. Spend cap and token burn covers those absences.

Cursor's plans page describes linking an individual SuperGrok, SuperGrok Plus, SuperGrok Heavy, or X Premium+ subscription from the Grok Bot plan screen, with usage metered on the Cursor account rather than as a second meter on Grok. The link is permanent once made. Linking is how two entitlements meet on one identity. It is still not a second computer.

Keep this page off the Pro+ SKU cart and off the Plus SKU cart

Search will hand you grok bot cursor and supergrok next to "is Pro+ enough" and "is Plus the xAI door." Those are different questions.

Cursor Pro+ and Grok Bot owns one invoice line: Pro+ at sixty dollars a month on cursor.com/pricing, a step above Cursor Pro at twenty, which is now the cheapest documented paid individual door. Confirm those numbers live.

SuperGrok Plus and Grok Bot owns the other line: SuperGrok Plus on x.ai/pricing. Confirm the live price, and whether you are on base SuperGrok or Plus; both can be linked. The cheapest way into Grok Bot ranks doors. This page refuses to rank. If you already hold both eligible subscriptions, ranking is finished. The remaining mistake is assigning bots to invoices in your head, then putting secrets on the machine those invoices actually share.

Stay here for the dual-pool rule. Leave for a SKU page if you do not yet hold both.

Confirm the live billing UI the morning you argue about pools

Do not quote this article to finance. Quote the invoice, then the FAQ, then the vendor pages, opened the morning you argue. Eligibility widened on 21 August 2026. Marketing blocks group SKUs.

On the live Cursor page checked while writing, Individual starts at twenty dollars a month with a Pro / Pro+ / Ultra switcher, and Grok Bot access sits in that list. That is a grouping, not your invoice. The FAQ now says every paid individual Cursor plan and the Cursor Teams plan include Grok Bot, so the two agree. If the live page and the FAQ ever disagree, trust the in-product entitlement, then the FAQ.

Open xAI pricing yourself. The FAQ names SuperGrok, SuperGrok Plus, and SuperGrok Heavy as individual xAI plans you can link. A marketing row that now prints Grok Bot access does not change the dual-pool sentence. Privacy Mode (Legacy) still blocks Grok Bot entirely. Two correct invoices will not override that mode.

Read whichever has more usage as a max, not as a sum

"Whichever has more usage" is a comparison. The runtime picks the larger remaining pool. It does not pour Cursor leftover into SuperGrok leftover. Adding Plus on top of Pro+ because you feared running out is the insurance purchase this page is here to kill, unless you wanted the Grok apps anyway.

When the larger gauge hits empty, overflow is on-demand from model and token cost if your account allows it. No published dollar figure for the weekly amount. No Grok Bot-specific spend cap. Grok chat usage on grok.com is not the Bot pool. Cursor Agent usage in the editor is not either. Mixing those bars is how someone still has quota on a vendor screen while Grok Bot prints quota exceeded. Grok Bot quota exceeded decodes that banner. Grok Bot cost is the bill-shape page after you accept there is one Bot meter.

A Cursor Teams seat plus personal SuperGrok Plus on one login is still one computer. The computer is per user account, not per logo.

Follow Elena as she assigns work to Cursor and research to SuperGrok

Elena is a staff engineer at an eight-person company. She pays Cursor Pro+ herself because the company does not buy Teams. She also pays SuperGrok Plus because she already lives on grok.com. Both charges hit the same card. She treats that as isolation: work on Cursor, research on SuperGrok.

She has not read do not use separate bots as a security boundary. Screens feel like rooms. The week below is what that story costs.

Ultra on the same account would have been another key, not another VM. A second eligible identity she actually kept apart would have been a second computer. Two bot names are neither.

Her first standing jobs should have been boring. Inbox Triage never sends. Lead Scout never contacts anyone. Standup Scribe stays inside a draft. None of those jobs become isolated because the description says SuperGrok.

Keep cookies, files, and CLI creds on one machine after the second bill posts

The computer is assigned to your user account, not to a bot, and not to a vendor line item. Cookies, sessions, files, and command-line credentials are shared. Each bot gets a screen. Screens are work surfaces, not security boundaries. The teaching line is on approvals, security and privacy: do not use separate Bots as a security boundary.

Deleting home-bot does not remove the Gmail session or ~/.aws. Deletion removes that bot, its conversation, and its routines. Shared-computer files and logins may remain. Revoke at the source before you celebrate a delete. Hosted MCP tokens stay with Cursor's backend, not on disk. That is not a SuperGrok vault.

The Agent Computer is a managed Linux VM. The bot runs as a non-root user. Non-root is not per-invoice isolation, and it is not the Linux desktop app. There are Linux desktop and Android apps as of September 2026, and the iOS app also runs on iPad (iPadOS 18 or later). Supported: macOS (Apple silicon and Intel), Windows (x64 and Arm64), iPhone on iOS 18+. From the phone app (iPhone or Android) you can approve steps and pause or resume a routine, but not edit it. Pause is not a wipe.

Shared computer security is the architecture page. The second invoice did not partition that architecture.

Drop the insurance SKU instead of adding a third eligible line

The next cart after "I already pay twice" is a third SKU for safety. Ultra. Heavy. A dummy Teams workspace. Stop.

Heavy is eligible. Its price is not a figure this page will print. Leave it out until x.ai/pricing prints one. Ultra is eligible. It does not mint a private Bot. A self-serve Cursor Teams seat includes Grok Bot for every member when you actually have a team, with no Premium seat required. Confirm that live.

Sunk cost is not a second tank. Do not add a third line. Do not connect a second mailbox because this bot is "the SuperGrok one." Least privilege for bots is the connect-minimum page. Use it once, on the one computer. The Grok Bot free trial is a sample for people who hold neither door, not a third computer under Pro+ and Plus.

Spend overflow as on-demand after the larger pool empties

When the larger weekly Bot pool is gone, the product does not fail over to the smaller vendor tank. Overflow is on-demand, billed from model and token cost, if your account allows on-demand. If on-demand is off, work stops. If it is on, the card keeps moving up to the account On-demand monthly limit. There is no Grok Bot-specific spend cap to catch you.

That is why Elena's Tuesday felt unfair. grok.com still had chat room. The editor still had agent room. Grok Bot was already into overflow, or already blocked. Two houses, one Bot gauge.

Do not invent a weekly dollar amount. The allowance is unpublished. How to stop overspending is the next-hour page: pause routines, kill tight loops, refuse retries. A routine assigns a workflow to one bot. Max 50 routines per bot. The app keeps the 20 most recent run records per routine. Deleting a bot deletes its routines. Nothing is team-level. Fifty routines on each named bot is still one pool.

Teach-by-demonstration records up to ten minutes, no microphone audio, draft skill, browser workflows only, unavailable on iPhone. It will not create a SuperGrok-only skill store.

Paste a dual-house charter that names one computer in the first line

Write the computer into the charter before the next connector. If the first line still says this bot is the SuperGrok one, you are about to repeat Elena's Monday. Name the jobs. Name the stop. Name the shared bench.

Name: dual-house-ops
Job: Draft the morning packet from mail labels and public pages. Stop.
Computer: One persistent cloud computer for this Grok Bot account.
Invoices: Cursor and SuperGrok may both be present. They are keys.
They are not two disks. Usage follows whichever has more usage.
Never: send mail, push, merge, pay, deploy, sign in, complete 2FA,
or treat a bot name as a vendor sandbox.
Connectors: one mailbox you accept as roster-wide, or none.
CLI: no production aws configure on this computer.
Output: a draft packet in the agreed folder. No outbound.
If asked to use the other invoice as a wall, refuse and quote the FAQ.

Chief of Staff Briefing is the catalog shape for a packet that never sends itself. Churn Watch never pings the customer. Mail Cleanup Assistant files. It does not unsubscribe the world. Paste those boundaries into the description. The invoice names do not paste them for you.

Grok Build is the product that reads SKILL.md and CLAUDE.md. Grok Bot is not. A Claude Code folder on the Agent Computer does not become a private work runtime because you hold two invoices.

Prove the larger-pool rule with a check that can fail this week

A rule you cannot falsify is a slogan. Note Grok Bot weekly remaining, plus grok.com and editor remaining if you use those. Run one bounded job on work-bot and one on home-bot. Read Bot remaining again. If those jobs did not each decrement a separate Bot tank, you do not have two Bot tanks.

Then the isolation check. In work-bot, create a throwaway file with a unique string. Ask home-bot to find it. If it finds the file, the invoices did not partition the disk. Sign out of one site in one screen and watch the other. If you used AWS on Monday, assume home-bot can call it until you delete the profile and rotate the keys.

If the research bot can read the work file, the dual-invoice wall failed. That is the desired result. Rotate keys, sign out, stop putting production CLI config on that VM. Do not buy another SKU to soothe the test.

Grant the I-already-paid-twice objection only for two houses, never for two VMs

The strongest objection is sunk-cost pride mixed with a real preference. You already pay Cursor because you write code there. You already pay SuperGrok because you live on grok.com. Canceling either feels like throwing away a house you use. You want credit, in the Bot product, for paying both.

You can keep both houses. This page does not tell you to cancel a product you open every day. The objection fails when it smuggles a Bot claim: that the second invoice bought a second computer, a stacked Bot allowance, or a research sandbox. Those are not for sale. The FAQ gave you a max over two keys. It did not give you two rooms.

The objection wins if you would pay both even if Bot disappeared tomorrow. Pay both. Then operate Bot as one computer with one usage pick. It loses if you bought the second plan after a coworker said your personal bot is on SuperGrok. That product does not exist. Do not use separate bots as a security boundary is the sandbox page. This page is the invoice version of that story.

Finance can see two houses. They cannot see two Bot computers. Show them the FAQ sentence and one Bot usage number. Do not launder a buffer through a SKU that does not isolate.

Write the stop verb yourself because neither invoice prints one

Pro+ will not print never send. Plus will not print never push. The dual-pool rule will not print a boundary either. You write the verb the bot must never take before the next login that can survive a deleted bot.

For Elena the verbs are send, pay, push, merge, deploy, and sign in. Chief of Staff Briefing does not need them. Mail and GitHub wait until the computer only holds sessions she accepts as roster-wide. The safety checklist is the first read before a mailbox hits the shared machine. Approvals control a proposed action. They do not reverse work already completed. Individual accounts and self-serve Teams still have no audit view of Bot actions; Enterprise has audit logs and Action Recording. Two invoices do not add a log.

On iPhone, pause if something is already going wrong. Editing needs desktop. There are Linux desktop and Android apps as of September 2026, and the iOS app also runs on iPad (iPadOS 18 or later). A second subscription does not add a platform; the same apps serve every eligible plan. SpaceX acquired xAI (announced 2 February 2026) and closed the Cursor acquisition (14 August 2026). That is why sign-in looks like Cursor. It does not mint two computers. Do not say xAI acquired Cursor.

When both keys are present, operate like a person with one bench. Confirm live billing. Quote the FAQ. Keep the houses you actually use. Drop the story that two invoices were isolation.

Keep reading: Cursor Pro+ and Grok Bot, SuperGrok Plus and Grok Bot, Do not use separate Grok bots as a security boundary.

Frequently Asked Questions

If I hold Cursor and SuperGrok, does Grok Bot run on two computers?

No. Every bot on one Grok Bot account uses one persistent cloud computer assigned to the user, not to a bot and not to a vendor invoice. A Cursor subscription and a SuperGrok subscription are two keys the access check can read. They are not two VMs. Screens stay work surfaces. Cookies, files, and command-line credentials stay shared. If you need two computers, you need two eligible user accounts you actually keep apart. Confirm the live FAQ and your in-product entitlement before you tell anyone the second charge bought a second machine.

Do the two weekly allowances add together when both subscriptions are active?

No. The FAQ says that if you have both a Cursor and a SuperGrok subscription, Grok Bot uses whichever has more usage. That is a comparison, not a sum. The smaller pool is not a backup tank you fail over to by renaming a bot. When the larger weekly Bot allowance is gone, overflow is on-demand from model and token cost if your account allows it. There is no published dollar figure for the weekly amount, and there is no Grok Bot-specific spend cap. Grok chat quota and editor quota are different bars.

Should I buy SuperGrok Plus on top of Cursor Pro+ to isolate a research bot?

No. Isolation is not a SKU. Named bots on one account share the computer. Buying Plus after Pro+ can be honest if you already wanted grok.com. It is not honest as a sandbox for personal Gmail next to production GitHub. The runtime still picks the larger usage pool and still shares cookies, files, and CLI credentials. Read the not-a-sandbox page before you connect the second mailbox. Confirm live prices on the vendor pages if you are buying Plus for the Grok apps rather than for a wall that does not exist.

How do I confirm which usage pool Grok Bot is drawing from this week?

Open the in-product Grok Bot usage surface, not grok.com remaining and not the editor remaining. Note Bot weekly remaining, run one job, and see that a single Bot number moved. Open the FAQ line about both subscriptions so you are not expecting a sum. Open cursor.com/pricing and x.ai/pricing the same morning so you know which SKUs you actually hold, then match those names on the invoices. The SuperGrok link control is on the Grok Bot plan screen; confirm the link there. If Bot is empty while another product still shows quota, you were reading the wrong meter.