SpyBara
Go Premium

Documentation 2026-11-03 23:00 UTC to 2026-11-04 23:01 UTC

1 file changed +13 −9. View all changes and history on the product overview
2026
Thu 12 22:57 Wed 11 23:00 Tue 10 23:57 Fri 6 23:59 Wed 4 23:01

computers.md +13 −9

Details

5Each member of your team gets one hosted computer where every Bot they run does5Each member of your team gets one hosted computer where every Bot they run does

6its work. **Manage Member Computers and Data**, under **Security & Compliance**6its work. **Manage Member Computers and Data**, under **Security & Compliance**

7on the [Grok Bot page of the Cursor dashboard](https://cursor.com/dashboard/bot),7on the [Grok Bot page of the Cursor dashboard](https://cursor.com/dashboard/bot),

8lets admins recreate or terminate computers across many members at once, or8lets admins recreate or terminate computers across many members at once,

9[delete computers along with their data](#delete-vms-and-data), or

9[delete all of a member's Grok Bot data](#delete-all-grok-bot-data).10[delete all of a member's Grok Bot data](#delete-all-grok-bot-data).

10**Terminate Inactive Computers**, under **Bot Computers**, turns on11**Terminate Inactive Computers**, under **Bot Computers**, turns on

11[automatic termination](#terminate-inactive-computers-automatically) for members12[automatic termination](#terminate-inactive-computers-automatically) for members


29| **Recreate** | Builds a replacement computer on the latest image and runs [Team Setup Scripts](/grok-bot/private-networks). The current computer stays available until the replacement is ready, then Grok Bot switches over. A Bot that is mid-turn pauses at a safe point and resumes on the new computer. If it cannot pause in time, that member's recreate is not started and shows as failed. | Roll out a new image or an updated Team Setup manifest to many members at once. [Network policy](/grok-bot/security#network-policy) changes reach computers without a recreate. |30| **Recreate** | Builds a replacement computer on the latest image and runs [Team Setup Scripts](/grok-bot/private-networks). The current computer stays available until the replacement is ready, then Grok Bot switches over. A Bot that is mid-turn pauses at a safe point and resumes on the new computer. If it cannot pause in time, that member's recreate is not started and shows as failed. | Roll out a new image or an updated Team Setup manifest to many members at once. [Network policy](/grok-bot/security#network-policy) changes reach computers without a recreate. |

30| **Terminate** | Deletes the member's computer, running or hibernated. Running work stops. The computer does not restart on its own; the member's next message starts a fresh one on the same durable disk. | End a member's current work, or clear a computer that is stuck. Terminating does not remove access; see the [FAQ](#faq). |31| **Terminate** | Deletes the member's computer, running or hibernated. Running work stops. The computer does not restart on its own; the member's next message starts a fresh one on the same durable disk. | End a member's current work, or clear a computer that is stuck. Terminating does not remove access; see the [FAQ](#faq). |

31 32 

33## Delete VMs and data

34 

35**Delete VMs and Data** deletes a member's computer and its durable disk. Their

36Bots and conversations stay, and their next message starts an empty computer.

37 

38* **At most 1,000 members** per operation.

39* **It can't be undone.** Each operation is recorded in the

40 [Audit Log](https://cursor.com/dashboard/audit-log).

41 

32## Delete all Grok Bot data42## Delete all Grok Bot data

33 43 

34**Delete All Grok Bot Data** permanently deletes a member's Bots,44**Delete All Grok Bot Data** permanently deletes a member's Bots,


58 68 

59Open **Manage selected** and pick **Recreate VMs** or **Terminate VMs**. A69Open **Manage selected** and pick **Recreate VMs** or **Terminate VMs**. A

60confirmation screen restates the action and the number of members it affects.70confirmation screen restates the action and the number of members it affects.

61The same menu also offers **Delete VMs and Data**, which removes the computer71The same menu also offers [Delete VMs and Data](#delete-vms-and-data) and

62and its durable data, and

63[Delete All Grok Bot Data](#delete-all-grok-bot-data). Use either only when you72[Delete All Grok Bot Data](#delete-all-grok-bot-data). Use either only when you

64want the member to start from empty. Both delete actions ask you to type73want the member to start from empty.

65`DELETE` to confirm.

66 74 

67### Confirm75### Confirm

68 76 


123| **Failed**, Grok Bot data could not be deleted | The deletion did not finish. | Run the operation again. If it fails twice, [contact support](https://cursor.com/help/grok-bot/get-help). |131| **Failed**, Grok Bot data could not be deleted | The deletion did not finish. | Run the operation again. If it fails twice, [contact support](https://cursor.com/help/grok-bot/get-help). |

124| **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, and the member keeps their current computer. | 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. |132| **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, and the member keeps their current computer. | 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. |

125| **Failed**, Recreation status unavailable | Cursor could not tell whether a recreate was already running on the member's computer, so it made no change. | Run the operation again in a few minutes. |133| **Failed**, Recreation status unavailable | Cursor could not tell whether a recreate was already running on the member's computer, so it made no change. | Run the operation again in a few minutes. |

126| **Failed**, Another computer operation is in progress | Another operation was using the member's computer during **Delete VMs and Data**. | Wait for it to finish, then run again for this member. |

127| **Failed**, Computer operation lock unavailable | Cursor could not reserve the member's computer for **Delete VMs and Data**, so it made no change. | Run the operation again. |

128| **Failed**, Data in an older format can't be deleted yet | The member's stored data is in an older format, so **Delete VMs and Data** deleted nothing. | [Contact support](https://cursor.com/help/grok-bot/get-help) with the member's email. |

129| **Failed**, Durable data could not be deleted | **Delete VMs and Data** removed the computer but not its stored data. | Run **Delete VMs and Data** again for this member. If it fails twice, [contact support](https://cursor.com/help/grok-bot/get-help). |

130 134 

131## Restart after a settings change135## Restart after a settings change

132 136