2026-08-28 · Guide

What Survives If You Drop Grok Bot

Finance stopped paying Cursor Pro+ on Tuesday afternoon, and Linear still opened as the ops user on the Grok Bot computer Wednesday morning. Cancelling the invoice felt like leaving the product. Named bots vanished from the sidebar in the same sitting. Neither action signed a vendor out. Neither action emptied /workspace. Neither action pulled a hosted MCP grant out of Cursor's backend.

This page is what survives if you drop grok bot: the eligibility stamp, not a named profile. Delete a Grok Bot safely is per-bot teardown. Retire a Grok Bot is per-bot retirement for a scratch card. Stay here when the company is cancelling access. Pellmere is an invented eleven-person shop, not a real customer. Marek in ops watched finance cancel Cursor Pro+ at sixty dollars a month. Vendor consoles stayed signed in until someone signed them out.

All bots on an account share one persistent cloud computer assigned to your user account, not to a bot. Screens are not security boundaries. Deleting a Bot does not remove shared-computer files or browser sessions. Hosted MCP sign-in tokens stay with Cursor's backend. Enterprise organization admins can Terminate a member's computer, and it still keeps the durable disk.

Treat a Pro+ cancel as leaving the product, never as a named-bot wipe

Drop means the eligibility stamp goes away: Cursor Pro at twenty dollars a month, Cursor Pro+ at sixty, Cursor Ultra at two hundred, a self-serve Cursor Teams seat, a linked individual SuperGrok, SuperGrok Plus or SuperGrok Heavy, or the one-time trial. Rechecked 23 September 2026 against cursor.com/pricing, Cursor's plans page, and the Grok Bot FAQ. Cursor Hobby, the free plan, does not include Grok Bot. Landing on Hobby is a product exit even if the editor keeps working.

A named-bot delete takes one profile, one conversation, and that bot's routines off the sidebar. It does not cancel Pro+, wipe the managed Linux VM, or tell Linear you left.

If the bot still needs to exist next month, you are not dropping the product. If finance is cutting the sixty-dollar line, you are. What Is a Grok Bot? is a durable profile on an account-level computer, not a VM you vacuum by cancelling.

Sign every vendor console out while the eligibility stamp still exists

The control plane for the leftover cookie jar is Grok Bot itself. Open Agent Computer on a desktop while Pro+ (or whichever stamp you still hold) is live. Open each vendor URL the roster used. Sign out until you see a login prompt, not the ops portal.

Then revoke at the vendor. Session cookies can outlive a polite sign-out. Confirm the labels on that vendor's current security, devices, or connected-apps page. This article will not invent those menu names. If someone reused a personal password on a shared console, rotate it.

Do this for every console on the inventory. A project tracker, a CRM, a billing portal, and a docs subdomain are four sessions more often than they are one. Static egress IPs explain why some services flag datacenter addresses. They do not sign the GUI out when the invoice dies.

If you cancel first and only then remember Linear, you may no longer open Agent Computer. Cursor Hobby, the free plan, does not include Grok Bot. Restore an eligible stamp long enough to reach the shared browser, or revoke from the vendor's security page on a laptop you still control. Laptop revoke ends the grant at the source. It does not clear the cookie on a computer you can no longer drive. Sign out while the stamp exists.

Revoke hosted MCP in Cursor settings because those tokens never sat on the computer

Hosted MCP sign-in tokens stay with Cursor's backend. The computer never stores those tokens. The teams and enterprises page, checked 25 August 2026, is the source. Quote it in the ticket. Re-read the live page before you file. The product ships weekly.

Dropping Grok Bot does not pull those grants. The Cursor account remains if the company keeps Hobby or any other Cursor SKU. MCP authentication is shared across Cursor and Grok Bot. Cancelling Pro+ does not empty that drawer.

