Documentation 2026-09-27 22:59 UTC to 2026-09-28 23:57 UTC

31 31 

32When an action needs approval, the conversation shows the proposed operation32When an action needs approval, the conversation shows the proposed operation

33and its inputs. Review the target, scope, and values before approving.33and its inputs. Review the target, scope, and values before approving.

34 34**Allow once** lets the Bot continue with that action, **Always allow** can

35* On desktop, **Allow once** lets the Bot continue with that action and35save a matching rule, and **Deny** blocks it. The controls are the same on

36 **Deny** blocks it. **Always allow** can save a matching rule.36iPhone.

37* On iPhone and Android, the Auto-review sheet offers **Allow**, **Deny**, and,

38 when a rule is proposed, **Always allow**; a local-command card offers

39 **Allow once** and **Deny**.

40 37 

41Do not approve an action whose target or effect you cannot identify. Ask the Bot38Do not approve an action whose target or effect you cannot identify. Ask the Bot

42to explain it in plain language or produce a draft first.39to explain it in plain language or produce a draft first.

44## Configure Auto Review41## Configure Auto Review

45 42 

46With Auto Review on, Grok Bot evaluates tool calls and computer actions before43With Auto Review on, Grok Bot evaluates tool calls and computer actions before

47they run. Open **Settings → General → Bot → Auto-review** to add rules.44they run. Open **Settings → General → Auto-review** to add rules.

48 45 

49* **Ask first** rules always stop matching actions for you.46* **Ask first** rules always stop matching actions for you.

50* **Allow automatically** rules let matching actions proceed only when the47* **Allow automatically** rules let matching actions proceed only when the

66behavior change over time. Auto Review is model-based and should complement,63behavior change over time. Auto Review is model-based and should complement,

67not replace, least privilege and explicit approval boundaries.64not replace, least privilege and explicit approval boundaries.

68 65 

69Personal Auto-review rules are saved to your account and applied on every66Personal Auto-review rules are stored on the current desktop and synced to its

70desktop you sign in to, as well as on your Grok Bot computer.67Grok Bot computer, so another desktop installation needs its own.

71 68 

72## Enter passwords and verification codes yourself69## Enter passwords and verification codes yourself

73 70 

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. **Grok Bot Computers** on the

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

8an organization admin recreate or terminate those computers for many members at8organization admins two ways to manage those computers: run a recreate or

9once, with a confirmation step and a result for each member. For the rest of9terminate across many members at once, or turn on

10the admin controls, see10[automatic termination](#terminate-inactive-computers-automatically) for

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

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

12 13 

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

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

15the member belongs to. Members never see this control.16the member belongs to. Members never see this control.

16 17 

17## Recreate or terminate18## Recreate or terminate

18 19 

19Both actions keep the member's durable disk. They differ in what happens next.20Both actions keep the member's durable disk, so their synced Bots, files, and

21logins come back on the next computer. Both remove apps and packages members

22installed themselves. Anything your Team Setup manifests install comes back on

23the new computer.

20 24 

21| Action | What happens | What members keep | When to use it |25| Action | What happens | When to use it |

22| --- | --- | --- | --- |26| --- | --- | --- |

23| **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. |27| **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. 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. |

24| **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). |28| **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). |

25 

26Both actions remove apps and packages that members installed themselves.

27Anything your Team Setup manifests install comes back on the new computer.

28 29 

29## Run an operation30## Run an operation

30 31 

311. Open Grok Bot Computers. Go to32### Open Grok Bot Computers

