Manage Grok Bot Computers: Recreate, Terminate and Delete Data

Each member gets one hosted computer where every Bot they run does its work. Manage Member Computers and Data sits under Security & Compliance on the Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. page of the Cursor dashboard, and it's Enterprise only. Organization admins and Enterprise team admins can use it, and members never see it.

Recreate and terminate share more than you might expect. Both keep the member's durable disk, so synced Bots, files and logins come back on the next computer. Both remove apps and packages the member installed themselves, and anything your Team Setup Scripts install comes back. Where they differ is what happens to running work.

Network policy changes reach computers without a recreate, so you don't need one for that. And terminating doesn't remove access. To do that, remove the member from the team or turn off their access with Manage Group Access, and revoke their sessions in your identity provider, which the identity guide covers.

Delete All Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. Data is the heavier option. It permanently deletes a member's Bots, conversations, memory, routines and computer, across every team they belong to. Their Cursor account stays. Because the deletion reaches every team the member is in, running it from one team also removes what the member built under their other teams.

The same menu also has Delete VMs and Data, which removes the computer and its durable data. The docs say to use either delete option only when you want the member to start from empty, which is a narrower case than it might sound. For a stuck computer, terminate is enough.

The flow is five short steps in the dashboard. Selection is by search, so for a large group it's mostly a matter of getting the search right before you use Select all.

1. 1Go to Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. in the Cursor dashboard, find Manage Member Computers and Data under Security & Compliance, and select Manage.
2. 2Search by name or email and check the members you want. Select all picks everyone in the current results.
3. 3Open Manage selected and pick Recreate VMs or Terminate VMs. A confirmation screen restates the action and the number of members it affects.
4. 4Select Recreate VMs or Terminate VMs to start. Members without a computer are skipped.
5. 5Watch the progress card for queued, running, complete, skipped and failed counts, with a status on each member's row. When it finishes, select Done to clear the results.

A few things about how the operation runs change how you plan around it:

• It runs on Cursor's side. Closing the dialog or the browser doesn't stop it, and reopening Manage in the same browser picks the progress back up.
• Large operations take a while. Members are processed in batches, and each recreate waits for the replacement to be ready before it counts as complete.
• One operation per team at a time. The action buttons stay disabled until you select Done on the finished results.
• Retry Start never duplicates work. Use it when the dashboard can't confirm the operation started.

You can also select a member from any team they belong to. One computer serves every team the member is in, so recreating or terminating it from one team affects the same computer everywhere.

A finished operation lists a result for every member you selected. Skipped results need nothing from you. Failed results mostly mean wait, or run again.

Read the failure list as reassuring, mostly. VM scan incomplete means Cursor made no change at all, and a recreate that fails because a Bot couldn't pause leaves the member on their current computer. The docs say to run the operation again in both cases. The deletion failures are the ones to watch, since a deletion that fails twice is the documented point to involve support.

The last row is the one you'll probably see most during a busy workday, since it comes from Bots that are mid-turn. The docs suggest retrying once the member's Bots are idle, if you can arrange that.

Yes. To roll out across many teams from a script, start the same operations with the Organization API. You send a team, a list of members and an action, then poll the operation for counts and a result per member.

The API and the dashboard share the one-operation-per-team limit. An operation started from either place blocks the other until it finishes, so whichever starts second can't run until the first is done.

A hibernated computer stays around until someone terminates it, even when the member has moved on or stopped using Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition.. Terminate Inactive Computers, under Bot Computers on the same dashboard page, does that cleanup. When a member's computer goes 30 days without use, Cursor terminates it, and using Grok Bot again restarts the count.

It's off by default, and turning it on opens a confirmation. Two things to know before you select Turn On:

• Computers already past 30 days are included, with no grace period. Cursor checks hibernated computers on a rolling schedule, so termination lands in the days after the 30-day mark.
• Members lose nothing and do nothing. The durable disk stays, and the next message starts a fresh computer with Bots, files and logins in place. Self-installed apps and packages are removed, and Team Setup Scripts run again.

It can't interrupt a working Bot. The 30 days count from when the computer went to sleep after its last use, and an awake computer is never terminated by this setting. Turning the setting off stops further terminations. Because one computer spans every team a member belongs to, the setting applies to a member's computer if any of their Enterprise teams has it on.

During a recreate, the desktop app shows Updating Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition.'s Computer until the switch completes, and working Bots pause at a safe point and continue on the new computer. Sign-in sessions inside the computer can drop, so members may need to sign in to company tools again under your identity provider's policies.

After a terminate, manual or automatic, the member's next message starts a fresh computer on their durable disk. The reconnect can take a few minutes. Bots, files and logins that had synced come back, but a turn that was running is lost.

That lost turn is worth telling members about before a planned terminate. For image rollouts more generally, the deployment guide explains how Cursor moves idle computers to new images on its own, and the admin overview covers the rest of the Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. page.