Revoke the connection in Cursor settings while you still know which servers you connected. A browser sign-out does not pull a backend grant. A settings revoke does not clear a Linear cookie. Mix the two drawers and you will "sign out" and leave the grant alive, or revoke MCP and leave the portal loaded.

If Pellmere never used hosted MCP, write that down as a negative. An audit view of Bot actions does not exist outside Enterprise, so you will not get a product log of which named worker connected which server at 02:14. Where Grok Bot MCP Sign-In Tokens Actually Live is the location page. The exit move is revoke in Cursor, because the token outlives the roster and the Pro+ line.

Walk Marek from Tuesday's Pro+ cancel into Wednesday's still-open Linear tab

Pellmere is an invented eleven-person shop. Marek runs ops. After eligibility widened on 21 August 2026, the company bought one Cursor Pro+ seat at sixty dollars a month, the cheapest paid path at the time, checked against cursor.com/pricing on 25 August 2026. They pasted Inbox Triage, Lead Scout, and Churn Watch onto the same account. Marek signed Linear and HubSpot into the shared browser, connected a hosted MCP server in Cursor, and dumped fourteen CSV exports into /workspace/pellmere-ops/. Fourteen is an arbitrary count for this walkthrough, not a product limit.

Tuesday 25 August 2026, 17:40. Finance tells Marek they will drop grok bot. Cursor Hobby, the free plan, still gives them the editor. Marek deletes the three named bots in twenty minutes and replies that Grok Bot is gone.

Wednesday 26 August 2026, 09:12. The Pro+ period has not ended. Marek opens a scratch name to look around. Linear opens as the ops user. HubSpot still shows the portal. Fourteen files are still listed. Cursor settings still show the hosted MCP connection. Named-bot delete removed three profiles, three conversations, and every routine those bots owned, including the twenty stored run records per routine. It did not sign Linear out.

The exit he owed, on desktop, while Pro+ still stamped the account: inventory while a bot still exists (individual accounts have no audit view of Bot actions); pause every routine (max 50 per Bot, nothing is team-level) and copy wording off this computer; sign out until login prompts appear; revoke at each vendor's current security page; revoke hosted MCP in Cursor settings; delete /workspace/pellmere-ops/ and confirm the path is gone; disable skills that should not return; then cancel Pro+, last. Substitute Salesforce or a billing console and the order does not change. Read those product pages on the day you drop.

Split what a named-bot delete removes from what a product drop leaves behind

What you lose when you delete names is often the handover: routine wording, the last twenty run records, the chat that named the dirty folders. What you keep is the login, the export, the CLI token, and the Cursor-backend MCP grant. Cancelling Pro+ removes eligibility. It does not add a wipe that named-bot delete failed to perform. You do not get a cleaner disk because the invoice died. You get a disk you may no longer be allowed to open.

Skills travel because they are account objects. Files travel because the computer is assigned to the user, not to a bot. MCP travels because Cursor holds it. "Do not use separate Bots as a security boundary." A cancelled invoice is not a security boundary either.

Delete workspace leftovers before billing cuts the key to the computer

Files the roster wrote under /workspace stay after you delete names and after you cancel Pro+. CRM exports, invoice PDFs, .env files, and notes with customer names are the usual leftovers. Lead Scout did not need a private disk to open /workspace/pellmere-ops/. Chief of Staff Briefing would not need one either if someone later restored eligibility on this account.

Delete or move anything you would not want the next eligible period to see. If you need an archive, put it somewhere this computer cannot reach, then delete the copy here. Do not hand this step to a janitor bot with silent delete rights. Name the folder while the roster still exists. /workspace/pellmere-ops/ is a handle you can delete. Files named export.csv in the workspace root are how residue hides. Confirm with a directory listing. Screenshots of a live vendor dashboard are data. Delete the images.

If billing already cut the key, you cannot list /workspace from Grok Bot until you are eligible again. Vendor-side revoke still matters. The cloud copy may sit until you restore a stamp long enough to open the computer, or until whatever retention Cursor and xAI apply to that VM, which this page will not invent. Do the file pass while you can still list the directory.