32 [Grok Bot in the Cursor dashboard](https://cursor.com/dashboard/bot), find33 

33 **Grok Bot Computers**, and select **Manage**.34Go to [Grok Bot in the Cursor dashboard](https://cursor.com/dashboard/bot),

342. Select members. Search by name or email, then check the members you want.35find **Grok Bot Computers**, and select **Manage**.

35 **Select all** picks everyone in the current results.36 

363. Choose an action. Select **Recreate VMs…** or **Terminate VMs…**. A37### Select members

37 confirmation screen restates the action and the number of members it38 

38 affects.39Search by name or email, then check the members you want. **Select all** picks

394. Confirm. Select **Recreate VMs** or **Terminate VMs** to start. Members40everyone in the current results.

40 without a computer are skipped.41 

415. Watch the results. A progress card shows queued, running, complete, skipped,42### Choose an action

42 and failed counts, and each member's row shows its status. When the43 

43 operation finishes, select **Done** to clear the results and start another.44Open **Manage selected** and pick **Recreate VMs** or **Terminate VMs**. A

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

46The same menu also offers **Delete VMs and Data**, which removes the computer

47and its durable data. Use it only when you want the member to start from empty.

48 

49### Confirm

50 

51Select **Recreate VMs** or **Terminate VMs** to start. Members without a

52computer are skipped.

53 

54### Watch the results

55 

56A progress card shows queued, running, complete, skipped, and failed counts,

57and each member's row shows its status. When the operation finishes, select

58**Done** to clear the results and start another.

44 59 

45## How an operation runs60## How an operation runs

46 61 

64| **Skipped**, Action could not be completed | The member left the team, or their account changed, while the operation was queued. | Nothing. |79| **Skipped**, Action could not be completed | The member left the team, or their account changed, while the operation was queued. | Nothing. |

65| **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. |80| **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. |

66| **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. |81| **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. |

67| **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. |82| **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. |

83 

84## Terminate inactive computers automatically

85 

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

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

88Computers**, below **Grok Bot Computers** on the same dashboard page, does that

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

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

91 

92The setting is off by default. Turning it on opens a confirmation. Two things

93to know before you select **Turn On**:

94 

95* **Computers already past 30 days are included.** There is no grace period.

96 Cursor checks hibernated computers on a rolling schedule, so termination

97 lands in the days after the 30-day mark rather than at the exact moment.

98* **Members lose nothing and do nothing.** An automatic terminate works like a

99 manual one. The durable disk stays, and the member's next message starts a

100 fresh computer with their Bots, files, and logins in place. Apps and packages

101 they installed themselves are removed, and Team Setup runs again.

102 

103Turning the setting off stops further terminations. One computer spans every

104team a member belongs to, so the setting applies to a member's computer if any

105of their Enterprise teams has it on.

68 106 

69## What members see107## What members see

70 108 

71During a recreate, the desktop app shows **Updating Grok Bot's Computer** until109During a recreate, the desktop app shows **Updating Grok Bot's Computer** until

72the switch completes. Bots that were working pause at a safe point and continue110the switch completes. Bots that were working pause at a safe point and continue

73on the new computer. If a Bot cannot pause in time, the member keeps their111on the new computer. Sign-in sessions inside the computer can drop when it is

74current computer and that member's result shows as failed. Sign-in sessions112recreated, so members sign in to company tools again under your identity

75inside the computer can drop when it is recreated, so members sign in to113provider's policies.

76company tools again under your identity provider's policies.

77 114 

78After a terminate, the member's next message starts a fresh computer on their115After a terminate, manual or automatic, the member's next message starts a

79durable disk. The reconnect can take a few minutes. Bots, files, and logins116fresh computer on their durable disk. The reconnect can take a few minutes.

80that had synced come back; a turn that was running is lost.117Bots, files, and logins that had synced come back; a turn that was running is

118lost.

81 119 

82## FAQ120## FAQ

83 121 

89 127 

90### Does terminating stop a member from using Grok Bot?128### Does terminating stop a member from using Grok Bot?

91 129 

92No. Terminating a computer ends the member's current work; their next message130No. Terminating a computer, by hand or automatically, ends the member's current

93starts a fresh computer on the same durable disk, with their Bots, files, and131work. Their next message starts a fresh computer on the same durable disk, with

94logins. To remove access, remove the member from the team or turn off their132their Bots, files, and logins. To remove access, remove the member from the

95access with **Manage Group Access**, and revoke their sessions in your identity133team or turn off their access with **Manage Group Access**, and revoke their

96provider. See134sessions in your identity provider. See

97[Enable Grok Bot](/grok-bot/teams-and-enterprises#enable-grok-bot).135[Enable Grok Bot](/grok-bot/teams-and-enterprises#enable-grok-bot).

98 136 

137### Can automatic termination interrupt a Bot that is still working?

138 

139No. The 30 days count from when the computer went to sleep after its last use.

140A computer that is awake, because a Bot is working or the member is using Grok

141Bot, is never terminated by this setting.

142 

99## Related pages143## Related pages

100 144 

101* [Grok Bot for teams and enterprises](/grok-bot/teams-and-enterprises)145* [Grok Bot for teams and enterprises](/grok-bot/teams-and-enterprises)

102* [Grok Bot security](/grok-bot/security)146* [Grok Bot security](/grok-bot/security)

103* [Connect to private networks](/grok-bot/private-networks)147* [Connect to private networks](/grok-bot/private-networks)

104* [Update, recover, or reset the computer](/grok-bot/computer-and-apps#update-recover-or-reset-the-computer)148* [Update, recover, or reset the computer](/grok-bot/computer-and-apps#update-recover-or-reset-the-computer)

149* [Grok Bot computer](https://cursor.com/help/grok-bot/computer-recovery)

39provision the user, then have them sign in to Cursor for a seat or invite them39provision the user, then have them sign in to Cursor for a seat or invite them

40from the [Cursor dashboard](https://cursor.com/dashboard).40from the [Cursor dashboard](https://cursor.com/dashboard).

41 41 

42If you use [SCIM](https://cursor.com/docs/account/teams/scim), provisioning is42**SCIM is Enterprise only.** If you use

43SCIM 2.0, available on the Enterprise plan, and deprovisioning is automatic:43[SCIM](https://cursor.com/docs/account/teams/scim), provisioning is SCIM 2.0,

44removing the user in your identity provider removes them from Cursor.44and deprovisioning is automatic: removing the user in your identity provider

45removes them from Cursor.

45 46 

46## Assign the Cursor app47## Assign the Cursor app

47 48 

13services stay off the public internet, and access is governed by the access13services stay off the public internet, and access is governed by the access

14controls and identity provider you already use.14controls and identity provider you already use.

15 15 

16> Team Setup is Enterprise only. It does not appear on other plans. Network16> **Team Setup is Enterprise only.** It does not appear on other plans.

17> Controls is also Enterprise only. That17> **Network Controls is also Enterprise only.** That

18> [network policy](/grok-bot/security#network-policy) is a separate layer that18> [network policy](/grok-bot/security#network-policy) is a separate layer that

19> still applies; private network reach does not replace your destination19> still applies; private network reach does not replace your destination

20> allowlist.20> allowlist.

62 62 

63## Before you start63## Before you start

64 64 

65* You are a team admin on the Enterprise plan. Team Setup does not appear on other65* You are a team admin on the Enterprise plan. **Team Setup is Enterprise

66 plans.66 only** and does not appear on other plans.

67* Your networking client runs on Debian-based Linux and can be installed and67* Your networking client runs on Debian-based Linux and can be installed and

68 started from a shell script. Team computers run Linux, and scripts run as the68 started from a shell script. Team computers run Linux, and scripts run as the

69 computer user with `sudo` available.69 computer user with `sudo` available.

71 connector inside the VPC or intranet you want to reach, per your vendor's71 connector inside the VPC or intranet you want to reach, per your vendor's

72 architecture.72 architecture.

73* You have decided how computers will authenticate to your network. Keep73* You have decided how computers will authenticate to your network. Keep

74 credentials out of setup scripts.74 credentials out of setup scripts; if a script needs one, store it as a

75 [Team Secret](/grok-bot/teams-and-enterprises#team-secrets).

75 76 

76## How Team Setup runs your scripts77## How Team Setup runs your scripts

77 78 

79[Cursor dashboard](https://cursor.com/dashboard/bot): manifests of install80[Cursor dashboard](https://cursor.com/dashboard/bot): manifests of install

80scripts that run on every team computer. Each manifest holds one or more script81scripts that run on every team computer. Each manifest holds one or more script

81entries, and each entry has an **ID**, a **Setup Script**, and an optional82entries, and each entry has an **ID**, a **Setup Script**, and an optional

82**Check Script**.83**Check Script**. To run a manifest on one cohort's computers only, add it under

84the group's Grok Bot tab instead; see

85[Group settings](/grok-bot/teams-and-enterprises#group-settings). Group

86manifests follow the same rules as the ones below.

83 87 

84* Scripts run as the computer user on every team computer; use `sudo` for88* Scripts run as the computer user on every team computer; use `sudo` for

85 privileged installs.89 privileged installs.

90 to verify it succeeded.94 to verify it succeeded.

91* Entries run one at a time, in order. Each script has a 30-minute timeout. A95* Entries run one at a time, in order. Each script has a 30-minute timeout. A

92 failed script does not block the computer; it is retried on a later refresh.96 failed script does not block the computer; it is retried on a later refresh.

97* Scripts read your team's

98 [Team Secrets](/grok-bot/teams-and-enterprises#team-secrets) as environment

99 variables, so a credential a script needs never appears in the manifest.

100 Secrets are present only while the script runs, and script output is redacted

101 before it is logged. A computer whose setup comes from more than one team

102 receives no secrets.

93 103 

94## Create the manifest104## Create the manifest

95 105 

121}131}

122```132```

123 133 

124> Do not include secrets. Setup scripts run as the computer user on every team134> Do not paste secret values into scripts. Setup scripts run as the computer

125> computer, and manifests are plain text applied to your whole fleet. Do not135> user on every team computer, and manifests are plain text applied to your

126> embed auth keys, tokens, or other credentials. Have members authenticate136> whole fleet. If a script needs an auth key, token, or other credential, store

127> interactively in the computer's browser, where your identity provider's137> it as a [Team Secret](/grok-bot/teams-and-enterprises#team-secrets) and read

128> policies apply, or use a mechanism from your vendor's documentation that keeps138> it from the environment, for example `"$MY_AUTH_KEY"`. Where your vendor

129> long-lived credentials out of the script.139> supports it, prefer having members authenticate interactively in the

140> computer's browser, where your identity provider's policies apply.

130 141 

131## Set up your networking client142## Set up your networking client

132 143 

159**Connect and verify:**170**Connect and verify:**

160 171 

1611. Authenticate each computer. Tailscale prints a login URL that opens in the1721. Authenticate each computer. Tailscale prints a login URL that opens in the

162 computer's browser, where your identity provider's policies apply. Keep auth173 computer's browser, where your identity provider's policies apply. If you

163 keys out of the script.174 would rather join computers without a member signing in, store a reusable,

175 tagged [auth key](https://tailscale.com/docs/concepts/auth-keys) as a

176 [Team Secret](/grok-bot/teams-and-enterprises#team-secrets) and pass it from

177 the environment, for example `tailscale up --auth-key "$TS_AUTHKEY"`. Every

178 team computer then joins under the same key and tags rather than under the

179 member's identity, so scope the key's ACLs accordingly. Never paste the key

180 into the script itself.

1642. Confirm the computer appears in your Tailscale admin console and is allowed1812. Confirm the computer appears in your Tailscale admin console and is allowed

165 to use the exit node.182 to use the exit node.

1663. Ask a Bot to reach an internal hostname.1833. Ask a Bot to reach an internal hostname.

167 184 

168**If it does not work:**185**If it does not work:**

169 186 

170* The client installed but nobody authenticated. The login step is deliberately187* The client installed but nobody authenticated. With browser login, the step

171 manual, since scripts cannot hold secrets. Check the machine list in your188 is manual; with an auth key, check that the Team Secret exists, that its name

172 Tailscale admin console.189 matches what the script reads, and that the key has not expired. Check the

190 machine list in your Tailscale admin console.

173* Your team's network policy is allowlist-only and blocks Tailscale's191* Your team's network policy is allowlist-only and blocks Tailscale's

174 coordination servers or relays. Allow the endpoints from Tailscale's docs.192 coordination servers or relays. Allow the endpoints from Tailscale's docs.

175 Running computers apply the change within about a minute. Sleeping computers193 Running computers apply the change within about a minute. Sleeping computers

191**Before you start:** you run a Cloudflare Tunnel connector inside your private209**Before you start:** you run a Cloudflare Tunnel connector inside your private

192network, with the services you need routed through it, and you have chosen your210network, with the services you need routed through it, and you have chosen your

193Cloudflare Access policy. Identity-based policies fit this pattern well, since211Cloudflare Access policy. Identity-based policies fit this pattern well, since

194members sign in through the browser. Access service tokens are secrets; keep212members sign in through the browser. Access service tokens are secrets; if you

195them out of setup scripts.213use them, store them as

214[Team Secrets](/grok-bot/teams-and-enterprises#team-secrets) rather than in

215setup scripts.

196 216 

197**Team Setup manifest:**217**Team Setup manifest:**

198 218 

222 Cloudflare's endpoints. Allow them. Running computers apply the change within242 Cloudflare's endpoints. Allow them. Running computers apply the change within

223 about a minute. Sleeping computers apply it when they next wake.243 about a minute. Sleeping computers apply it when they next wake.

224* A service token was embedded in the setup script. Do not do this; manifests are244* A service token was embedded in the setup script. Do not do this; manifests are

225 plain text. Use identity-based Access, or supply tokens at use time.245 plain text. Use identity-based Access, or store the token as a Team Secret and

246 have the script read it from the environment.

226* A `cloudflared access tcp` listener is not running when the Bot needs it.247* A `cloudflared access tcp` listener is not running when the Bot needs it.

227 Listeners do not persist across sessions; start one when needed.248 Listeners do not persist across sessions; start one when needed.

228 249 

280 301 

281### Can I put an auth key or credential in the setup script?302### Can I put an auth key or credential in the setup script?

282 303 

283No. Setup scripts are not a secret store, and the dashboard warns against304Not in the script text. Manifests are plain text, and the dashboard warns

284including secrets. Authenticate computers interactively, or use a mechanism from305against pasting secrets into them. Store the credential as a

285your vendor's docs that does not require embedding a long-lived credential in the306[Team Secret](/grok-bot/teams-and-enterprises#team-secrets) on the Grok Bot page

286script.307and have the script read it as an environment variable. Team Secrets are

308Enterprise only. Where your vendor supports it, interactive browser login is

309still the simplest option, since your identity provider's policies apply to it.

287 310 

288### Which networking tools can I use?311### Which networking tools can I use?

289 312 

318 341 

319### Which plans include Team Setup?342### Which plans include Team Setup?

320 343 

321Team Setup is Enterprise only. Team admins manage manifests. If you do not see344**Team Setup is Enterprise only.** Team admins manage manifests. If you do not

322it on the Grok Bot page of the dashboard, you are not on Enterprise, or you345see it on the Grok Bot page of the dashboard, you are not on Enterprise, or you

323need your account team to enable Grok Bot for the organization.346need your account team to enable Grok Bot for the organization.

324 347 

325### What happens if the setup script fails on some computers?348### What happens if the setup script fails on some computers?

9common review questions are on the9common review questions are on the

10[Grok Bot security FAQ](/grok-bot/security-faq).10[Grok Bot security FAQ](/grok-bot/security-faq).

11 11 

12> Enterprise only on the Grok Bot dashboard: the organization-wide enable12> **Enterprise only** on the Grok Bot dashboard: the organization-wide enable

13> switch, Network Controls, Team Setup, Action Recording, Allow Local Egress,13> switch, **Network Controls**, **Team Setup**,

14> Enforce Auto-review with its team rules, and computer management for14> [**Team Secrets**](/grok-bot/teams-and-enterprises#team-secrets),

15> organization admins. Audit logs, OpenTelemetry Export, the MCP allowlist, and15> **Action Recording**, **Allow Local Egress**, **Enforce Auto-review** with

16> SCIM are also Enterprise only. Self-serve Teams do not see those settings.16> its team rules, and computer management for organization admins. Audit logs,

17> The full list is under17> OpenTelemetry Export, the MCP allowlist, and SCIM are also Enterprise only.

18> Self-serve Teams do not see those settings. The full list is under

18> [admin controls](/grok-bot/teams-and-enterprises#admin-controls).19> [admin controls](/grok-bot/teams-and-enterprises#admin-controls).

19 20 

20## Network policy21## Network policy

21 22 

22Network Controls is Enterprise only. Admins set a Grok Bot network policy from23**Network Controls is Enterprise only.** Admins set a Grok Bot network policy

23the Grok Bot page of the [Cursor dashboard](https://cursor.com/dashboard/bot),24from the [Grok Bot page](https://cursor.com/dashboard/bot) of the Cursor

24under **Network** as **Grok Bot Network Access**.25dashboard. It controls which destinations team computers can reach. Self-serve

25It controls which destinations team computers can reach. Self-serve Teams do26Teams do not see this panel and cannot set a destination allowlist. Teams

26not see this panel and cannot set a destination allowlist. Teams without a27without a policy default to allow-all.

27policy default to allow-all.

28 28 

29| Mode | Effect |29| Mode | Effect |

30| --- | --- |30| --- | --- |

33| **Defaults + Team Allowlist** | Cursor's default destinations plus your list |33| **Defaults + Team Allowlist** | Cursor's default destinations plus your list |

34| **Team Allowlist Only** | Only your list, plus the destinations a computer needs to function |34| **Team Allowlist Only** | Only your list, plus the destinations a computer needs to function |

35 35 

36* Destinations cover web domains as well as IP ranges with ports for raw36* **Destinations** cover web domains as well as IP ranges with ports for raw

37 connections, with no cap on the number of entries.37 connections, with no cap on the number of entries.

38* Directory groups are Enterprise only, inside Network Controls. Groups can set38* **Directory groups. Enterprise only, inside Network Controls.** Groups can

39 their own network policy, which replaces the team's for their members, and a39 set their own network policy, which replaces the team's for their members,

40 lock makes the team policy effective for everyone.40 and a lock makes the team policy effective for everyone.

41* The policy is separate from Cloud Agent network settings. Running computers41* **The policy is separate from Cloud Agent network settings.** Running

42 apply changes automatically within about a minute. Sleeping computers apply42 computers apply changes automatically within about a minute. Sleeping

43 changes when they next wake. You do not need to recreate the computer.43 computers apply changes when they next wake. You do not need to recreate the

44* Restricting egress limits where data can be sent. Dedicated data loss44 computer.

45* **Restricting egress limits where data can be sent.** Dedicated data loss

45 prevention hooks are not available.46 prevention hooks are not available.

46 47 

47Blocking a plugin does not block that service's website. The48Blocking a plugin does not block that service's website. The

48[connector policy](/grok-bot/teams-and-enterprises#admin-controls) and the49[connector policy](/grok-bot/teams-and-enterprises#connector-policy) and the

49network policy are separate layers, and closing both paths takes both controls.50network policy are separate layers, and closing both paths takes both controls.

50 51 

51## Static egress IPs52## Static egress IPs

52 53 

53Hosted computers reach the internet through shared static egress IP addresses54Hosted computers reach the internet through shared static egress IP addresses

54by default. The ranges are shared across Grok Bot customers, and dedicated per-customer IPs55by default. The ranges are shared across Grok Bot customers, and dedicated

55are not available, so treat the ranges as identifying Grok Bot traffic rather56per-customer IPs are not available, so treat the ranges as identifying Grok Bot

56than your team alone. Current ranges are available from your account team, and57traffic rather than your team alone. Current ranges are available from your

57the product control is the destination allowlist rather than a source IP58account team, and the product control is the destination allowlist rather than

58editor.59a source IP editor.

59 60 

60If member devices sit behind Zscaler or another TLS-inspecting gateway, allow61If member devices sit behind Zscaler or another TLS-inspecting gateway, allow

61Cursor's domains and exempt them from inspection on every profile, including62Cursor's domains and exempt them from inspection on every profile, including

62off-network. See [Configure TLS-inspecting proxies](/grok-bot/proxies).63off-network. See [Configure TLS-inspecting proxies](/grok-bot/proxies).

63 64 

64Members can route traffic through their desktop to use its network and IP65Members can route traffic through their desktop to use its network and IP

65address. Team Setup is Enterprise only. Those teams can also install their own66address. **Team Setup is Enterprise only.** Those teams can also install their

66networking client on every team computer. Both paths are separate from the67own networking client on every team computer. Both paths are separate from the

67shared egress ranges. See68shared egress ranges. See

68[Connect to private networks](/grok-bot/private-networks).69[Connect to private networks](/grok-bot/private-networks).

69 70 

79 80 

80When an action needs approval, the conversation shows the proposed operation81When an action needs approval, the conversation shows the proposed operation

81and its inputs. **Allow once** lets the Bot continue with that action,82and its inputs. **Allow once** lets the Bot continue with that action,

82**Always allow** can save a matching rule, and **Deny** blocks it (on iPhone83**Always allow** can save a matching rule, and **Deny** blocks it. The controls

83and Android, the Auto-review sheet offers **Allow**, **Deny**, and, when a rule84are the same on iPhone. An approval controls the proposed action, not

84is proposed, **Always allow**). An approval85work already completed, and nobody should approve an action whose target or

85controls the proposed action, not work already completed, and nobody should86effect they cannot identify.

86approve an action whose target or effect they cannot identify.

87 87 

88Auto Review is the review layer behind those prompts: an independent review88Auto Review is the review layer behind those prompts: an independent review

89model that evaluates risky Bot actions before they run, covering shell89model that evaluates risky Bot actions before they run, covering shell

91and event triggers), and delegation such as Cloud Agent and subagent launches.91and event triggers), and delegation such as Cloud Agent and subagent launches.

92It can let an action proceed, require approval, or deny it.92It can let an action proceed, require approval, or deny it.

93 93 

94* Team admins can enforce Auto-review. Enterprise only. The switch lives on94* **Team admins can enforce Auto-review. Enterprise only.** The switch lives

95 the Grok Bot page of the Cursor dashboard. When it is on, members cannot95 on the Grok Bot page of the Cursor dashboard. When it is on, members cannot

96 turn Auto-review off. See96 turn Auto-review off, unless a group they belong to lifts the lock with

97 [Enforce Auto-review](/grok-bot/teams-and-enterprises#enforce-auto-review).97 **Don't enforce for this group**; see

98* Admins can add team Auto-review rules. Enterprise only. These live on the98 [Enforce Auto-review](/grok-bot/teams-and-enterprises#enforce-auto-review)

99 Grok Bot page too. They apply to every member's Bots, show up as locked rows99 and [Group settings](/grok-bot/teams-and-enterprises#group-settings).

100 in the member settings table, and save automatically when an admin adds,100* **Admins can add team Auto-review rules. Enterprise only.** These live on

101 edits, or deletes a rule. If admins turn enforcement off, the team rules stop101 the Grok Bot page too. They apply to every member's Bots, show up as locked

102 applying and members go back to their own rules only. See102 rows in the member settings table, and save automatically when an admin

103 adds, edits, or deletes a rule. If admins turn enforcement off, the team

104 rules stop applying and members go back to their own rules only. See

103 [Auto-review rules](/grok-bot/teams-and-enterprises#auto-review-rules).105 [Auto-review rules](/grok-bot/teams-and-enterprises#auto-review-rules).

104* Members can add personal rules under **Settings → General → Bot →106* **Members can add personal rules** under **Settings → General →

105 Auto-review**. **Ask first** rules always stop matching actions, and **Allow107 Auto-review**. **Ask first** rules always stop matching actions, and

106 automatically** rules let matching actions proceed only when the reviewer108 **Allow automatically** rules let matching actions proceed only when the

107 finds no other reason to stop. Personal rules sit on top of team rules but109 reviewer finds no other reason to stop. Members can add personal rules on

108 only make behavior stricter; **Ask first** wins when rules conflict. Narrow110 top of team rules, but they only make behavior stricter; **Ask first** wins

109 rules around a known action and scope work best, like "ask first before111 when rules conflict. Keep rules narrow and tied to a known action, like "ask

110 sending any external email" or "allow automatically when running112 first before sending any external email" or "allow automatically when

111 `git status` in `/workspace/reports`"; avoid broad rules like "allow113 running `git status` in `/workspace/reports`". Avoid broad rules like "allow

112 everything in the browser". Personal rules are saved to the member's account114 everything in the browser". Personal rules are stored on the current desktop

113 and applied on every desktop they sign in to.115 and synced to its Grok Bot computer, so another desktop installation needs

114* It does not review every side effect; memory writes and most settings changes116 its own.

115 are examples. Treat it as a complement to explicit boundaries and least117* **It does not review every side effect.** Memory writes and most settings

116 privilege, working alongside controls that do not depend on a model's118 changes are examples. Treat it as a complement to explicit boundaries and

119 least privilege, working alongside controls that do not depend on a model's

117 judgment: per-action approvals, the network policy, and per-user isolation.120 judgment: per-action approvals, the network policy, and per-user isolation.

118 121 

119For the member-facing walkthrough of these prompts and rules, see122For the member-facing walkthrough of these prompts and rules, see

124Members sign in to Grok Bot with their Cursor account, so your existing Cursor127Members sign in to Grok Bot with their Cursor account, so your existing Cursor

125SSO configuration applies. SAML 2.0 single sign-on works with Okta, Microsoft128SSO configuration applies. SAML 2.0 single sign-on works with Okta, Microsoft

126Entra, Google Workspace, and OneLogin, and SSO can be required for all members129Entra, Google Workspace, and OneLogin, and SSO can be required for all members

127(which blocks password login). SCIM is Enterprise only: SCIM 2.0 provisioning130(which blocks password login). **SCIM is Enterprise only:** SCIM 2.0

128and deprovisioning. For step-by-step Okta and Entra ID configuration, including131provisioning and deprovisioning. For step-by-step Okta and Entra ID

129app assignment and sign-in rules for the computer browser, see132configuration, including app assignment and sign-in rules for the computer

130[Configure identity and access](/grok-bot/identity-and-access).133browser, see [Configure identity and access](/grok-bot/identity-and-access).

131 134 

132Inside the hosted computer, members sign in to applications through your own135Inside the hosted computer, members sign in to applications through your own

133identity provider in the browser, comparable to enrolling a new laptop. Your136identity provider in the browser, comparable to enrolling a new laptop. Your

136 139 

137A Bot has no identity or credentials of its own:140A Bot has no identity or credentials of its own:

138 141 

139* Bots act as the signed-in member. A Bot can never hold more access than the142* **Bots act as the signed-in member.** A Bot can never hold more access than

140 person it belongs to, every action stays attributable to a named member, and143 the person it belongs to, every action stays attributable to a named member,

141 there is no separate machine identity outside your identity provider to144 and there is no separate machine identity outside your identity provider to

142 provision, rotate, or audit. Team-managed connectors are the one exception:145 provision, rotate, or audit. Team-managed connectors are the one exception:

143 they may use team or service-account credentials.146 they may use team or service-account credentials.

144* Connector tokens stay on Cursor's backend. Bots invoke tools without147* **Connector tokens stay on Cursor's backend.** Bots invoke tools without

145 receiving OAuth tokens, and tokens are never stored on the computer.148 receiving OAuth tokens, and tokens are never stored on the computer.

146* Credentials stay with the member. For login, two-factor, and payment steps,149* **Credentials stay with the member.** For login, two-factor, and payment

147 the Bot hands the computer to the member rather than typing credentials. For150 steps, the Bot hands the computer to the member rather than typing

148 supported connections, a secure secret request masks the entered value and151 credentials. For supported connections, a secure secret request masks the

149 keeps it out of the transcript and away from the model; passwords and152 entered value and keeps it out of the transcript and away from the model;

150 one-time codes never belong in ordinary chat. See153 passwords and one-time codes never belong in ordinary chat. See

154 [Store secrets securely](https://cursor.com/help/grok-bot/secrets) and

151 [Enter passwords and verification codes yourself](/grok-bot/approvals-security-and-privacy#enter-passwords-and-verification-codes-yourself).155 [Enter passwords and verification codes yourself](/grok-bot/approvals-security-and-privacy#enter-passwords-and-verification-codes-yourself).

152 156 

153To end a member's current work, an organization admin terminates the member's157To end a member's current work, an organization admin terminates the member's

172Action Recording captures Bot actions, and OpenTelemetry Export sends those176Action Recording captures Bot actions, and OpenTelemetry Export sends those

173events to your collector when configured, tagged `cursor.surface=grok_bot`.177events to your collector when configured, tagged `cursor.surface=grok_bot`.

174 178 

175* Audit logs are Enterprise only. They cover admin, security, and179* **Audit logs. Enterprise only.** They cover admin, security, and

176 authentication events, plus Grok Bot control-plane events: Bot creation,180 authentication events, plus Grok Bot control-plane events: Bot creation,

177 member access changes, Team Setup manifests, MCP authentication, Slack181 member access changes, Team Setup manifests, MCP authentication, Slack

178 account links, and routines. Filter them by application in the dashboard, or182 account links, and routines. Filter them by application in the dashboard, or

179 stream them to your SIEM. Self-serve Teams do not get this log.183 stream them to your SIEM. Self-serve Teams do not get this log.

180* Action Recording is Enterprise only. It is a setting on the Grok Bot page,184* **Action Recording. Enterprise only.** It is a setting on the Grok Bot page,

181 off by default. When a team enables it, Cursor records Bot actions, including185 off by default. When a team enables it, Cursor records Bot actions, including

182 scrubbed shell commands, in an internal store with a 90-day retention. Action186 scrubbed shell commands, in an internal store with a 90-day retention. Action

183 Recording events do not appear on the Audit Log page. To receive the187 Recording events do not appear on the Audit Log page. To receive the

184 sanitized events in your own collector, configure188 sanitized events in your own collector, configure

185 [OpenTelemetry Export](https://cursor.com/docs/enterprise/opentelemetry-export),189 [OpenTelemetry Export](https://cursor.com/docs/enterprise/opentelemetry-export),

186 which is also Enterprise only. Privacy Mode (Legacy) forces recording off.190 which is also Enterprise only. Exported records may include the member's

191 email; it is not exported for teams on Privacy Mode (Legacy), which also

192 forces recording off.

193* **Conversation content export. Enterprise only, opt-in.** OpenTelemetry

194 Export can also send the text of user prompts and assistant responses, and

195 the arguments and results of hosted MCP tool calls. It is off until an admin

196 allows it for the team and turns it on for the destination. Known credential

197 shapes, PEM blocks, and email addresses are redacted before export, but

198 pattern matching cannot catch every secret. See

199 [Conversation content export](/grok-bot/teams-and-enterprises#logging-and-audit).

187 200 

188## Endpoint tooling201## Endpoint tooling

189 202 

190Grok Bot does not ship a built-in customer-facing telemetry or EDR feed. The203Grok Bot does not ship a built-in customer-facing telemetry or EDR feed. The

191computers are Cursor-operated infrastructure that Cursor monitors for204computers are Cursor-operated infrastructure that Cursor monitors for

192operational health and abuse, and that telemetry deliberately excludes customer205operational health and abuse, and that telemetry deliberately excludes customer

193data. Team Setup is Enterprise only; those admins can install their own tooling206data. **Team Setup is Enterprise only.** Those admins can install their own

194on every team computer.207tooling on every team computer.

195 208 

196## Data retention and deletion209## Data retention and deletion

197 210 

199in the browser on a durable disk across sessions. Connector tokens are never212in the browser on a durable disk across sessions. Connector tokens are never

200stored on the computer.213stored on the computer.

201 214 

202* Idle computers hibernate automatically; hibernation is not deletion.215* **Idle computers hibernate automatically.** Hibernation is not deletion.

203* Image updates preserve files: computers on a stale system image are recreated216* **Image updates preserve files.** Computers on a stale system image are

204 on the fresh image with member files preserved.217 recreated on the fresh image with member files preserved.

205* Member resets keep synced data. Members can reset their own computer from the218* **Member resets keep synced data.** Members can reset their own computer

206 desktop app. Reset keeps the synced durable data, and recent unsynced work219 from the desktop app. Reset keeps the synced durable data, and recent

207 can be lost. See220 unsynced work can be lost. See

208 [Update, recover, or reset the computer](/grok-bot/computer-and-apps#update-recover-or-reset-the-computer).221 [Update, recover, or reset the computer](/grok-bot/computer-and-apps#update-recover-or-reset-the-computer).

209* Deletion follows the DPA. Under the222* **Deletion follows the DPA.** Under the

210 [Data Processing Agreement](https://cursor.com/terms/dpa), data is deleted or223 [Data Processing Agreement](https://cursor.com/terms/dpa), data is deleted or

211 returned within 30 days of written direction after the service ends.224 returned within 30 days of written direction after the service ends.

212* Backups run daily. Cursor's production control plane is covered by daily225* **Backups run daily.** Cursor's production control plane is covered by daily

213 encrypted backups, replicated to a separate recovery facility.226 encrypted backups, replicated to a separate recovery facility.

214 227 

215A per-organization retention policy and customer-managed point-in-time restore228A per-organization retention policy and customer-managed point-in-time restore

230analytics show the model that served each request, including failovers, and243analytics show the model that served each request, including failovers, and

231billing follows the serving model.244billing follows the serving model.

232 245 

233* The team model allowlist is Enterprise only, and enforcement is not246* **The team model allowlist is Enterprise only, and enforcement is not

234 guaranteed. The list is honored by default, and onboarding presents an247 guaranteed.** The list is honored by default. Onboarding presents an

235 acknowledgement that Grok Bot may not follow it, so treat enforcement as248 acknowledgement that Grok Bot may not follow it, so treat enforcement as

236 configuration dependent. See249 configuration dependent. See

237 [model access control](https://cursor.com/docs/enterprise/model-and-integration-management#model-access-control).250 [model access control](https://cursor.com/docs/enterprise/model-and-integration-management#model-access-control).

238* Privacy Mode applies. While a member is on your team, the team's privacy mode251* **Privacy Mode applies.** While a member is on your team, the team's privacy

239 governs them, and with Privacy Mode enabled, customer data is not used for252 mode governs them, and with Privacy Mode enabled, customer data is not used

240 training.253 for training.

241* Zero Data Retention follows Cursor's existing provider agreements. Model254* **Zero Data Retention follows Cursor's existing provider agreements.** Model

242 providers do not keep prompts or outputs, and Grok Bot adds no separate255 providers do not keep prompts or outputs, and Grok Bot adds no separate

243 control. Providers may run abuse and safety classifiers, and flagged data256 control. Providers may run abuse and safety classifiers, and flagged data

244 may be stored for investigation.257 may be stored for investigation.

28### If we block a plugin, can a Bot still reach that service in the browser?28### If we block a plugin, can a Bot still reach that service in the browser?

29 29 

30Yes. Blocking a plugin does not block that service's website. The30Yes. Blocking a plugin does not block that service's website. The

31[connector policy](/grok-bot/teams-and-enterprises#admin-controls) and the31[connector policy](/grok-bot/teams-and-enterprises#connector-policy) and the

32[network policy](/grok-bot/security#network-policy) are separate layers.32[network policy](/grok-bot/security#network-policy) are separate layers.

33Closing the website path takes Network Controls, which is Enterprise only.33Closing the website path takes **Network Controls**, which is Enterprise only.

34 34 

35### Can admins push connectors to members?35### Can admins push connectors to members?

36 36 

41 41 

42### Can we restrict which destinations computers can reach?42### Can we restrict which destinations computers can reach?

43 43 

44Network Controls is Enterprise only. Admins set a Grok Bot network policy from44**Network Controls is Enterprise only.** Admins set a Grok Bot network policy

45that panel on the Grok Bot page of the dashboard. Self-serve Teams do not see45from that panel on the Grok Bot page of the dashboard. Self-serve Teams do not

46it and cannot set a destination allowlist, and teams without a policy default46see it and cannot set a destination allowlist, and teams without a policy

47to allow-all. See [network policy](/grok-bot/security#network-policy).47default to allow-all. See [network policy](/grok-bot/security#network-policy).

48 48 

49### Do admin controls apply per group, or only org-wide?49### Do admin controls apply per group, or only org-wide?

50 50 

51Directory-group scope is part of Network Controls, which is Enterprise only.51Directory-group scope is part of **Network Controls**, which is Enterprise

52Groups can set their own policy, and a lock makes the team policy effective for52only. Groups can set their own policy, and a lock makes the team policy

53everyone. The organization-wide enable switch is also Enterprise only and53effective for everyone. The organization-wide enable switch is also Enterprise

54applies to the whole organization. Cloud Agents, Team Rules, and public54only and applies to the whole organization. Cloud Agents, Team Rules, and

55template sharing apply to the whole team on Teams and Enterprise. Enforce55public template sharing apply to the whole team on Teams and Enterprise.

56Auto-review and Auto-review rules are Enterprise only and also apply to the56Enforce Auto-review and Auto-review rules are Enterprise only and also apply

57whole team. Allow Local Egress is Enterprise only and applies to the whole57to the whole team. Allow Local Egress is Enterprise only and applies to the

58team.58whole team. On Enterprise, a group's Grok Bot tab can widen Cloud Agents, local

59execution, local egress, Auto-review, rules, and setup scripts for that group's

60members, never tighten them. See

61[Group settings](/grok-bot/teams-and-enterprises#group-settings).

59 62 

60### Why do some websites block Bots?63### Why do some websites block Bots?

61 64 

73 76 

74Yes. A member can route a Grok Bot computer's web traffic through their77Yes. A member can route a Grok Bot computer's web traffic through their

75desktop, using its network and IP address. Enterprise teams can also install a78desktop, using its network and IP address. Enterprise teams can also install a

76networking client on every hosted computer through Team Setup. See79networking client on every hosted computer through **Team Setup**. See

77[Connect to private networks](/grok-bot/private-networks).80[Connect to private networks](/grok-bot/private-networks).

78 81 

79### Grok Bot hangs at computer setup from our network. Why?82### Grok Bot hangs at computer setup from our network. Why?

101 104 

102### Can I see what Bots did on behalf of my team?105### Can I see what Bots did on behalf of my team?

103 106 

104Spend and usage are on the dashboard usage page, broken down by product. Audit107Spend and usage are on the dashboard usage page, broken down by product.

105logs are Enterprise only; they cover admin, security, and authentication108**Audit logs are Enterprise only.** They cover admin, security, and

106events, plus Grok Bot control-plane events like Bot creation, access changes,109authentication events, plus Grok Bot control-plane events like Bot creation,

107Team Setup, and routines, filterable by application, and can stream to your110access changes, Team Setup, and routines, filterable by application, and can

108SIEM. Action Recording is Enterprise only and is a separate setting, off by111stream to your SIEM. **Action Recording is Enterprise only** and is a separate

109default; when enabled, it records Bot actions internally. OpenTelemetry Export112setting, off by default. When enabled, it records Bot actions internally.

110is Enterprise only; configure it to receive those events in your own113**OpenTelemetry Export is Enterprise only.** Configure it to receive those

111collector, tagged `cursor.surface=grok_bot`. They do not appear on the Audit114events in your own collector, tagged `cursor.surface=grok_bot`. They do not

112Log page.115appear on the Audit Log page. To also receive user prompts, assistant

116responses, and the arguments and results of hosted MCP tool calls, opt in to

117[conversation content export](/grok-bot/teams-and-enterprises#logging-and-audit).

113See [logging and audit](/grok-bot/security#logging-and-audit).118See [logging and audit](/grok-bot/security#logging-and-audit).

114 119 

115### Can I restrict which models Grok Bot uses?120### Can I restrict which models Grok Bot uses?

122 127 

123### Where do Grok Bot computers run?128### Where do Grok Bot computers run?

124 129 

125In the United States today. That is not the same as Cursor's US-only data130In the United States today. That is not the same as Cursor's

126residency program, which does not apply to Grok Bot by default. If your review131[US-only data residency](https://cursor.com/docs/enterprise/privacy-and-data-governance#data-residency)

127needs a written residency commitment, contact your account team. See132program, which does not apply to Grok Bot by default. If your review needs a

133written residency commitment, contact your account team. See

128[data residency](/grok-bot/security#data-residency).134[data residency](/grok-bot/security#data-residency).

129 135 

130### Can we run Grok Bot on-premises or from our own image?136### Can we run Grok Bot on-premises or from our own image?

135 141 

136### Can we install our own security tooling on team computers?142### Can we install our own security tooling on team computers?

137 143 

138Team Setup is Enterprise only. Those admins can install their own tooling on144**Team Setup is Enterprise only.** Those admins can install their own tooling

139every team computer. Grok Bot does not ship a built-in customer-facing EDR145on every team computer. Grok Bot does not ship a built-in customer-facing EDR

140feed. See [endpoint tooling](/grok-bot/security#endpoint-tooling).146feed. See [endpoint tooling](/grok-bot/security#endpoint-tooling).

141 147 

142### Why do members have to sign in to company tools again?148### Why do members have to sign in to company tools again?

59rules with `Required by your admin. You can't edit or delete this rule.` You59rules with `Required by your admin. You can't edit or delete this rule.` You

60can add your own rules on top, but they only make behavior stricter; **Ask60can add your own rules on top, but they only make behavior stricter; **Ask

61first** wins when rules conflict. If your admin turns enforcement off, you only61first** wins when rules conflict. If your admin turns enforcement off, you only

62see and use your own rules. Your personal rules are saved to your account and62see and use your own rules. Your personal rules are stored on the current

63apply on every desktop you sign in to. Read63desktop and synced to its Grok Bot computer, so another desktop installation

64needs its own. Read

64[Approvals, security, and privacy](/grok-bot/approvals-security-and-privacy)65[Approvals, security, and privacy](/grok-bot/approvals-security-and-privacy)

65before changing either.66before changing either.

66 67 

105For how plans, weekly usage, and on-demand spend work, see106For how plans, weekly usage, and on-demand spend work, see

106[Plans and billing](https://cursor.com/help/grok-bot/plans).107[Plans and billing](https://cursor.com/help/grok-bot/plans).

107 108 

109## Team Setup

110 

111Team Setup is Enterprise only. When an Enterprise admin provides a managed

112setup for your team's computers, **Team Setup** shows it here so you can review

113or reinstall it. Admins configure the manifests from the Cursor dashboard; see

114[Grok Bot for teams and enterprises](/grok-bot/teams-and-enterprises#admin-controls).

115 

108## Updates116## Updates

109 117 

110The update controls live in **Settings → Updates**. The Grok Bot app and Grok118The update controls live in **Settings → Updates**. The Grok Bot app and Grok

129* **Notifications** preference137* **Notifications** preference

130 138 

131These settings belong to one Bot. **Execution on Local Computer** is set per139These settings belong to one Bot. **Execution on Local Computer** is set per

132computer, and your Auto-review rules are saved to your account and apply on140computer, and your personal Auto-review rules are stored on each desktop.

133every desktop you sign in to.

134 141 

135## Understand attention states142## Understand attention states

136 143 

15| --- | --- |15| --- | --- |

16| Individuals | Included with every paid Cursor plan, or through an individual SuperGrok link |16| Individuals | Included with every paid Cursor plan, or through an individual SuperGrok link |

17| Teams | Included; every member has access, and usage follows the seat's allowance |17| Teams | Included; every member has access, and usage follows the seat's allowance |

18| Enterprise | Enable Grok Bot for your team from your dashboard |18| Enterprise | Enable Grok Bot for your team from [your dashboard](https://cursor.com/dashboard/bot) |

19 19 

20That table is product access, not the admin control list. Grok Bot is included20That table is product access, not the admin control list. Grok Bot is included

21on Teams. Several settings are Enterprise only and do not appear for21on Teams. Several settings are Enterprise only and do not appear for

27## Enabling Grok Bot for your team27## Enabling Grok Bot for your team

28 28 

29On the Teams plan, Grok Bot is enabled by default, and every member has access29On the Teams plan, Grok Bot is enabled by default, and every member has access

30without any admin action. It stays off for teams on Privacy Mode (Legacy) or on30without any admin action. It stays off for teams on

31a [legacy request-based plan](https://cursor.com/docs/models-and-pricing#legacy-request-based-pricing).31[Privacy Mode (Legacy)](#before-you-roll-out) or on a

32[legacy request-based plan](https://cursor.com/docs/models-and-pricing#legacy-request-based-pricing).

32There is no switch to turn it off.33There is no switch to turn it off.

33 34 

34On the Enterprise plan, an admin turns it on from35On the Enterprise plan, an admin turns it on from

35[Grok Bot in the Cursor dashboard](https://cursor.com/dashboard/bot). Once36[Grok Bot in the Cursor dashboard](https://cursor.com/dashboard/bot). Once

36enabled, you can give access to all team members or limit it to specific37enabled, you can give access to all team members or limit it to specific

37groups with **Manage Group Access**. Turning Grok Bot off blocks every member38[groups](https://cursor.com/dashboard/members?subtab=groups) with

38without deleting their computers.39**Manage Group Access**. Turning Grok Bot off blocks every member without

40deleting their computers.

39 41 

40Admins on either plan can bring members in with **Invite Team** on the Grok Bot42Admins on either plan can bring members in with **Invite Team** on the Grok Bot

41page. Existing Cursor users on your team get an email with a download link. New43page. Existing Cursor users on your team get an email with a download link. New

79 an independent review model called Auto Review.81 an independent review model called Auto Review.

80* Administrative control. Team admins can set Team Rules, Cloud Agent82* Administrative control. Team admins can set Team Rules, Cloud Agent

81 delegation, template sharing, and the local execution ceiling. Network83 delegation, template sharing, and the local execution ceiling. Network

82 Controls, Team Setup, Allow Local Egress, Action Recording, Enforce84 Controls, Team Setup, Team Secrets, Allow Local Egress, Action Recording,

83 Auto-review, Auto-review rules, and the organization-wide enable switch are85 Enforce Auto-review, Auto-review rules, and the organization-wide enable

84 Enterprise only.86 switch are Enterprise only.

85 87 

86The pieces fit together like this:88The pieces fit together like this:

87 89 

94 page of the [Cursor dashboard](https://cursor.com/dashboard/bot). Team96 page of the [Cursor dashboard](https://cursor.com/dashboard/bot). Team

95 Rules, Cloud Agent delegation, public template sharing, and Execution on97 Rules, Cloud Agent delegation, public template sharing, and Execution on

96 Local Computer are available to team admins. Enterprise only on that page:98 Local Computer are available to team admins. Enterprise only on that page:

97 the organization-wide enable switch, Network Controls, Team Setup, Allow99 the organization-wide enable switch, Network Controls, Team Setup, Team

98 Local Egress, Action Recording, Enforce Auto-review, Auto-review rules, and100 Secrets, Allow Local Egress, Action Recording, Enforce Auto-review,

99 computer management for organization admins. Members never see this page.101 Auto-review rules, and computer management for organization admins. Members

102 never see this page.

1003. The Bot. Shell, browser, and computer use inside the hosted computer. A Bot1033. The Bot. Shell, browser, and computer use inside the hosted computer. A Bot

101 has no access by default and acts only with accounts the member signs it104 has no access by default and acts only with accounts the member signs it

102 into. It hands login, two-factor authentication, and payment steps to the105 into. It hands login, two-factor authentication, and payment steps to the

129Most Grok Bot settings sit on the Grok Bot page of the132Most Grok Bot settings sit on the Grok Bot page of the

130[Cursor dashboard](https://cursor.com/dashboard/bot), which only admins see. A133[Cursor dashboard](https://cursor.com/dashboard/bot), which only admins see. A

131few live in Team Settings, your Team Marketplace, or your identity provider.134few live in Team Settings, your Team Marketplace, or your identity provider.

132Several controls are available only on the Enterprise plan; the rest are135Several controls are available only on the

133available on Teams and Enterprise.136[Enterprise plan](https://cursor.com/docs/enterprise); the rest are available

137on Teams and Enterprise. Enterprise teams can also widen several of these

138controls for one cohort from a group's Grok Bot tab; see

139[Group settings](#group-settings).

134 140 

135### Access and identity141### Access and identity

136 142 

138 144 

139#### Enable Grok Bot145#### Enable Grok Bot

140 146 

141The organization-wide switch on the Grok Bot page, labeled **Enable Grok Bot147The organization-wide switch on the Grok Bot page, with **Manage Group Access**

142for your team**, with **Manage Group Access** beside it. A team that has never148beside it. Turning it on opens a setup modal that covers privacy mode, pricing,

143set up Grok Bot sees a **Set Up Grok Bot** call to action with an **Open Docs**149and model availability. Turning it off blocks every member without deleting

144link instead; on Enterprise it opens a setup modal that covers privacy mode,150their computers. See

145pricing, and model availability. Turning the switch off opens a **Disable Grok

146Bot** confirmation and then blocks every member without deleting their

147computers. On the Teams plan the same card is a status line, **Grok Bot is

148enabled for your team**, with no switch. See

149[Enabling Grok Bot for your team](#enabling-grok-bot-for-your-team).151[Enabling Grok Bot for your team](#enabling-grok-bot-for-your-team).

150 152 

151Available on the Enterprise plan.153Available on the Enterprise plan.

168 170 

169#### Cloud Agents171#### Cloud Agents

170 172 

171Allows or blocks Bots delegating coding tasks to Cursor Cloud Agents. The173Allows or blocks Bots delegating coding tasks to Cursor

172switch is on the Grok Bot page, applies to the whole team, and is on by174[Cloud Agents](https://cursor.com/docs/cloud-agent). The switch is on the Grok

173default. Delegated work runs on separate computers under your existing175Bot page, applies to the whole team, and is on by default. Delegated work runs

174[Cloud Agent](https://cursor.com/docs/cloud-agent) controls. Turn it off when176on separate computers under your existing Cloud Agent controls. Turn it off

175your team does not need delegation.177when your team does not need delegation.

176 178 

177#### Public template sharing179#### Public template sharing

178 180 

187Grok Bot inherits your team's Cursor connector policy. There is no separate189Grok Bot inherits your team's Cursor connector policy. There is no separate

188Grok Bot connector list, and connectors appear as plugins in the app. Set which190Grok Bot connector list, and connectors appear as plugins in the app. Set which

189servers members can use from your Team Marketplace on the dashboard's191servers members can use from your Team Marketplace on the dashboard's

190[Plugins page](https://cursor.com/dashboard/plugins), not on the Grok Bot page.192[Plugins & MCPs page](https://cursor.com/dashboard/plugins), not on the Grok

191The MCP allowlist is Enterprise only; see193Bot page. The MCP allowlist is Enterprise only; see

192[MCP server trust management](https://cursor.com/docs/enterprise/model-and-integration-management#mcp-server-trust-management).194[MCP server trust management](https://cursor.com/docs/enterprise/model-and-integration-management#mcp-server-trust-management).

193Any permitted connector is available to every Bot a member runs, and a blocked195Any permitted connector is available to every Bot a member runs, and a blocked

194one shows as **Disabled by team admin**. Pushing connectors to members, whether196one shows as **Disabled by team admin**. Pushing connectors to members, whether

226scope each rule to Cursor, Grok Bot, or both. Rules applied to Grok Bot are228scope each rule to Cursor, Grok Bot, or both. Rules applied to Grok Bot are

227always required, so members cannot turn them off. Keep them short and few, like229always required, so members cannot turn them off. Keep them short and few, like

228"never move company data to personal accounts." Rules guide a Bot; for approval230"never move company data to personal accounts." Rules guide a Bot; for approval

229behavior, use [Auto-review rules](#auto-review-rules).231behavior, use [Auto-review rules](#auto-review-rules). For guidance that

232belongs to one cohort, add Group Rules under [Group settings](#group-settings).

230 233 

231#### Enforce Auto-review234#### Enforce Auto-review

232 235 

233Prevents members from turning Auto-review off. The switch is on the Grok Bot236Prevents members from turning Auto-review off. The switch is on the Grok Bot

234page and is off by default. When it is on, Bots always check risky actions237page and is off by default. When it is on, Bots always check risky actions

235before running them and ask for approval when needed. Turn it on before you238before running them and ask for approval when needed. Turn it on before you

236rely on team Auto-review rules.239rely on team Auto-review rules. A group can lift the lock for its own members

240with **Don't enforce for this group**; see [Group settings](#group-settings).

237 241 

238Available on the Enterprise plan.242Available on the Enterprise plan.

239 243 

271#### Team Setup275#### Team Setup

272 276 

273Manifests of install scripts that run on every team computer, so the same277Manifests of install scripts that run on every team computer, so the same

274tooling is present everywhere. Keep secret values out of setup scripts. Members278tooling is present everywhere. Keep secret values out of setup scripts; when a

275do not see or manage the setup in the app; scripts run on their computer when279script needs a credential, store it as a [Team Secret](#team-secrets) and read

276it starts and on a periodic refresh. For how manifests run, and to install a280it from the environment. Members see the managed setup under **Team Setup** in

277networking client that reaches private services, see281the app, where they can review or reinstall it. For how manifests run, and to

278[Connect to private networks](/grok-bot/private-networks).282install a networking client that reaches private services, see

283[Connect to private networks](/grok-bot/private-networks). To run extra

284scripts on one cohort's computers only, add them under

285[Group settings](#group-settings).

286 

287Available on the Enterprise plan.

288 

289#### Team Secrets

290 

291Team-wide values that Team Setup scripts read as environment variables, so a

292script can hold a license key, auth key, or service token without the value

293appearing in the manifest. Add them under **Team Secrets** on the Grok Bot

294page: each secret is an environment variable name and a value. Cursor stores

295the value encrypted, and the dashboard never shows it again after you save it.

296Team admins, including unpaid admins, can add, replace, or delete them.

297 

298How they reach the computer:

299 

300* Every Setup Script and Check Script in your Team Setup manifests, and in

301 group [Setup Scripts](#group-settings), runs with the team's secrets in its

302 environment. Reference a secret by name, for example `"$MY_LICENSE_KEY"`.

303* Secrets exist only in the script's process environment. Once the script

304 finishes, the value is gone unless the script wrote it somewhere, so store

305 nothing on the computer that you do not want every Bot that member runs to

306 reach.

307* Script output is checked for secret values before it is logged, and matches

308 are redacted.

309* A computer receives secrets only when its Team Setup comes from exactly one

310 team. A member whose computer applies setup from two or more teams gets no

311 secrets from any of them, since scripts from different teams share one

312 computer user.

313* Changes, including rotated values, take effect the next time the scripts

314 run: when a computer starts, on the periodic refresh, or when you recreate

315 it. See

316 [Roll out to existing computers](/grok-bot/private-networks#roll-out-to-existing-computers).

317 

318Limits: up to 100 secrets per team, up to 32 KB per value, and up to 96 KB in

319total. Names must be valid environment variable names, and names the computer

320runtime reserves, such as `PATH`, `HOME`, and anything starting with `SAND_`

321or `LD_`, are rejected when you save. Team Secrets are for scripts you control.

322They do not make a value available to Bots directly, and they are separate from

323the [secrets members store on a Bot](https://cursor.com/help/grok-bot/secrets).

324They are not available through the Admin API.

279 325 

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

281 327 

286because one computer spans every team the member belongs to. **Recreate** moves332because one computer spans every team the member belongs to. **Recreate** moves

287members 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

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

289disk; the member's next session starts a fresh computer on it. Neither action335disk; the member's next session starts a fresh computer on it.

290removes access: to do that, remove the member from the team or turn off Grok336**Terminate Inactive Computers**, below it, does the terminate for you when a

291Bot for their group, and revoke their sessions in your identity provider. See337computer goes 30 days without use. It is off by default. None of these remove

338access: 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. See

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

293 341 

294Available on the Enterprise plan.342Available on the Enterprise plan.

299 347 

300#### Action Recording348#### Action Recording

301 349 

302Records Bot actions: connector (MCP) tool calls, shell commands, browser350Records what a Bot did: every tool call and how it ended, the decision that

303navigations, and computer use sessions. Events are sanitized before they are351allowed or refused it (Auto-review, a hook, or the member), connector (MCP)

304stored or exported. Shell commands are secret-scrubbed; browser navigations352tool calls, shell commands, browser navigations, computer use sessions, file

305keep each page as `scheme://host/path` with the title but strip query strings353transfers, messages the Bot sent, routine runs, guardrail interventions, skills

306and credentials; computer use sessions record action and screenshot counts and354it read, and work it handed to subagents or cloud agents. Events are metadata,

307the session duration, without the screenshots, clicks, or typed text. The355sanitized before they are stored or exported. Shell commands are

356secret-scrubbed; browser navigations keep each page as `scheme://host/path`

357with the title but strip query strings and credentials; computer use sessions

358record action and screenshot counts and the session duration, without the

359screenshots, clicks, or typed text; every other event carries ids, outcomes,

360and durations. Tool arguments and results, file paths and names, and message

361bodies are never exported on these events; MCP arguments and results ship only

362through the opt-in conversation content export described below. The

308switch is on the Grok Bot page and is off by default. Recorded events do not363switch is on the Grok Bot page and is off by default. Recorded events do not

309appear on the Audit Log page. To receive them in your own collector, configure364appear on the Audit Log page. To receive them in your own collector, configure

310[OpenTelemetry Export](#opentelemetry-export), which delivers each event365[OpenTelemetry Export](https://cursor.com/docs/enterprise/opentelemetry-export),

311tagged `cursor.surface=grok_bot`. Retention details are on366which delivers each event tagged `cursor.surface=grok_bot`; the

367[Wire Reference](https://cursor.com/docs/enterprise/opentelemetry-export/wire#shared-grok_bot-attributes)

368lists every event and attribute. Retention details are on

312[logging and audit](/grok-bot/security#logging-and-audit).369[logging and audit](/grok-bot/security#logging-and-audit).

313 370 

314Available on the Enterprise plan.371Available on the Enterprise plan.

315 372 

373#### Conversation content export

374 

375An opt-in addition to OpenTelemetry Export that streams the text of user

376prompts and assistant responses from Grok Bot, and the arguments and results of

377Grok Bot MCP tool calls. It is off by default. In **Team Settings →

378OpenTelemetry Export**, turn on **Allow conversation content export**, then

379turn on **Conversation content** on your destination. That turns on

380**Prompts** and **Responses** and leaves **Tool I/O** off; turn on **Tool I/O**

381to also receive MCP tool arguments and results. Keep Action Recording on as

382well, so every tool I/O record has an MCP tool call record to join to. Turning

383a toggle off stops that export; turning it back on does not backfill earlier

384messages or tool calls.

385 

386Tool I/O covers hosted connector calls only: MCP calls Cursor runs, such as

387Jira, Slack, and Linear. `stdio` servers on the Bot's computer and built-in

388tools report no payloads yet.

389 

390Cursor scrubs the content before export: known credential shapes, PEM blocks,

391and email addresses become `[REDACTED: ...]` markers. Pattern matching cannot

392recognize every secret or every piece of personal data, and your team owns that

393residual risk. Teams on Privacy Mode (Legacy) cannot turn on conversation

394content export. See

395[Conversation content](https://cursor.com/docs/enterprise/opentelemetry-export#conversation-content)

396and [MCP tool I/O](https://cursor.com/docs/enterprise/opentelemetry-export#mcp-tool-io).

397 

398Available on the Enterprise plan.

399 

316#### Audit logs400#### Audit logs

317 401 

318Admin, security, and authentication events, plus Grok Bot control-plane402Admin, security, and authentication events, plus Grok Bot control-plane

329#### OpenTelemetry Export413#### OpenTelemetry Export

330 414 

331Streams Cursor usage metrics and logs, including recorded Grok Bot actions, to415Streams Cursor usage metrics and logs, including recorded Grok Bot actions, to

332a collector you run. It is the customer path for Action Recording events.416a collector you run. It is the customer path for Action Recording events and,

333Configure it under **Team Settings → OpenTelemetry Export**. Endpoint417when you opt in, conversation content. Records may include the member's email

418(`cursor.user.email`); it is optional and not exported for teams on Privacy

419Mode (Legacy). Configure it under **Team Settings → OpenTelemetry Export**.

420Endpoint

334requirements and the event schema are on421requirements and the event schema are on

335[OpenTelemetry Export](https://cursor.com/docs/enterprise/opentelemetry-export).422[OpenTelemetry Export](https://cursor.com/docs/enterprise/opentelemetry-export).

336 423 

337Available on the Enterprise plan.424Available on the Enterprise plan.

338 425 

426### Group settings

427 

428The controls above set the team-wide baseline. To widen that baseline for one

429cohort, open a group your team owns from

430[Members > Groups](https://cursor.com/dashboard/members?subtab=groups) and use

431its **Grok Bot** tab. Group settings only widen: a group can grant its members

432more than the team allows, never less, and a member in several groups gets the

433most permissive result. This is the same rule as

434[group model access](https://cursor.com/docs/enterprise/model-and-integration-management#how-team-and-group-model-access-combine).

435A group control left at the team's value changes nothing, so tighten controls

436on the Grok Bot page and widen them per group.

437 

438The tab has four sections:

439 

440* **Agent Capabilities.** Allow [Cloud Agents](#cloud-agents), raise the

441 [Execution on Local Computer](#execution-on-local-computer) ceiling, or turn

442 on [Allow Local Egress](#allow-local-egress) for group members when the team

443 has them off or stricter. For Auto-review, **Don't enforce for this group**

444 lifts the team's [Enforce Auto-review](#enforce-auto-review) lock so group

445 members can turn Auto-review off, and group Auto-review rules combine with

446 the team's [Auto-review rules](#auto-review-rules), with **Ask first**

447 winning when rules conflict.

448* **Network.** The group's own network policy, as described under

449 [Network Controls](#network-controls). A locked team policy applies to

450 everyone.

451* **Group Rules.** Rules for the group's Bots, combined with

452 [Team Rules](#team-rules). Members cannot turn them off.

453* **Setup Scripts.** Manifests that run on group members' computers alongside

454 [Team Setup](#team-setup). They use the same structure and run the same way,

455 the same no-secrets rule applies, and they read the same

456 [Team Secrets](#team-secrets) as the team's manifests; there are no

457 group-level secrets. See

458 [how Team Setup runs your scripts](/grok-bot/private-networks#how-team-setup-runs-your-scripts).

459 

460Group settings apply to groups your team owns, whether you manage membership by

461hand or sync it through

462[SCIM](https://cursor.com/docs/account/teams/scim#directory-groups). They are

463separate from

464[Organization Groups](https://cursor.com/docs/enterprise/organization-groups).

465To control who can use Grok Bot at all, use **Manage Group Access** on the Grok

466Bot page instead; see

467[Enabling Grok Bot for your team](#enabling-grok-bot-for-your-team).

468 

469Available on the Enterprise plan.

470 

339## Admin API471## Admin API

340 472 

341Enable Grok Bot and manage capabilities, Enforce Auto-review, group access,473Enable Grok Bot and manage capabilities, Enforce Auto-review, group access,

342network policy, team rules, and setup scripts through the474network policy, team rules, and setup scripts through the

343[Admin API](https://cursor.com/docs/account/teams/admin-api#grok-bot).475[Admin API](https://cursor.com/docs/account/teams/admin-api#grok-bot).

476[Team Secrets](#team-secrets) are managed from the dashboard only.

344 477 

345## Security478## Security

346 479 

411 544 

412### Why does a member see a plugin as Disabled by team admin?545### Why does a member see a plugin as Disabled by team admin?

413 546 

414Your team's connector policy blocks that server. Enable it in Teams547Your team's connector policy blocks that server. Enable it in **Teams

415Marketplace, add its server URL to your MCP allowlist if you use one, and have548Marketplace**, add its server URL to your MCP allowlist if you use one, and

416the member restart the app. If a permitted plugin still fails for regular549have the member restart the app. If a permitted plugin still fails for regular

417members with a vendor-side permission error, check the provider's550members with a vendor-side permission error, check the provider's

418requirements; some vendors restrict their MCP endpoints to their own551requirements; some vendors restrict their MCP endpoints to their own

419administrators. See552administrators. See

429### Can I see what kind of work my team does with Grok Bot?562### Can I see what kind of work my team does with Grok Bot?

430 563 

431Yes, on Enterprise teams where it has rolled out. The Conversation Insights564Yes, on Enterprise teams where it has rolled out. The Conversation Insights

432page of the Analytics dashboard has a Grok Bot source that groups Bot565page of the Analytics dashboard has a **Grok Bot** source that groups Bot

433conversations by Type of Work and Level of Automation. See566conversations by Type of Work and Level of Automation. See

434[Grok Bot Conversation Insights](https://cursor.com/docs/account/teams/analytics#grok-bot-conversation-insights).567[Grok Bot Conversation Insights](https://cursor.com/docs/account/teams/analytics#grok-bot-conversation-insights).

435 568 

444* [Connect to private networks](/grok-bot/private-networks)577* [Connect to private networks](/grok-bot/private-networks)

445* [Configure TLS-inspecting proxies](/grok-bot/proxies)578* [Configure TLS-inspecting proxies](/grok-bot/proxies)

446* [Manage Grok Bot computers](/grok-bot/computers)579* [Manage Grok Bot computers](/grok-bot/computers)

580* [Create and manage Bots](/grok-bot/bots)

447* [Approvals, security, and privacy](/grok-bot/approvals-security-and-privacy)581* [Approvals, security, and privacy](/grok-bot/approvals-security-and-privacy)

448* [Admin API](https://cursor.com/docs/account/teams/admin-api#grok-bot)582* [Admin API](https://cursor.com/docs/account/teams/admin-api#grok-bot)

449* [Grok Bot Conversation Insights](https://cursor.com/docs/account/teams/analytics#grok-bot-conversation-insights)583* [Grok Bot Conversation Insights](https://cursor.com/docs/account/teams/analytics#grok-bot-conversation-insights)