SPB Git

Repository Public

computers.md 6.3 KB 106 lines markdown

1<!-- source: https://docs.x.ai/grok-bot/computers (from https://docs.x.ai/llms-full.txt, retrieved 2026-09-19T05:28:55Z) -->2#### Manage and protect34# Manage Grok Bot computers56Each member of your team gets one hosted computer where every Bot they run does7its work. **Grok Bot Computers** on the8[Grok Bot page of the Cursor dashboard](https://cursor.com/dashboard/bot) lets9an organization admin recreate or terminate those computers for many members at10once, with a confirmation step and a result for each member. For the rest of11the admin controls, see12[Grok Bot for teams and enterprises](/grok-bot/teams-and-enterprises).1314Grok Bot Computers is Enterprise only, and it appears only for organization15admins. Team admin rights are not enough, because one computer spans every team16the member belongs to. Members never see this control.1718## Recreate or terminate1920Both actions keep the member's durable disk. They differ in what happens next.2122| Action | What happens | What members keep | When to use it |23| --- | --- | --- | --- |24| **Recreate** | Builds a replacement computer on the latest image and runs [Team Setup](/grok-bot/teams-and-enterprises#team-setup). The current computer stays available until the replacement is ready, then Grok Bot switches over. | Synced Bots, files, and logins. A Bot that is mid-turn is asked to pause at a safe point and resumes on the new computer. If it cannot pause in time, the recreate for that member is not started and shows as failed. | Roll out a new image or apply an updated Team Setup manifest to many members at once. [Network policy](/grok-bot/security#network-policy) changes reach computers without a recreate. |25| **Terminate** | Deletes the member's computer, running or hibernated. It does not restart on its own; the member's next session starts a fresh computer on the same durable disk. | Synced Bots, files, and logins. Running work stops. | End a member's current work, or clear a computer that is stuck. Terminating does not remove access; see the [FAQ](#faq). |2627Both actions remove apps and packages that members installed themselves.28Anything your Team Setup manifests install comes back on the new computer.2930## Run an operation31321. Open Grok Bot Computers. Go to33   [Grok Bot in the Cursor dashboard](https://cursor.com/dashboard/bot), find34   **Grok Bot Computers**, and select **Manage**.352. Select members. Search by name or email, then check the members you want.36   **Select all** picks everyone in the current results.373. Choose an action. Select **Recreate VMs…** or **Terminate VMs…**. A38   confirmation screen restates the action and the number of members it39   affects.404. Confirm. Select **Recreate VMs** or **Terminate VMs** to start. Members41   without a computer are skipped.425. Watch the results. A progress card shows queued, running, complete, skipped,43   and failed counts, and each member's row shows its status. When the44   operation finishes, select **Done** to clear the results and start another.4546## How an operation runs4748* **It runs on Cursor's side.** Closing the dialog or the browser does not stop49  it. Reopen **Manage** in the same browser to pick the progress back up.50* **Large operations take a while.** Members are processed in batches, and each51  recreate waits for the replacement computer to be ready before it counts as52  complete.53* **One operation per team at a time.** The action buttons stay disabled until54  you select **Done** on the finished results.55* **Retry Start never duplicates work.** Use it when the dashboard cannot56  confirm the operation started.5758## Skipped and failed members5960A finished operation lists a result for every member you selected.6162| Result | Meaning | What to do |63| --- | --- | --- |64| **Skipped**, No VM | The member had no running or hibernated computer. | Nothing. |65| **Skipped**, Action could not be completed | The member left the team, or their account changed, while the operation was queued. | Nothing. |66| **Failed**, Another recreation is in progress | The member's computer is already being recreated, by an update or another admin. | Wait for it to finish, then run again for this member. |67| **Failed**, VM scan incomplete | Cursor could not confirm the state of the member's computer, so it made no change. | Run the operation again in a few minutes. |68| **Failed**, Action could not be completed | The recreate or terminate did not finish. For a recreate, a Bot on the member's computer may have been unable to pause in time; the member's current computer is left as it was. | Run the operation again for the affected members, once their Bots are idle if you can. If it fails twice, [contact support](https://cursor.com/help/grok-bot/get-help) with the member's email and the time of the operation. |6970## What members see7172During a recreate, the desktop app shows **Updating Grok Bot's Computer** until73the switch completes. Bots that were working pause at a safe point and continue74on the new computer. If a Bot cannot pause in time, the member keeps their75current computer and that member's result shows as failed. Sign-in sessions76inside the computer can drop when it is recreated, so members sign in to77company tools again under your identity provider's policies.7879After a terminate, the member's next message starts a fresh computer on their80durable disk. The reconnect can take a few minutes. Bots, files, and logins81that had synced come back; a turn that was running is lost.8283## FAQ8485### Can I recreate a member's computer from a different team?8687Yes. Select the member from any team they belong to. One computer serves every88team the member is in, so recreating or terminating it from one team affects89the same computer everywhere.9091### Does terminating stop a member from using Grok Bot?9293No. Terminating a computer ends the member's current work; their next message94starts a fresh computer on the same durable disk, with their Bots, files, and95logins. To remove access, remove the member from the team or turn off their96access with **Manage Group Access**, and revoke their sessions in your identity97provider. See98[Enable Grok Bot](/grok-bot/teams-and-enterprises#enable-grok-bot).99100## Related pages101102* [Grok Bot for teams and enterprises](/grok-bot/teams-and-enterprises)103* [Grok Bot security](/grok-bot/security)104* [Connect to private networks](/grok-bot/private-networks)105* [Update, recover, or reset the computer](/grok-bot/computer-and-apps#update-recover-or-reset-the-computer)106
Files main
Menu

Theme