Treat admin Terminate as a halt and still expect durable storage to remain

The admin action that the August teams documentation only previewed has shipped as Terminate, under Grok Bot Computers on the Cursor dashboard. It is Enterprise only and for organization admins only, so Pellmere's single Pro+ seat never sees it. Terminate deletes a member's computer, running or hibernated, and the member's next session starts a fresh computer on the same durable disk. Do not tell finance that Terminate is how you drop grok bot.

Terminate keeps the durable disk. Terminating the computer is a halt. It is not a promise that /workspace/pellmere-ops/ vanishes, that Linear must re-auth, or that you get an audit log: synced Bots, files, and logins come back, while apps the member installed are removed. Individual accounts and self-serve Teams still have no audit view of Bot actions; Enterprise has audit logs and Action Recording. Terminate does not record what Inbox Triage already did.

A related control that has also shipped is the team-level ceiling on local execution (Never allow / Ask every time / Always allow), set by team admins on Teams and Enterprise, where members can choose a stricter option but not a looser one. That is about the Mac or Windows machine in front of you, not leftover Linear cookies on the cloud computer. Pause exists today and is also not a wipe. Privacy Mode (Legacy) blocks Grok Bot entirely. Turning that Cursor setting on is a block, not a session close.

Deleting the Cursor account is a different flow, via account settings. This page is a Grok Bot product-exit guide, not an account-deletion guide. If Pellmere also plans to close the Cursor identity, do the vendor sign-outs and the MCP revokes first.

Answer the finance lead who says the cancelled invoice already signed everyone out

The strongest objection to this checklist is: skip it. Cancel Pro+. The computer was a paid feature. Features die when invoices die. Linear will notice. Cursor will drop the MCP grant because Grok Bot is gone. Isolation across bots will mop up anything that remains.

The docs contradict that on independent pages. All bots on an account share one persistent cloud computer assigned to the user, not to a bot (computer and apps). Cookies, sessions, files, and command-line credentials are available across the roster. Do not use separate Bots as a security boundary (approvals, security and privacy). Deleting a Bot does not remove shared-computer files or browser sessions. Hosted MCP sign-in tokens stay with Cursor's backend. Enterprise admin Terminate exists now, and it keeps durable storage.

Finance is right about one number. Cursor Pro+ is sixty dollars a month and Cursor Hobby is free. The sixty-dollar saving is real. The editor remains after the drop. That arithmetic does not sign Linear out. Vendors do not subscribe to your Cursor invoice. They hold a session or an OAuth grant until you revoke it on their page or until that grant expires on their clock. Confirm expiry on the vendor's current page. Do not invent it here.

Where the objection wins is narrow. If the roster never left the computer (no browser login, no file, no CLI token, no connector, no hosted MCP, no saved skill), cancelling Pro+ is a billing tidy plus a roster that goes dark. Most companies that run Grok Bot signed into something. That something is what a product exit is for.

Fail Inbox Triage if a vendor portal still loads after you intend to drop grok bot

An exit you do not test is a story you told yourself. Run checks that are allowed to fail, from a sibling bot on the same account, before you cancel the stamp. Inbox Triage is a good sibling because it was not supposed to be a Linear researcher. If it can still open Linear as ops, the cookie is roster-wide. Checking from Lead Scout's own screen only tells you Lead Scout can see Lead Scout's leftovers.

The fail column is the point. If Linear still loads, you are not finished. If the fourteen files still list, you are not finished. If MCP still shows connected, you are not finished. Do this before finance submits the cancel. After eligibility ends, Inbox Triage may not be there to fail. Teardown of a vendor session does not teardown Gmail. See the safety checklist if a mailbox was in scope.

Refuse to treat a downgrade to Cursor Hobby as leftover Grok Bot access

