3# Manage Grok Bot computers3# Manage Grok Bot computers
4 4
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. The **Bot Computers** section of the6its work. The
7[Grok Bot page of the Cursor dashboard](https://cursor.com/dashboard/bot) gives7[Grok Bot page of the Cursor dashboard](https://cursor.com/dashboard/bot) gives
8organization admins and team admins on an Enterprise team two ways to manage8organization admins and team admins on an Enterprise team two ways to manage
9those computers: run a recreate or terminate across many members at once with9those computers. Under **Security & Compliance**, **Manage Member Computers and
10**Manage Bot Computers**, or turn on10Data** runs a recreate or terminate across many members at once. Under **Bot
11Computers**, you can turn on
11[automatic termination](#terminate-inactive-computers-automatically) for12[automatic termination](#terminate-inactive-computers-automatically) for
12computers that go 30 days without use. For the rest of the admin controls, see13computers that go 30 days without use. For the rest of the admin controls, see
13[Grok Bot for teams and enterprises](/grok-bot/teams-and-enterprises).14[Grok Bot for teams and enterprises](/grok-bot/teams-and-enterprises).
14 15
15**Manage Bot Computers is Enterprise only**. It appears for organization admins16**Manage Member Computers and Data is Enterprise only**. It appears for
16and for team admins on an Enterprise team. Members never see this control. Team17organization admins and for team admins on an Enterprise team. Members never
17admins can also18see this control. Team admins can also
18[restart the team's computers after a settings change](#restart-after-a-settings-change).19[restart the team's computers after a settings change](#restart-after-a-settings-change).
19 20
20## Recreate or terminate21## Recreate or terminate
31 32
32## Run an operation33## Run an operation
33 34
34### Open Manage Bot Computers35### Open Manage Member Computers and Data
35 36
36Go to [Grok Bot in the Cursor dashboard](https://cursor.com/dashboard/bot).37Go to [Grok Bot in the Cursor dashboard](https://cursor.com/dashboard/bot).
37Under **Bot Computers**, find **Manage Bot Computers** and select **Manage**.38Under **Security & Compliance**, find **Manage Member Computers and Data** and
39select **Manage**.
38 40
39### Select members41### Select members
40 42
48The same menu also offers **Delete VMs and Data**, which removes the computer50The same menu also offers **Delete VMs and Data**, which removes the computer
49and its durable data. Use it only when you want the member to start from empty.51and its durable data. Use it only when you want the member to start from empty.
50 52
53The menu also has **Delete All Grok Bot Data**, which goes further. It
54permanently deletes each selected member's Grok Bot data on every team they
55belong to: their Bots (including Team Bots that teammates use), conversations,
56memory, routines, connected apps, email inboxes, files, and computers. Members
57stay on the team and start fresh the next time they use Grok Bot. It cannot be
58undone and works on up to 100 members at a time. Both delete actions ask you to
59type `DELETE` to confirm.
60
51### Confirm61### Confirm
52 62
53Select **Recreate VMs** or **Terminate VMs** to start. Members without a63Select **Recreate VMs** or **Terminate VMs** to start. Members without a
79 89
80## Run operations through the API90## Run operations through the API
81 91
82Organization admins can recreate, terminate, or delete members' computers from92Organization admins can recreate, terminate, or delete members' computers, or
83a script with the Organization API. Send a team, a list of members, and an93delete all of their Grok Bot data, from a script with the Organization API.
94Send a team, a list of members, and an
84action, then poll the operation for its counts and, for operations of up to95action, then poll the operation for its counts and, for operations of up to
851,000 members, a result for each member. The API and the dashboard share the961,000 members, a result for each member. The API and the dashboard share the
86limit of one operation per team, so a start from either one fails while97limit of one operation per team, so a start from either one fails while
113 124
114Team admins on an Enterprise team can run this restart, not only organization125Team admins on an Enterprise team can run this restart, not only organization
115admins. It only recreates; **Terminate VMs** and **Delete VMs and Data** are126admins. It only recreates; **Terminate VMs** and **Delete VMs and Data** are
116under **Manage Bot Computers**.127under **Manage Member Computers and Data**.
117 128
118## Terminate inactive computers automatically129## Terminate inactive computers automatically
119 130
120A hibernated computer stays around until someone terminates it, even when the131A hibernated computer stays around until someone terminates it, even when the
121member has moved on or stopped using Grok Bot. **Terminate Inactive132member has moved on or stopped using Grok Bot. **Terminate Inactive
122Computers**, just above **Manage Bot Computers** in the same section, does that133Computers**, in the **Bot Computers** section, does that
123cleanup for you. When a member's computer goes 30 days without use, Cursor134cleanup for you. When a member's computer goes 30 days without use, Cursor
124terminates it. Using Grok Bot again restarts the count.135terminates it. Using Grok Bot again restarts the count.
125 136
