Documentation 2026-10-01 23:57 UTC to 2026-10-02 23:57 UTC

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. **Grok Bot Computers** on the6its work. The **Bot Computers** section of 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 two ways to manage those computers: run a recreate or8organization admins two ways to manage those computers: run a recreate or

9terminate across many members at once, or turn on9terminate across many members at once with **Manage Bot Computers**, or turn on

10[automatic termination](#terminate-inactive-computers-automatically) for10[automatic termination](#terminate-inactive-computers-automatically) for

11computers that go 30 days without use. For the rest of the admin controls, see11computers that go 30 days without use. For the rest of the admin controls, see

12[Grok Bot for teams and enterprises](/grok-bot/teams-and-enterprises).12[Grok Bot for teams and enterprises](/grok-bot/teams-and-enterprises).

13 13 

14**Grok Bot Computers is Enterprise only**, and it appears only for organization14**Manage Bot Computers is Enterprise only**, and it appears only for organization

15admins. Team admin rights are not enough, because one computer spans every team15admins. Team admin rights are not enough, because one computer spans every team

16the member belongs to. Members never see this control. Team admins can still16the member belongs to. Members never see this control. Team admins can still

17[restart the team's computers after a settings change](#restart-after-a-settings-change).17[restart the team's computers after a settings change](#restart-after-a-settings-change).

30 30 

31## Run an operation31## Run an operation

32 32 

33### Open Grok Bot Computers33### Open Manage Bot Computers

34 34 

35Go to [Grok Bot in the Cursor dashboard](https://cursor.com/dashboard/bot),35Go to [Grok Bot in the Cursor dashboard](https://cursor.com/dashboard/bot).

36find **Grok Bot Computers**, and select **Manage**.36Under **Bot Computers**, find **Manage Bot Computers** and select **Manage**.

37 37 

38### Select members38### Select members

39 39 

98 98 

99Team admins on an Enterprise team can run this restart, not only organization99Team admins on an Enterprise team can run this restart, not only organization

100admins. It only recreates; **Terminate VMs** and **Delete VMs and Data** stay100admins. It only recreates; **Terminate VMs** and **Delete VMs and Data** stay

101with organization admins under **Grok Bot Computers**.101with organization admins under **Manage Bot Computers**.

102 102 

103## Terminate inactive computers automatically103## Terminate inactive computers automatically

104 104 

105A hibernated computer stays around until someone terminates it, even when the105A hibernated computer stays around until someone terminates it, even when the

106member has moved on or stopped using Grok Bot. **Terminate Inactive106member has moved on or stopped using Grok Bot. **Terminate Inactive

107Computers**, below **Grok Bot Computers** on the same dashboard page, does that107Computers**, just above **Manage Bot Computers** in the same section, does that

108cleanup for you. When a member's computer goes 30 days without use, Cursor108cleanup for you. When a member's computer goes 30 days without use, Cursor

109terminates it. Using Grok Bot again restarts the count.109terminates it. Using Grok Bot again restarts the count.

110 110 

68it:68it:

69 69 

701. Open the Bot's **Share** menu and choose **Publish to Team**.701. Open the Bot's **Share** menu and choose **Publish to Team**.

712. In **How should your Team Bot start?**, choose one:712. The Bot checks what a copy would start from: this chat and its own

72 * **Copy** *Bot name* to start with the Bot's chat and memories. Your72 memories.

73 personal Bot stays private and keeps working for you.73 * If most of those memories are personal facts about you, such as your

74 * **Start fresh** to create a new Team Bot without the chat or its memories.74 family, health, or schedule, or the chat is about your own life or

753. Work through the setup cards. For each one, choose what the team copy gets:75 individual work, it asks **How should your Team Bot start?** Choose

76 plugins, secrets, memories, skills, files, and routines. Memories you don't76 **Copy** *Bot name* to start with the Bot's chat and memories, or

77 pick stay private; choose **Keep private** to share none.77 **Start fresh** to create a new Team Bot without them.

78 * Otherwise, including when the Bot is new, it makes the copy right away and

79 replies **Done. Your team copy is in the sidebar.**

803. In the team copy's chat, work through the setup cards. For each one, choose

81 what the team copy gets: plugins, secrets, memories, skills, files, and

82 routines. Memories you don't pick stay private; choose **Keep private** to

83 share none.

784. For routines, choose whether each one moves to the team copy or stays on844. For routines, choose whether each one moves to the team copy or stays on

79 your personal Bot. Either way, a routine only runs for you, and teammates85 your personal Bot. Either way, a routine only runs for you, and teammates

80 never see it.86 never see it.

81 87 

82If most of what a Bot knows is about you personally, a copy won't do much for88Your personal Bot stays private and keeps working for you, and teammates can't

83your team. Create a new Team Bot instead.89see the team copy until you publish it. If most of what a Bot knows is about

90you personally, a copy won't do much for your team. Create a new Team Bot

91instead.

84 92 

85## Set up what the Bot needs93## Set up what the Bot needs

86 94 

351### Add Team Bots for members by default359### Add Team Bots for members by default

352 360 

353On the Grok Bot page of the361On the Grok Bot page of the

354[Cursor dashboard](https://cursor.com/dashboard/bot), under **Bot362[Cursor dashboard](https://cursor.com/dashboard/bot), under **Team Bots**,

355Capabilities**, choose **Manage Team Bots**. For each Team Bot, choose who gets363choose **Manage Team Bots**. For each Team Bot, choose who gets it in their

356it in their sidebar automatically: **All team**, **None**, or specific groups.364sidebar automatically: **All team**, **None**, or specific groups. Groups come

357Groups come from the **Members & Groups** page.365from the **Members & Groups** page.

358 366 

359Members who get a Team Bot this way see **Required by your admin. You can't367Members who get a Team Bot this way see **Required by your admin. You can't

360turn this off.**368turn this off.**

265of four modes, from allow-all to a team allowlist of domains and IP ranges:265of four modes, from allow-all to a team allowlist of domains and IP ranges:

266**No Policy (Allow All)**, **Allow All Network Access**, **Defaults + Team266**No Policy (Allow All)**, **Allow All Network Access**, **Defaults + Team

267Allowlist**, or **Team Allowlist Only**. Directory groups can carry their own267Allowlist**, or **Team Allowlist Only**. Directory groups can carry their own

268policy as **Group Network Access**, and **Lock for all groups** makes the team268policy as **Group Network Access**, and **Lock for All Groups** makes the team

269policy apply to everyone. Teams without a policy default to allow-all. See269policy apply to everyone. Teams without a policy default to allow-all. See

270[network policy](/grok-bot/security#network-policy) for the modes and how a270[network policy](/grok-bot/security#network-policy) for the modes and how a

271new policy reaches running computers.271new policy reaches running computers.

325 325 

326Available on the Enterprise plan.326Available on the Enterprise plan.

327 327 

328#### Grok Bot Computers328#### Manage Bot Computers

329 329 

330Lets organization admins recreate or terminate the computers of many members330Lets organization admins recreate or terminate the computers of many members

331at once, with a result for each member. Team admin rights are not enough,331at once, with a result for each member. Team admin rights are not enough,

333members to the latest image and Team Setup while keeping their Bots, files, and333members to the latest image and Team Setup while keeping their Bots, files, and

334logins. **Terminate** ends the member's current work and keeps the durable334logins. **Terminate** ends the member's current work and keeps the durable

335disk; the member's next session starts a fresh computer on it.335disk; the member's next session starts a fresh computer on it.

336**Terminate Inactive Computers**, below it, does the terminate for you when a336**Terminate Inactive Computers**, just above it in the **Bot Computers**

337computer goes 30 days without use. It is off by default. None of these remove337section, does the terminate for you when a computer goes 30 days without use.

338It is off by default. None of these remove

338access: to do that, remove the member from the team or turn off Grok Bot for339access: to do that, remove the member from the team or turn off Grok Bot for

339their group, and revoke their sessions in your identity provider. See340their group, and revoke their sessions in your identity provider. See

340[Manage Grok Bot computers](/grok-bot/computers).341[Manage Grok Bot computers](/grok-bot/computers).