Cursor Hobby, the free plan, does not include Grok Bot. Every paid Cursor plan does, from Cursor Pro at twenty dollars a month. So a downgrade from Pro+ to Pro is not a drop at all: it keeps Grok Bot and only lowers weekly usage. For Grok Bot, the exit rung is Hobby.

After you drop grok bot by landing on Hobby, the editor will keep working. Cloud Agents, Bugbot, and other Cursor surfaces are separate products. Confirm those on Cursor's pages. Do not treat a working IDE as proof that the Bot computer was wiped, or as leftover Grok Bot. Cursor Hobby vs Cursor Pro for Grok Bot is the plan comparison. Cursor Pro+ and Grok Bot is the sixty-dollar door. A free Hobby editor is not a Bot tombstone.

If Pellmere instead keeps a linked SuperGrok Plus, they have not dropped Grok Bot. They have changed which house pays, and the link keeps granting usage while SuperGrok Plus stays active. With both a Cursor and a SuperGrok subscription, Grok Bot uses whichever has more usage. You drop grok bot when no remaining stamp is on the eligible list. Confirm the live invoice the morning you argue about it. Eligibility widened on 21 August 2026. Launch-week Ultra-only posts, and posts that say Cursor Pro at twenty is excluded, are stale.

SpaceX acquired xAI (announced 2 February 2026). SpaceX acquired Anysphere, the company behind Cursor (closed 14 August 2026). They are siblings under one parent. That is why the handshake is a Cursor flow. It is not why cancelling one Cursor SKU wipes vendor sessions on the Bot computer.

Close vendor sessions from a desktop, not from a pocket pause

From the phone app (iPhone or Android) you can approve steps and pause or resume a routine, but not edit it. Editing and testing a routine still need the desktop app; the phone can now show run history and delete a routine. Supported clients are macOS on Apple silicon and Intel, Windows on x64 and Arm64, and 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 bots run on a managed Linux VM as a non-root user. That is not the Linux desktop client. Sign-out, file removal, and MCP revoke confirmation need a desktop.

Pause from the phone if finance pings you on a train. That stops routines. It does not sign Linear out, delete /workspace/pellmere-ops/, or revoke hosted MCP. Those steps need a desktop: a Mac, a Windows machine, or the Linux desktop app. Do not invent an SSH story as a product-exit method. Grok Bot launched in beta on 11 August 2026. Teach-by-demonstration is unavailable on iPhone and is not an offboarding tool.

Write the drop order into the charter so billing cannot outrun sign-out

The boundary that makes a company-wide Grok Bot roster safe to run is not only "never send, never purchase, never change production." Those still matter. This page adds: never treat a cancelled invoice as a session close, never treat a named-bot delete as a product exit, and never let finance cut Pro+ before Linear shows a login prompt. Put the order in the bot's description so future Marek does not rediscover it at 17:40 on a Tuesday.

Paste this block, then fill the bracketed names.

Role: company Grok Bot roster on [account], eligibility via [stamp, e.g. Cursor Pro+].
You read [systems]. You write files only under /workspace/[company]-ops/.
You never send, never purchase, never change [system] records, never
message a customer. Drafts stay in this conversation.

Product exit is a human checklist. You never claim a sidebar delete
finished it. You never claim a cancelled invoice signed anyone out.
You never claim an admin Terminate cleared the disk.

When I say drop grok bot:
1. List every console, cookie, file path, skill, CLI token, hosted MCP
   server, and routine the roster used. Write them into
   /workspace/[company]-ops/DROP.md. Wait.
2. Pause every routine. I copy anything we still need off this computer.
   You do not invent a replacement schedule on another product.
3. I sign out of [vendors] on this computer and revoke at each source.
   You do not reopen [vendors] to "confirm."
4. I revoke hosted MCP in Cursor settings. Those tokens are not on disk.
5. After I confirm login prompts, delete /workspace/[company]-ops/
   except DROP.md if I still need it, then stop.
6. I disable skills that should not return if this account becomes
   eligible again.
7. I cancel [stamp] last, or I delete named bots last. You do not
   volunteer "the login died with the invoice." That sentence is false
   on this runtime.

Boundary: you never treat a second named bot as a clean room, you never
tell me Isolation across bots will close a session, and you never tell
me an admin Terminate will wipe durable storage.

Three lines in that charter do the real work. Files go in a named folder so the exit has a path. Billing is forbidden from running ahead of sign-out. The bot is forbidden from describing Terminate, delete, or a cancelled invoice as a wipe. Do not share a public bot link that contains vendor URLs or ops emails.

Least Privilege for Bots is how you connect less next time. One Computer, Many Screens is the architecture.

Send per-bot delete and per-bot retirement to the pages that own them

This page stops when the job is a company leaving Grok Bot: cancelling Pro, Pro+, Ultra, a Teams seat, a linked SuperGrok tier, or ending a trial. It stops at a dead vendor session, a swept folder, a revoked MCP grant, paused routines, and an invoice you are allowed to cancel.

It does not walk the sidebar delete control. That is How to Delete a Grok Bot Without Leaving Logins Behind. It does not recreate a keeper routine onto a bot that will still exist in November. That is How to Retire a Grok Bot Without Leaving Sessions Behind. If you still need Grok Bot and only need one name gone, you are on the wrong page. If Monday is already empty because you deleted the owner, use Grok Bot Routine Did Not Run.

There is no Grok Bot-specific spend cap, only the account On-demand monthly limit. Subscriptions include a weekly usage allowance. Overflow is on-demand from model and token cost. This page will not print a dollar figure for that allowance. Spend is not the leftover that survives a drop. Sessions, files, and Cursor-backend tokens are.

Keep reading: How to Delete a Grok Bot Without Leaving Logins Behind, How to Retire a Grok Bot Without Leaving Sessions Behind, Where Grok Bot MCP Sign-In Tokens Actually Live.

Frequently Asked Questions

If I cancel Cursor Pro+ to drop grok bot, are vendor sessions gone?

No. Cancelling Cursor Pro+ removes an eligibility stamp. It does not sign Linear, HubSpot, or any other vendor out of the shared browser on the Grok Bot computer. All bots on an account share one persistent cloud computer assigned to your user account, not to a bot. Deleting named bots also does not remove shared-computer files or sessions. Sign out on Agent Computer while you still have access, then revoke at each vendor on that vendor's current security page. A downgrade to Cursor Hobby leaves the editor working and still does not wipe those cookies.

Does deleting every named bot wipe files when we leave the product?

No. Deleting a Bot removes its active profile, conversation, and routines. Shared computer files and sign-ins are not isolated by Bot and may remain. Screens are work surfaces, not security boundaries. Fourteen CSVs under a company folder stay until you delete that folder yourself. Skills remain available across bots if the account later becomes eligible again. Copy routine text before you delete, because the last twenty run records per routine die with the bot. Then sweep the disk. Then cancel the stamp.

Do hosted MCP tokens die when Grok Bot eligibility ends?

No. Hosted MCP sign-in tokens stay with Cursor's backend and are never stored on the computer. Dropping Grok Bot does not walk into that drawer. If the company keeps any Cursor account, including Hobby, those grants can remain until you revoke them in Cursor settings. A browser sign-out does not pull a backend token. A settings revoke does not clear a cookie on the shared computer. Close both drawers.

Will an admin Terminate wipe durable storage after we cancel?

No. Terminate, under Grok Bot Computers on the Cursor dashboard, is Enterprise only and for organization admins only. It deletes a member's computer while the durable disk is kept, and the member's next session starts a fresh computer on that disk. Kept durable storage means files you hoped would vanish may still be there. Terminate is a halt, not an audit log, and not a substitute for sign-out and a directory listing. Pause exists today and also does not wipe the disk. Do the file pass yourself, before billing cuts the key.