Documentation 2026-11-11 23:00 UTC to 2026-11-12 20:59 UTC

82saves the rule and can go ahead the next time. To finish the task now, ask the82saves the rule and can go ahead the next time. To finish the task now, ask the

83Bot to try again.83Bot to try again.

84 84 

85### Shared Bots and group chats85### Team Bots and group chats

86 86 

87On a [shared Bot](/grok-bot/team-bots), each teammate answers cards for their87On a [Team Bot](/grok-bot/team-bots), each teammate answers cards for their

88own requests in their own chat with the Bot. In a Slack thread, the card has88own requests in their own chat with the Bot. In a Slack thread, the card has

89**Allow once**, **Deny**, and **View details**, and only the person who asked89**Allow once**, **Deny**, and **View details**, and only the person who asked

90can answer. In a group chat, only the person whose message the Bot is answering90can answer. In a group chat, only the person whose message the Bot is answering

231URLs in a Bot you share. See [Share a Bot](/grok-bot/bots#share-a-bot) and the231URLs in a Bot you share. See [Share a Bot](/grok-bot/bots#share-a-bot) and the

232[third-party bot terms](https://x.ai/legal/bot-sharing-terms).232[third-party bot terms](https://x.ai/legal/bot-sharing-terms).

233 233 

234A [shared Bot](/grok-bot/team-bots) is different: teammates chat with the same234A [Team Bot](/grok-bot/team-bots) is different: teammates chat with the same

235Bot, and the apps, secrets, skills, and files its owner adds work in every235Bot, and the apps, secrets, skills, and files its owner adds work in every

236teammate's chat. Only add keys and files you're happy for everyone you share it236teammate's chat. Only add keys and files you're happy for everyone you share it

237with to use.237with to use.

36 36 

37To pick a different one later, right-click your primary Bot in the sidebar and37To pick a different one later, right-click your primary Bot in the sidebar and

38choose **Replace with different Bot**. On iPhone and Android, use **Replace38choose **Replace with different Bot**. On iPhone and Android, use **Replace

39Primary Bot…** in the Bot's menu. A [shared Bot](/grok-bot/team-bots) can't39Primary Bot…** in the Bot's menu. A [Team Bot](/grok-bot/team-bots) can't

40be your primary Bot.40be your primary Bot.

41 41 

42## Edit a Bot42## Edit a Bot

51 51 

52The Bot keeps lasting rules in its memory. Personal Bots no longer have a52The Bot keeps lasting rules in its memory. Personal Bots no longer have a

53description or a **Bot settings** page; to change what a Bot does, tell it in53description or a **Bot settings** page; to change what a Bot does, tell it in

54chat. A [shared Bot](/grok-bot/team-bots) still has a description, which its54chat. A [Team Bot](/grok-bot/team-bots) still has a description, which its

55owner or a Manager edits under **About** in the Bot's details.55owner or a Manager edits under **About** in the Bot's details.

56 56 

57### Change a Bot's name, picture, and label57### Change a Bot's name, picture, and label

82from Photos** or **Take Photo**, then lets you crop the image; images can be up82from Photos** or **Take Photo**, then lets you crop the image; images can be up

83to 25 MB.83to 25 MB.

84 84 

85On Grok Bot for Android 1.18.0, tapping **Done** or **Discard** after changing a

86Bot's name, title, or picture can show a blank or error screen. Your change is

87usually saved; go back to the chat and check. This is fixed in Android 1.19.0;

88update Grok Bot when Google Play offers it.

89 

85## Organize your roster90## Organize your roster

86 91 

87* **Pin** active Bots to keep them at the top of the sidebar.92* **Pin** active Bots to keep them at the top of the sidebar.

67 67 

68Voice chat works with one Bot at a time, not in group chats; open that Bot's68Voice chat works with one Bot at a time, not in group chats; open that Bot's

69own chat to start a call. On desktop you can also voice chat with a teammate's69own chat to start a call. On desktop you can also voice chat with a teammate's

70[shared Bot](/grok-bot/team-bots) from your own chat with it.70[Team Bot](/grok-bot/team-bots) from your own chat with it.

71 71 

72If the connection drops, Grok Bot tries to reconnect on its own first, so a72If the connection drops, Grok Bot tries to reconnect on its own first, so a

73short drop usually picks back up without you doing anything. If it can't, the73short drop usually picks back up without you doing anything. If it can't, the

76**Dismiss**, check your internet connection, and choose **Start voice chat**76**Dismiss**, check your internet connection, and choose **Start voice chat**

77again.77again.

78 78 

79On the phone app (1.18 and later, iPhone and Android), a voice chat ends when a

80phone call, FaceTime, or another app takes over the audio. This works the same

81as choosing **Hang up**, and the voice chat doesn't resume on its own; choose

82**Start voice chat** again when you're done. Short interruptions on Android,

83such as a navigation prompt, only pause the conversation.

84 

79If Grok Bot says microphone access was denied, allow it to use the microphone in85If Grok Bot says microphone access was denied, allow it to use the microphone in

80your system settings. If it says no microphone was found, connect one and try86your system settings. If it says no microphone was found, connect one and try

81again. To choose which microphone the desktop app uses, open **Settings** and87again. To choose which microphone the desktop app uses, open **Settings** and

147| Your email is on a domain your company manages, or your Cursor account is on a team | Connecting from X Chat isn't available. Use Grok Bot in the Grok Bot app instead. |153| Your email is on a domain your company manages, or your Cursor account is on a team | Connecting from X Chat isn't available. Use Grok Bot in the Grok Bot app instead. |

148| Your Grok account's email isn't verified | Verify your email on Grok, then try again. |154| Your Grok account's email isn't verified | Verify your email on Grok, then try again. |

149| More than one Cursor account uses your email | [Contact support](/grok-bot/troubleshooting) with the email address. |155| More than one Cursor account uses your email | [Contact support](/grok-bot/troubleshooting) with the email address. |

150| You've used up your Grok Bot usage | See [How does Grok Bot usage work?](https://cursor.com/help/grok-bot/plans#how-does-grok-bot-usage-work) |156| You've used up your Grok Bot usage | See [How does Grok Bot usage work?](https://grok.com/help/grok-bot/plans#how-does-grok-bot-usage-work) |

151| Your Bots don't show up in X Chat | Update the X app to the latest version, then quit and reopen it. |157| Your Bots don't show up in X Chat | Update the X app to the latest version, then quit and reopen it. |

152| You see a new Bot instead of your own, or tapping your Bot shows **Something went wrong** | Your X account may be connected to a different Grok account. Follow the steps below. |158| You see a new Bot instead of your own, or tapping your Bot shows **Something went wrong** | Your X account may be connected to a different Grok account. Follow the steps below. |

153 159 

301and noisy updates.307and noisy updates.

302 308 

303A handoff needs a Bot acting for one person on that turn. Where you talk to it,309A handoff needs a Bot acting for one person on that turn. Where you talk to it,

304and whether it's a personal Bot or a [shared Bot](/grok-bot/team-bots),310and whether it's a personal Bot or a [Team Bot](/grok-bot/team-bots),

305decide this:311decide this:

306 312 

307| Bot | Where you ask | Can it message other Bots? | Acting for | Where the reply lands |313| Bot | Where you ask | Can it message other Bots? | Acting for | Where the reply lands |

308| --- | --- | --- | --- | --- |314| --- | --- | --- | --- | --- |

309| Personal Bot | The app, or your own Slack DM with it | Yes | You | The app chat, not Slack |315| Personal Bot | The app, or your own Slack DM with it | Yes | You | The app chat, not Slack |

310| Personal Bot | A Slack channel thread | No | Nobody, the thread is shared | The Bot says it can't do that |316| Personal Bot | A Slack channel thread | No | Nobody, the thread is shared | The Bot says it can't do that |

311| Shared Bot | A Slack channel thread or Slack DM | Yes, to that person's own Bots | The teammate who mentioned it | The same Slack thread |317| Team Bot | A Slack channel thread or Slack DM | Yes, to that person's own Bots | The teammate who mentioned it | The same Slack thread |

312 318 

313To hand work between Bots from a Slack channel, share a Bot and add it to Slack.319To hand work between Bots from a Slack channel, share a Bot and add it to Slack.

314A shared Bot has its own Slack app and handle, and anyone in the channel can320A Team Bot has its own Slack app and handle, and anyone in the channel can

315give it work. See [How do I add a shared Bot to321give it work. See [How do I add a Team Bot to

316Slack?](/grok-bot/team-bots#how-do-i-add-a-team-bot-to-slack)322Slack?](/grok-bot/team-bots#how-do-i-add-a-team-bot-to-slack)

317 323 

318## Use threads and reactions324## Use threads and reactions

44the page without the Bot seeing them. When a site emails a one-time code, the44the page without the Bot seeing them. When a site emails a one-time code, the

45Bot can read it from a connected Gmail or Outlook account or from [its own45Bot can read it from a connected Gmail or Outlook account or from [its own

46inbox](#give-your-bots-an-email-address). At checkout, it can use a card saved46inbox](#give-your-bots-an-email-address). At checkout, it can use a card saved

47in Vault, a card you enter in a Secure Form, or a connected wallet such as Link47in Vault, a card you enter in a Secure Form, or a connected wallet such as Link,

48or X Money; see [Pay for things](/grok-bot/vault#pay-for-things).48X Money, or Shop Pay; see [Pay for things](/grok-bot/vault#pay-for-things).

49 49 

50The Bot hands you the computer when a form can't do the step:50The Bot hands you the computer when a form can't do the step:

51 51 

873. When Grok Bot asks you to **Authorize** or **Authenticate**, finish the873. When Grok Bot asks you to **Authorize** or **Authenticate**, finish the

88 provider login in your browser.88 provider login in your browser.

894. If sign-in doesn't finish, choose **Reconnect** on the app, or **Reopen** on894. If sign-in doesn't finish, choose **Reconnect** on the app, or **Reopen** on

90 the in-chat card, to bring the sign-in page back.90 the in-chat card, to bring the sign-in page back. Finish the sign-in within

91 about 10 minutes, or start again from the card.

915. Confirm the app appears under **Installed**.925. Confirm the app appears under **Installed**.

92 93 

93In chat, type `@` to attach the app to the task.94In chat, type `@` to attach the app to the task.

121requires can't be removed.122requires can't be removed.

122 123 

123* **Apps are account-wide.** A connected app is available to every Bot you run.124* **Apps are account-wide.** A connected app is available to every Bot you run.

124 A teammate's [shared Bot](/grok-bot/team-bots) asks before it uses your125 A teammate's [Team Bot](/grok-bot/team-bots) asks before it uses your

125 accounts.126 accounts.

126* **App logins stay off the computer.** OAuth tokens are held on Cursor's127* **App logins stay off the computer.** OAuth tokens are held on Cursor's

127 connector backend, and the Bot invokes tools without receiving them.128 connector backend, and the Bot invokes tools without receiving them.

167 Bot leaves the sign-off to it. Gmail connects one mailbox at a time; to use a168 Bot leaves the sign-off to it. Gmail connects one mailbox at a time; to use a

168 different one, disconnect the current mailbox and authorize the other.169 different one, disconnect the current mailbox and authorize the other.

169 Disconnect Gmail if a Bot should not use that mailbox. Some other apps, like170 Disconnect Gmail if a Bot should not use that mailbox. Some other apps, like

170 Notion, can connect a second account.171 Notion, can [connect a second account](#connect-a-second-account).

171* **Stripe:** Stripe ends every connection a fixed time after sign-in, however172* **Stripe:** Stripe ends every connection a fixed time after sign-in, however

172 often it's used, so you need to reconnect it from time to time. If you've173 often it's used, so you need to reconnect it from time to time. If you've

173 used Stripe recently, a Bot tells you when it needs reconnecting.174 used Stripe recently, a Bot tells you when it needs reconnecting.

174* **X:** the X plugin needs X API credits on your X developer account.175* **X:** the X plugin needs X API credits on your X developer account.

176* **Microsoft Power BI:** connects with a work or school Microsoft account; a

177 personal Microsoft account can't connect it. The Bot can list workspaces,

178 reports, and datasets, and render a report or one of its pages as images.

179 Every Power BI tool only reads. Rendering needs the workspace on Premium,

180 Embedded, or Fabric capacity, and the Power BI tenant setting **Export

181 reports as image files** turned on.

182* **Google BigQuery:** the Bot queries the datasets the connected Google

183 account can read. It signs in to Google as **Grok**, like the other Google

184 apps, so a company Google block uses [the steps

185 below](#if-google-says-an-admin-needs-to-review-grok). A team admin can enter

186 the team's own Google OAuth client ID and secret in the plugin's team setup

187 on the dashboard's [Plugins & MCPs page](https://cursor.com/dashboard/plugins);

188 members then sign in under that client instead.

189* **Databricks Genie:** a team admin sets it up before members can connect it.

190 The admin registers an OAuth app connection in the Databricks account, then

191 enters the workspace URL, client ID, and client secret (left blank for a

192 public client) in the plugin's team setup on the dashboard's [Plugins & MCPs

193 page](https://cursor.com/dashboard/plugins). Each member then signs in with

194 their own Databricks account, and the Bot asks Genie questions in natural

195 language against the data that account can query.

196* **Asana:** needs no admin setup. The Bot works in the workspaces and projects

197 your Asana account can open.

198* **Vanta:** keeps each account in one region. The first time you connect it,

199 pick your account's region at sign-in: **United States**, **Europe**, or

200 **Australia**. A sign-in on the wrong region doesn't find your account; sign

201 in again and choose the other region.

202* **Shop Pay:** a wallet. Connect it and sign in to Shop, and the Bot can check

203 out with Shop Pay on Shopify stores. See [Pay for

204 things](/grok-bot/vault#pay-for-things).

205 

206### Connect a second account

207 

208Some apps can connect more than one account, like two Notion workspaces.

209 

2101. Choose **Connect apps** in the sidebar and open the app.

2112. Under **Accounts**, choose **Add Another Account**.

2123. Give the account a label, like work or personal.

2134. Choose **Authorize** and sign in to the second account.

214 

215On the phone, open the app from **Connect apps** and choose **Add account**.

216 

217Tell the Bot which account to use by its label, for example “Use my work

218Notion.” Every Bot on your Grok Bot account can use every connected account. If

219you don't see **Add Another Account**, that app connects one account at a time.

175 220 

176### If Google says an admin needs to review Grok221### If Google says an admin needs to review Grok

177 222 

178A company Google account can stop the connection before Gmail, Calendar, Drive,223A company Google account can stop the connection before Gmail, Calendar, Drive,

179Docs, Sheets, or Slides finishes signing in. Grok Bot signs in to Google as224Docs, Sheets, Slides, or BigQuery finishes signing in. Grok Bot signs in to

180**Grok**, not Cursor. This is separate from the Cursor **Disabled by team225Google as **Grok**, not Cursor. This is separate from the Cursor **Disabled by

181admin** control.226team admin** control.

182 227 

183If the Google page says **Your admin needs to review Grok**, Grok is not228If the Google page says **Your admin needs to review Grok**, Grok is not

184approved for that Workspace yet. Request access if that button is there, and229approved for that Workspace yet. Request access if that button is there, and

202page still says access is blocked, [contact support](/grok-bot/troubleshooting)247page still says access is blocked, [contact support](/grok-bot/troubleshooting)

203with the Google account email and a screenshot of the blocked page.248with the Google account email and a screenshot of the blocked page.

204 249 

250### If Microsoft says an admin needs to approve Grok Bot

251 

252A work or school Microsoft 365 account can stop **Outlook**, **Outlook

253Calendar**, **OneDrive**, or **Teams** from connecting until the organization's

254Microsoft 365 admin approves the app. Retrying the sign-in or allowing the

255permissions again doesn't help.

256 

257* On your computer, the sign-in page says **Your organization's Microsoft 365

258 admin needs to approve this app before you can connect** and shows an

259 **Approval link for your IT admin**. Send that link to your IT admin. After

260 they approve it, connect again from Grok Bot.

261* On the phone app 1.19.0 or later, the connect card says the same and adds

262 **Ask your IT admin to approve Grok Bot, then connect again**. The phone

263 doesn't show the approval link, so if your admin needs it, connect once from

264 your computer to get it.

265 

266If the page says the app is **blocked by your organization** instead, the admin

267has to allow the connection. The page lists the connector, the Microsoft Entra

268application ID, the error code, and the time to send them.

269 

270### If the phone says to connect on your computer

271 

272Some providers don't finish sign-in from a phone browser. On the phone app

2731.19.0 or later, **Connect** for **Adapter**, **Robinhood**, and **Intercom**,

274and for **Postiz** on iPhone, shows **Connect on your computer** instead of

275opening the sign-in page. Open Grok Bot on your computer and connect the app

276there. The connection then works on your phone too, because apps belong to your

277account, not the device.

278 

279**Slack** still signs in on the phone. If you close its sign-in before

280finishing, the phone reminds you that Slack's phone sign-in needs your

281workspace password, and that you can connect Slack from your computer instead.

282 

205### Connect 1Password283### Connect 1Password

206 284 

2071Password lets your Bots sign in to websites on their computer with logins from2851Password lets your Bots sign in to websites on their computer with logins from

277 can already open. If members see “This team does not have the SharePoint355 can already open. If members see “This team does not have the SharePoint

278 integration”, the admin needs to finish the Delegated sign-in.356 integration”, the admin needs to finish the Delegated sign-in.

279 357 

280For more setup help, see [Connect358For more setup help, see

281apps](https://cursor.com/help/grok-bot/connect-apps).359[Connect plugins](https://grok.com/help/grok-bot/connect-plugins).

282 360 

283## Give your Bots an email address361## Give your Bots an email address

284 362 

320 one is deleted.398 one is deleted.

321* **Yours, not one Bot's.** All your Bots can use the address in your own chats399* **Yours, not one Bot's.** All your Bots can use the address in your own chats

322 and routines. It isn't used in Slack threads or in chats where someone else is400 and routines. It isn't used in Slack threads or in chats where someone else is

323 talking to the Bot, and a [shared Bot](/grok-bot/team-bots) doesn't have a401 talking to the Bot, and a [Team Bot](/grok-bot/team-bots) doesn't have a

324 team address.402 team address.

325* **Reading mail.** Anyone can send mail to the address. Mail that fails the403* **Reading mail.** Anyone can send mail to the address. Mail that fails the

326 spam or virus scan is kept without its body or attachments, and it never404 spam or virus scan is kept without its body or attachments, and it never

43 43 

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

45conversations, memory, routines, and computer across every team they belong to.45conversations, memory, routines, and computer across every team they belong to.

46That includes shared Bots that teammates use, connected apps, email inboxes,46That includes Team Bots that teammates use, connected apps, email inboxes,

47and files. Their Cursor account stays, and they stay on the team and start47and files. Their Cursor account stays, and they stay on the team and start

48fresh the next time they use Grok Bot.48fresh the next time they use Grok Bot.

49 49 

128| **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. |128| **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. |

129| **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. |129| **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. |

130| **Failed**, Another deletion is in progress | This member's Grok Bot data is already being deleted. | Wait for it to finish. |130| **Failed**, Another deletion is in progress | This member's Grok Bot data is already being deleted. | Wait for it to finish. |

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

132| **Failed**, Action could not be completed | The recreate or terminate did not finish. For a recreate, a Bot on the member's computer may have been unable to pause in time, and the member keeps their current computer. | Run the operation again for the affected members, once their Bots are idle if you can. If it fails twice, [contact support](https://cursor.com/help/grok-bot/get-help) with the member's email and the time of the operation. |132| **Failed**, Action could not be completed | The recreate or terminate did not finish. For a recreate, a Bot on the member's computer may have been unable to pause in time, and the member keeps their current computer. | Run the operation again for the affected members, once their Bots are idle if you can. If it fails twice, [contact support](https://grok.com/help/grok-bot/get-help) with the member's email and the time of the operation. |

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

134 134 

135## Restart after a settings change135## Restart after a settings change

159period from 30 to 365 days. Turning it on or shortening the period opens a159period from 30 to 365 days. Turning it on or shortening the period opens a

160confirmation first.160confirmation first.

161 161 

162* **Deletion works like [Delete VMs and data](#delete-vms-and-data).** The

163 member's Bots and conversations stay. Their files, logins, and installed apps

164 are gone for good, and their next message starts an empty computer.

165* **There's no warning.** Members get no notice before their computer is

166 deleted.

167* **The shortest period wins.** One computer spans every team a member belongs

168 to, so it follows the shortest period set by any of their Enterprise teams.

169 

162Each deletion is recorded in the170Each deletion is recorded in the

163[Audit Log](https://cursor.com/dashboard/audit-log). Turning the setting off171[Audit Log](https://cursor.com/dashboard/audit-log). Turning the setting off

164stops further deletions.172stops further deletions.

206* [Grok Bot security](/grok-bot/security)214* [Grok Bot security](/grok-bot/security)

207* [Connect to private networks](/grok-bot/private-networks)215* [Connect to private networks](/grok-bot/private-networks)

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

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

1#### Reference

2 

3# Deep links

4 

5A deep link opens Grok Bot on your desktop or phone from a shortcut, note, or

6another app. The app must be installed and signed in.

7 

8## Start a message

9 

10```text

11grokbot://app/v1/prompt?id=<bot-id>&text=<message>

12```

13 

14Opens the Bot's chat with `text`, up to 1,000 characters, in the message box.

15The text is added only if the message box is empty, and it isn't sent until you

16send it. Without `id`, the link uses your

17[primary Bot](/grok-bot/bots#your-primary-bot), and does nothing if you haven't

18set one. The Bot's ID is the end of its link: click the Bot's name, choose

19**Share**, then **Copy link**. Encode `text`, for example `%20` for a space, or

20build the link here. The web link opens the app from a browser, so it works where

21`grokbot://` links aren't clickable.

121they [enable Grok Bot](/grok-bot/teams-and-enterprises#enabling-grok-bot-for-your-team).121they [enable Grok Bot](/grok-bot/teams-and-enterprises#enabling-grok-bot-for-your-team).

122Only providers on the sub-processor list can process your data, and the set of122Only providers on the sub-processor list can process your data, and the set of

123models changes over time. See123models changes over time. See

124[Models and data](/grok-bot/security#models-and-data) and124[Models and data](/grok-bot/security#models-and-data).

125[Which AI models power Grok Bot?](https://cursor.com/help/grok-bot/models).

126 125 

127## How does Grok Bot handle data and privacy?126## How does Grok Bot handle data and privacy?

128 127 

163your Cursor account, not on Grok or X, and macOS and iOS share the same usage.162your Cursor account, not on Grok or X, and macOS and iOS share the same usage.

164 163 

165See [Grok Bot on The X Subscription](/x-subscription/grok-bot) and164See [Grok Bot on The X Subscription](/x-subscription/grok-bot) and

166[Plans and billing](https://cursor.com/help/grok-bot/plans). Enterprise165[Plans and billing](https://grok.com/help/grok-bot/plans). Enterprise

167customers should contact their Cursor account team.166customers should contact their Cursor account team.

168 167 

169## Which Grok plans can I link?168## Which Grok plans can I link?

172**X Premium+**. **SuperGrok Lite** and **Grok Enterprise** cannot link. If you171**X Premium+**. **SuperGrok Lite** and **Grok Enterprise** cannot link. If you

173have a seat on a self-serve **Grok Business** plan, you don't link from the172have a seat on a self-serve **Grok Business** plan, you don't link from the

174plan screen. Sign out, then sign back in with **Sign in with Grok** using the173plan screen. Sign out, then sign back in with **Sign in with Grok** using the

175Grok account that holds the seat. On The X Subscription there's nothing to174Grok account that holds the seat. Grok Bot usage matches the license on your

176link: Grok Bot draws from your plan's shared weekly pool. See175seat: a **SuperGrok** license gets SuperGrok usage, and a **SuperGrok Heavy**

177[Link SuperGrok for Grok Bot](https://cursor.com/help/grok-bot/supergrok).176license gets SuperGrok Heavy usage. If an admin removes your seat, Grok Bot

177access from the seat ends. On The X Subscription there's nothing to link: Grok

178Bot draws from your plan's shared weekly pool. See

179[Link SuperGrok for Grok Bot](https://grok.com/help/grok-bot/supergrok).

180 

181If you see an error that the Grok account is already linked to another Cursor

182account, or you still don't have access after signing in with the right Grok

183account, [contact support](/grok-bot/troubleshooting#before-contacting-support)

184with your Cursor account email and the Grok account email.

178 185 

179## I don't see Link Grok Account.186## I don't see Link Grok Account.

180 187 

342limits template sharing, the app doesn't offer **Create a copy**.349limits template sharing, the app doesn't offer **Create a copy**.

343 350 

344The link exposes the Bot's configuration. Strip secrets and anything351The link exposes the Bot's configuration. Strip secrets and anything

345confidential before you share. Adding a shared Bot accepts the352confidential before you share. Adding a Team Bot accepts the

346[third-party bot terms](https://x.ai/legal/bot-sharing-terms). See353[third-party bot terms](https://x.ai/legal/bot-sharing-terms). See

347[Share a Bot](/grok-bot/bots#share-a-bot).354[Share a Bot](/grok-bot/bots#share-a-bot).

348 355 

349To give the team one Bot they all talk to, rather than a copy each person356To give the team one Bot they all talk to, rather than a copy each person

350customizes, publish a [shared Bot](/grok-bot/team-bots).357customizes, publish a [Team Bot](/grok-bot/team-bots).

351 358 

352## What happens if I delete a Bot?359## What happens if I delete a Bot?

353 360 

269 **Media**, **Links**, **Files**, **Apps**, or **Pinned**, to show only that269 **Media**, **Links**, **Files**, **Apps**, or **Pinned**, to show only that

270 kind. Choose **All** to see everything again.270 kind. Choose **All** to see everything again.

271 271 

272On a [shared Bot](/grok-bot/team-bots), the desktop Library lists what the272On a [Team Bot](/grok-bot/team-bots), the desktop Library lists what the

273Bot made for you under **Private to you**, and pages shared with your team and273Bot made for you under **Private to you**, and pages shared with your team and

274the Bot's own files under **Bot's files**. There's no **Pinned** heading: hover274the Bot's own files under **Bot's files**. There's no **Pinned** heading: hover

275over a row in **Private to you** and click its pin to keep it at the top. The275over a row in **Private to you** and click its pin to keep it at the top. The

34SuperGrok Plus, SuperGrok Heavy, or X Premium+ subscription, or use a seat on a34SuperGrok Plus, SuperGrok Heavy, or X Premium+ subscription, or use a seat on a

35self-serve Grok Business plan. See35self-serve Grok Business plan. See

36[Grok Bot on The X Subscription](/x-subscription/grok-bot) and36[Grok Bot on The X Subscription](/x-subscription/grok-bot) and

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

38 38 

39Grok Bot needs cloud data storage, so if your account is on Privacy Mode39Grok Bot needs cloud data storage, so if your account is on Privacy Mode

40(Legacy), the app asks you to switch to Privacy Mode first. On a team, a team40(Legacy), the app asks you to switch to Privacy Mode first. On a team, a team

85`Cmd/Ctrl+N`. Name the Bot and choose **Create**. On a Cursor team, **+** opens85`Cmd/Ctrl+N`. Name the Bot and choose **Create**. On a Cursor team, **+** opens

86a menu. Choose **Create a Bot** to make one, or **Browse shared Bots** to use a86a menu. Choose **Create a Bot** to make one, or **Browse shared Bots** to use a

87Bot a teammate shared. To share your own Bot with teammates, see87Bot a teammate shared. To share your own Bot with teammates, see

88[Shared Bots](/grok-bot/team-bots).88[Team Bots](/grok-bot/team-bots).

89 89 

90To rename a Bot later, click its name at the top of the chat to open its90To rename a Bot later, click its name at the top of the chat to open its

91details, then click the name again to edit it.91details, then click the name again to edit it.

22 engineering organization can access Grok Bot through your Cursor team.22 engineering organization can access Grok Bot through your Cursor team.

23* [Add an authentication rule](#allow-sign-in-to-idp-apps-from-the-computer) so23* [Add an authentication rule](#allow-sign-in-to-idp-apps-from-the-computer) so

24 users can sign in to IdP-provisioned apps from the Bot's computer, which runs24 users can sign in to IdP-provisioned apps from the Bot's computer, which runs

25 Linux and does not run device-trust agents.25 Linux and is not a managed device.

26 26 

27Only the first change controls Grok Bot sign-in. The second never blocks it, and27Only the first change controls Grok Bot sign-in. The second never blocks it, and

28it does not apply to connected-app sign-in, because connecting an app does not28it does not apply to connected-app sign-in, because connecting an app does not

96Inside the hosted computer, members sign in to applications through your own96Inside the hosted computer, members sign in to applications through your own

97identity provider in the browser, so your session policies govern those97identity provider in the browser, so your session policies govern those

98sessions. The computer runs Linux and is not enrolled in mobile device98sessions. The computer runs Linux and is not enrolled in mobile device

99management (MDM), and device-trust agents like Okta FastPass do not run on it.99management (MDM). Okta FastPass runs on it only after you [set up Okta Verify

100Any rule that requires FastPass, a registered or managed device, a compliant100and FastPass](/grok-bot/okta-fastpass). Without that setup, any rule that

101device, or a phishing-resistant factor only FastPass can satisfy fails in the101requires FastPass or a phishing-resistant factor only FastPass can satisfy fails

102computer browser.102in the computer browser. Rules that require a managed or compliant device fail

103 103either way.

104Do not turn FastPass or device compliance off for the whole company. Add a104 

105higher-priority rule scoped to this unmanaged Linux session. This change covers105Do not turn FastPass or device compliance off for the whole company. If your

106policies require FastPass, set up Okta Verify on the computers. Otherwise, add

107a higher-priority rule scoped to this unmanaged Linux session. This change covers

106only the IdP-provisioned apps the Bot opens in the computer browser; it is not108only the IdP-provisioned apps the Bot opens in the computer browser; it is not

107required for Grok Bot sign-in or for connected-app sign-in.109required for Grok Bot sign-in or for connected-app sign-in.

108 110 

113* Passkeys stored in a password manager on the computer, installed with115* Passkeys stored in a password manager on the computer, installed with

114 [Team Setup Scripts](/grok-bot/teams-and-enterprises#team-setup-scripts). Team116 [Team Setup Scripts](/grok-bot/teams-and-enterprises#team-setup-scripts). Team

115 Setup Scripts is Enterprise only.117 Setup Scripts is Enterprise only.

118* Okta FastPass, after you [set up Okta Verify and

119 FastPass](/grok-bot/okta-fastpass) with a Team Setup Script. FastPass

120 satisfies FastPass and Okta Verify factor requirements, but not

121 managed-device rules.

116 122 

117> Requiring managed devices for Grok Bot sign-in itself still works. Grok Bot123> Requiring managed devices for Grok Bot sign-in itself still works. Grok Bot

118> uses your Cursor SSO, so a device-aware sign-in policy in your identity124> uses your Cursor SSO, so a device-aware sign-in policy in your identity

183 189 

184## Limitations190## Limitations

185 191 

186* Okta FastPass does not run on Linux, so the Bot's computer cannot satisfy192* Okta FastPass runs on the Bot's computer only after you [set up Okta Verify

187 FastPass or managed-device rules.193 and FastPass](/grok-bot/okta-fastpass).

188* The computer is not enrolled in MDM by default.194* The computer is not enrolled in MDM by default, so it cannot satisfy

195 managed-device or compliant-device rules.

189* Group-based assignment in Entra ID requires P1 or P2 and does not include196* Group-based assignment in Entra ID requires P1 or P2 and does not include

190 nested groups.197 nested groups.

191 198 

214 221 

215## Related pages222## Related pages

216 223 

224* [Set up Okta Verify and FastPass](/grok-bot/okta-fastpass)

217* [Grok Bot security](/grok-bot/security)225* [Grok Bot security](/grok-bot/security)

218* [Grok Bot for teams and enterprises](/grok-bot/teams-and-enterprises)226* [Grok Bot for teams and enterprises](/grok-bot/teams-and-enterprises)

219* [SSO](https://cursor.com/docs/account/teams/sso)227* [SSO](https://cursor.com/docs/account/teams/sso)

272 272 

273Other places show less:273Other places show less:

274 274 

275* **Shared Bots notify only the sender.** In a shared Bot, the notice and its275* **Team Bots notify only the sender.** In a Team Bot, the notice and its

276 buttons go only to the teammate who sent the blocked message, in their own276 buttons go only to the teammate who sent the blocked message, in their own

277 chat with the Bot, and Edit or Reset changes only that chat. The Bot's owner277 chat with the Bot, and Edit or Reset changes only that chat. The Bot's owner

278 isn't shown the deny reason or your Blocked Message. Rooms and group chats278 isn't shown the deny reason or your Blocked Message. Rooms and group chats

324 324 

325**Covered:** the model requests behind your team members' Grok Bot325**Covered:** the model requests behind your team members' Grok Bot

326conversations. That includes every step of a turn, subagents, the summaries326conversations. That includes every step of a turn, subagents, the summaries

327Grok Bot writes of long conversations, and routines. A shared Bot or room327Grok Bot writes of long conversations, and routines. A Team Bot or room

328follows its team's inference hook. A personal Bot follows the team its owner has328follows its team's inference hook. A personal Bot follows the team its owner has

329selected. Each request gets its own frame with the conversation so far.329selected. Each request gets its own frame with the conversation so far.

330 330 

17 plan and Cursor Teams include Grok Bot, and you can also link an individual17 plan and Cursor Teams include Grok Bot, and you can also link an individual

18 SuperGrok, SuperGrok Plus, SuperGrok Heavy, or X Premium+ subscription. See18 SuperGrok, SuperGrok Plus, SuperGrok Heavy, or X Premium+ subscription. See

19 [Grok Bot on The X Subscription](/x-subscription/grok-bot) and19 [Grok Bot on The X Subscription](/x-subscription/grok-bot) and

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

21* Internet connection21* Internet connection

22 22 

23The iOS app also runs on iPad (iPadOS 18 or later).23The iOS app also runs on iPad (iPadOS 18 or later).

112 **Payments & subscriptions → Subscriptions**. For Google Play billing112 **Payments & subscriptions → Subscriptions**. For Google Play billing

113 questions and refunds, use113 questions and refunds, use

114 [Google Play's refund support](https://support.google.com/googleplay/answer/2479637).114 [Google Play's refund support](https://support.google.com/googleplay/answer/2479637).

115 Android has no in-app trial.115 Android has no in-app trial. A Google Play subscription belongs to the Grok

116 Bot account that bought it. If it was bought while you were signed in to a

117 different Grok Bot account, changing the plan from the app fails with a

118 general error and nothing is charged. Sign in to the account that owns the

119 subscription to change the plan, or let it end and subscribe again from the

120 account you want to use.

116 121 

117The Grok Bot usage-credit trial claimed on web or desktop is separate; see122The Grok Bot usage-credit trial claimed on web or desktop is separate; see

118[Is there a free trial?](/grok-bot/faq#is-there-a-free-trial).123[Is there a free trial?](/grok-bot/faq#is-there-a-free-trial).

213A Bot can use some apps on your phone when you ask, such as checking your218A Bot can use some apps on your phone when you ask, such as checking your

214calendar or setting a timer. This works only in your own chat with a Bot you219calendar or setting a timer. This works only in your own chat with a Bot you

215own in the Grok Bot app. It doesn't work in group chats, in other apps such as220own in the Grok Bot app. It doesn't work in group chats, in other apps such as

216Slack, or with a shared Bot someone else owns.221Slack, or with a Team Bot someone else owns.

217 222 

218On iPhone and Android:223On iPhone and Android:

219 224 

247phone passes alarms and timers to your Clock app, which may open. The Clock app252phone passes alarms and timers to your Clock app, which may open. The Clock app

248doesn't confirm that it saved them, so the Bot asks you to check there.253doesn't confirm that it saved them, so the Bot asks you to check there.

249 254 

255On Android, Grok Bot 1.18.0 removed the ability to read your phone's

256notifications, and the app no longer asks for notification access. If you

257granted it in an earlier version, you can remove it under **Settings** >

258**Notifications** > **Device & app notifications** on your phone.

259 

250### Keep Grok Bot open on your phone260### Keep Grok Bot open on your phone

251 261 

252The Bot can reach your phone only while Grok Bot is open on it. If the app is262The Bot can reach your phone only while Grok Bot is open on it. If the app is

390 400 

391See [Message and collaborate](/grok-bot/chat-and-collaboration) for group behavior and401See [Message and collaborate](/grok-bot/chat-and-collaboration) for group behavior and

392[Troubleshooting](/grok-bot/troubleshooting) for computer recovery.402[Troubleshooting](/grok-bot/troubleshooting) for computer recovery.

403 

404To start a message to a Bot from a shortcut or another app, use a

405[deep link](/grok-bot/deep-links).

1#### Teams and enterprises

2 

3# Set up Okta Verify and FastPass

4 

5This guide is for Okta admins whose sign-in policies require Okta FastPass.

6Grok Bot computers ship with a setup script that installs Okta Verify and starts

7the services FastPass needs, so Bots can sign in to Okta-protected apps in the

8computer browser. For assigning the Cursor app and other Okta and Entra ID

9settings, see [Configure identity and access](/grok-bot/identity-and-access).

10 

11> Okta Verify installs through

12> [Team Setup Scripts](/grok-bot/teams-and-enterprises#team-setup-scripts),

13> which is Enterprise only.

14 

15## Before you start

16 

17* You're an Okta admin and a Cursor team admin on the Enterprise plan.

18* If your team restricts egress with

19 [Network Controls](/grok-bot/security#network-policy), allowlist

20 `anysphere.okta.com` and your own Okta org, for example `yourorg.okta.com`.

21 Every team downloads the Okta Verify package from `anysphere.okta.com`,

22 whatever org it signs in to.

23 

24## 1. Configure your Okta org

25 

26Do this in the Okta Admin Console before anyone uses FastPass on a Grok Bot

27computer.

28 

291. Enable the **Okta Verify for Linux** feature (`ftrl2df4GICAJ5xl1QSU`) under

30 **Settings** > **Features**, or with

31 `POST /api/v1/features/ftrl2df4GICAJ5xl1QSU/enable`.

322. Under **Security** > **Authenticators**, confirm the **Okta Verify**

33 authenticator is active and its `signed_nonce` method is active.

343. Confirm the authentication policies for the Okta Dashboard and each app the

35 Bot signs in to allow FastPass or Okta Verify as a factor. Two-factor

36 assurance that includes Okta Verify is typical.

374. Keep **Email** or **Password** available as a factor. The first Okta Verify

38 enrollment on each computer needs it.

39 

40## 2. Add the Team Setup Script

41 

42The setup script is part of the Grok Bot computer image. It installs a pinned

43Okta Verify 7.1.3.0 build, then starts the Okta services, a login session shim,

44and the `com-okta-authenticator` URI handler. When a sign-in asks for FastPass,

45the handler opens the Okta Verify window on the desktop of the Bot that's

46signing in. The script is idempotent and holds no embedded certificates or

47secrets.

48 

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

50 and find **Team Setup Scripts** under **Bot Computers**.

51 

522. Create a manifest, or open an existing one, and add a script entry, for

53 example with the ID `okta-verify`.

54 

553. Set the **Setup Script** and **Check Script**, passing your org URL to both:

56 

57 ```bash

58 # Setup Script

59 setup-okta.sh --org-url=https://yourorg.okta.com

60 # Check Script

61 setup-okta.sh --check --org-url=https://yourorg.okta.com

62 ```

63 

644. Select **Save**.

65 

66The entry names the command, not a path, so it runs from any working directory.

67Computers run it at every start and on the periodic refresh. The services it

68starts don't survive a restart, so the check reruns setup when they're down. A

69failed setup is reported and never blocks the computer. See

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

71 

72### Okta Verify settings

73 

74The script writes the settings you pass to the Okta Verify admin settings file,

75`/etc/okta/adminconfig.json`. Pass the same options on the Check Script line,

76so the check confirms they're in place. The common ones:

77 

78| Option | Values | What it does |

79| --- | --- | --- |

80| `--org-url` | `https://yourorg.okta.com` | Prefills your org on the sign-in URL screen. It doesn't change where the package downloads from. |

81| `--enrollment-options` | `Default`, `Enabled`, `SilentEnrollmentDisabled`, `Disabled` | Controls how accounts enroll. |

82| `--user-verification-enrollment` | `Disabled`, `Deferred`, `Preferred`, `Required` | Controls passcode setup at enrollment. `Disabled` skips it, so sign-ins fail if your org requires user verification. |

83| `--auto-registration` | `DEVICE` | Turns on userless device registration. |

84 

85For the full list, see [Setup script reference](#setup-script-reference).

86 

87## 3. Enroll Okta Verify

88 

89Each computer enrolls once. Enrollment is stored in the computer's home

90directory and survives restarts.

91 

921. Open the Okta Verify window on your desktop. From a terminal on the

93 computer, run `setup-okta.sh --display :N`, where `:N` is your desktop's

94 display (the value of `$DISPLAY`).

952. Select **Get started**, then **Next**.

963. Enter `https://yourorg.okta.com` and select **Next**.

974. Sign in in the browser with whatever your policy allows, such as password

98 and email.

995. Create an Okta Verify passcode. Store it privately, and never commit it or

100 paste it into chat.

1016. Finish when Okta Verify shows **Account added** with passcode confirmation

102 on.

103 

104## 4. Verify FastPass

105 

1061. Open a fresh browser session on the computer and go to

107 `https://yourorg.okta.com`.

1082. Enter the username and select **Use Okta FastPass**.

1093. When Okta Verify asks for the passcode, enter it within about 30 seconds.

110 Type it or use right-click > **Paste**. Pressing Ctrl+V crashes the Linux

111 app.

1124. In the Admin Console, open **Reports** > **System Log** and confirm both

113 events:

114 * `user.authentication.auth_via_mfa` with **SUCCESS** and factor

115 **SIGNED\_NONCE**

116 * `user.session.start` with **SUCCESS** for the Okta Dashboard

117 

118## Setup script reference

119 

120The script lives at `/usr/local/bin/setup-okta.sh` on every Grok Bot computer.

121Run `setup-okta.sh --help` on a computer to print every option and Okta Verify

122setting it supports, with accepted values.

123 

124## Limitations

125 

126* Okta Verify runs as one window per computer user. While the window is open on

127 one Bot's desktop, a FastPass sign-in from another Bot's desktop on the same

128 computer shows its prompt in that window. The window closes after 5 minutes

129 without a sign-in.

130* Okta doesn't receive a device manufacturer or model from Grok Bot computers.

131 FastPass works without them.

132* Ctrl+V in the passcode prompt crashes Okta Verify on Linux. Use right-click >

133 **Paste** instead.

134 

135## Related pages

136 

137* [Configure identity and access](/grok-bot/identity-and-access)

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

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

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

38In the Grok Bot desktop app, open **Settings → Computer** and, under **Your computer**,38In the Grok Bot desktop app, open **Settings → Computer** and, under **Your computer**,

39turn on **Route traffic through this computer**. The route uses the current device's39turn on **Route traffic through this computer**. The route uses the current device's

40network and IP address. It stops when the setting is turned off or an Enterprise40network and IP address. It stops when the setting is turned off or an Enterprise

41admin disables **Allow Local Egress Routing**.41admin sets local egress routing to **Always off**. A

42[group setting](/grok-bot/teams-and-enterprises#group-settings) can still allow

43routing for that group's members.

42 44 

43The route does not open your private network to the Bot. Sites that resolve to45The route does not open your private network to the Bot. Sites that resolve to

44a private or VPN address are blocked unless they have been allowed for your46a private or VPN address are blocked unless they have been allowed for your

46To reach private services,48To reach private services,

47[install a networking client with Team Setup](#install-a-networking-client-with-team-setup).49[install a networking client with Team Setup](#install-a-networking-client-with-team-setup).

48 50 

49Each member controls their own desktop route. Enterprise admins can remove this51Each member controls their own desktop route. Enterprise admins can lock it for

50option for the whole team from52the whole team with **Always on** or **Always off** from

51[Grok Bot in the Cursor dashboard](https://cursor.com/dashboard/bot). See53[Grok Bot in the Cursor dashboard](https://cursor.com/dashboard/bot). See

52[Route traffic through your desktop](/grok-bot/settings-and-notifications#route-traffic-through-your-desktop).54[Route traffic through your desktop](/grok-bot/settings-and-notifications#route-traffic-through-your-desktop).

53 55 

166| WhatsApp Business | `ah-api.merge.dev`, `graph.facebook.com` |166| WhatsApp Business | `ah-api.merge.dev`, `graph.facebook.com` |

167| Zoho CRM, Zoho Books | `ah-api.merge.dev`, plus your Zoho data center's accounts host and API host, for example `accounts.zoho.com` and `www.zohoapis.com` for the United States (`.eu`, `.in`, `.com.au`, `.jp`, `.sa`, `.uk`, `.ae`, `.sg`, or `accounts.zohocloud.ca` and `www.zohoapis.ca` for Canada) |167| Zoho CRM, Zoho Books | `ah-api.merge.dev`, plus your Zoho data center's accounts host and API host, for example `accounts.zoho.com` and `www.zohoapis.com` for the United States (`.eu`, `.in`, `.com.au`, `.jp`, `.sa`, `.uk`, `.ae`, `.sg`, or `accounts.zohocloud.ca` and `www.zohoapis.ca` for Canada) |

168| Zoho Desk | `ah-api.merge.dev`, plus your data center's accounts host and its Desk host, for example `accounts.zoho.com` and `desk.zoho.com` |168| Zoho Desk | `ah-api.merge.dev`, plus your data center's accounts host and its Desk host, for example `accounts.zoho.com` and `desk.zoho.com` |

169| Microsoft Power BI | `api.powerbi.com` |

170| Databricks Genie | Your Databricks workspace host, as entered by your team admin in the plugin's setup, for example `dbc-a1b2c3d4-e5f6.cloud.databricks.com` |

171| Google BigQuery | `bigquery.googleapis.com` |

172| Asana | `mcp.asana.com` |

173| Vanta | The host for the region picked at sign-in: `mcp.vanta.com` (United States), `mcp.eu.vanta.com` (Europe), or `mcp.aus.vanta.com` (Australia) |

174| Shop Pay | `mcp.shop.com` |

169 175 

170Other connectors in the Team Marketplace are checked by the host in their176Other connectors in the Team Marketplace are checked by the host in their

171server address, which is shown on the dashboard's177server address, which is shown on the dashboard's

291 keeps it out of the transcript and away from the model. A card saved in Vault297 keeps it out of the transcript and away from the model. A card saved in Vault

292 fills at checkout without a separate approval each time, so members who want298 fills at checkout without a separate approval each time, so members who want

293 to approve each payment should not save the card. Vault is not available on299 to approve each payment should not save the card. Vault is not available on

294 shared Bots. Passwords and one-time codes never belong in ordinary chat. See300 Team Bots. Passwords and one-time codes never belong in ordinary chat. See

295 [Store secrets securely](/grok-bot/vault).301 [Store secrets securely](/grok-bot/vault).

296 302 

297To end a member's current work, an organization admin terminates the member's303To end a member's current work, an organization admin terminates the member's

376provider on the [sub-processor list](https://trust.cursor.com/subprocessors).382provider on the [sub-processor list](https://trust.cursor.com/subprocessors).

377Usage and spending views record this activity as Grok Bot usage rather than by383Usage and spending views record this activity as Grok Bot usage rather than by

378model. See384model. See

379[Which AI models power Grok Bot?](https://cursor.com/help/grok-bot/models).385[Can I pick the model?](/grok-bot/faq#can-i-pick-the-model).

380 386 

381* **The team model allowlist does not govern Grok Bot.** Grok Bot uses387* **The team model allowlist does not govern Grok Bot.** Grok Bot uses

382 SpaceXSI first-party models and may use third-party models regardless of your388 SpaceXSI first-party models and may use third-party models regardless of your

16user, every Bot shares that computer. Treat a login or file on the computer as16user, every Bot shares that computer. Treat a login or file on the computer as

17available to every Bot that user runs. When a workload needs its own computer17available to every Bot that user runs. When a workload needs its own computer

18and credential set, give it its own Cursor user. A teammate's18and credential set, give it its own Cursor user. A teammate's

19[shared Bot](/grok-bot/team-bots) usually works on a user's computer during19[Team Bot](/grok-bot/team-bots) usually works on a user's computer during

20that user's own chat with it.20that user's own chat with it.

21 21 

22### What can a Bot access?22### What can a Bot access?

144Grok Bot. Grok Bot manages model selection, and there is no customer-facing144Grok Bot. Grok Bot manages model selection, and there is no customer-facing

145model picker. If your contract restricts subprocessors, contact your account145model picker. If your contract restricts subprocessors, contact your account

146team. See146team. See

147[Which AI models power Grok Bot?](https://cursor.com/help/grok-bot/models).147[Can I pick the model?](/grok-bot/faq#can-i-pick-the-model).

148 148 

149### Where do Grok Bot computers run?149### Where do Grok Bot computers run?

150 150 

118routing, send a message from this computer to route through it instead. If the118routing, send a message from this computer to route through it instead. If the

119setting asks you to **Update Bot's computer**, do that first.119setting asks you to **Update Bot's computer**, do that first.

120 120 

121The setting applies to one desktop. If your Enterprise admin turns off **Allow121The setting applies to one desktop. Your Enterprise admin can lock it:

122Local Egress Routing**, the toggle turns off and locks. The setting reads122 

123`Your team admin has turned off local traffic routing. Grok Bot's computer routes traffic through the cloud.`123* **Always off**: the toggle turns off and locks. The setting reads

124and the switch shows `Disabled by your admin. You can't turn this on.` Any124 `Your team admin has turned off local traffic routing. Grok Bot's computer routes traffic through the cloud.`

125active route stops within five minutes. Your choice is preserved and takes125 and the switch shows `Disabled by your admin. You can't turn this on.`

126effect again if the admin re-allows local egress.126 Traffic goes through the cloud. Your choice is kept and applies again if the

127 admin changes the mode to **Members decide**.

128* **Always on**: the toggle turns on and locks with

129 `Required by your admin. You can't turn this off.` When none of your

130 computers is connected, Grok Bot's computer refuses routed sites. It does not

131 use the cloud instead. If Grok Bot's computer needs an update first, select

132 **Update Bot's computer**. Until you update, Grok Bot's computer routes

133 traffic through the cloud.

127 134 

128For private network options and their tradeoffs, see135For private network options and their tradeoffs, see

129[Connect to private networks](/grok-bot/private-networks).136[Connect to private networks](/grok-bot/private-networks).

191for you.198for you.

192 199 

193For how plans, weekly usage, and on-demand spend work, see200For how plans, weekly usage, and on-demand spend work, see

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

195 202 

196### Use a usage limit reset203### Use a usage limit reset

197 204 

289* [Approvals, security, and privacy](/grok-bot/approvals-security-and-privacy)296* [Approvals, security, and privacy](/grok-bot/approvals-security-and-privacy)

290* [Grok Bot for teams and enterprises](/grok-bot/teams-and-enterprises)297* [Grok Bot for teams and enterprises](/grok-bot/teams-and-enterprises)

291* [Grok Bot security](/grok-bot/security)298* [Grok Bot security](/grok-bot/security)

292* [Plans and billing](https://cursor.com/help/grok-bot/plans)299* [Plans and billing](https://grok.com/help/grok-bot/plans)

293* [Delete your Grok Bot account](https://cursor.com/help/grok-bot/delete-account)300* [Delete your Grok Bot account](https://grok.com/help/grok-bot/delete-account)

294* [Remove access and working data](/grok-bot/approvals-security-and-privacy#remove-access-and-working-data)301* [Remove access and working data](/grok-bot/approvals-security-and-privacy#remove-access-and-working-data)

218* **Delete routine** (the trash icon), which asks you to confirm218* **Delete routine** (the trash icon), which asks you to confirm

219 219 

220You can also right-click a routine to **Pause** or **Resume** it, **Test** it,220You can also right-click a routine to **Pause** or **Resume** it, **Test** it,

221**Edit** it in chat, or **Delete** it. On a shared Bot, the same menu can also221**Edit** it in chat, or **Delete** it. On a Team Bot, the same menu can also

222show **Who can use this routine?**: choose **Only me** to keep the routine to222show **Who can use this routine?**: choose **Only me** to keep the routine to

223yourself, or **Everyone with access** to run it for everyone who can use the223yourself, or **Everyone with access** to run it for everyone who can use the

224Bot.224Bot.

267Bot to widen schedules and narrow Slack triggers before you raise a plan or an267Bot to widen schedules and narrow Slack triggers before you raise a plan or an

268on-demand limit. A routine that never runs doesn't spend usage; **Test** does,268on-demand limit. A routine that never runs doesn't spend usage; **Test** does,

269because it performs the work. See [Plans and269because it performs the work. See [Plans and

270billing](https://cursor.com/help/grok-bot/plans) for weekly usage and the270billing](https://grok.com/help/grok-bot/plans) for weekly usage and the

271on-demand monthly limit.271on-demand monthly limit.

272 272 

273To control unattended usage, Grok Bot may ask whether to keep routines running273To control unattended usage, Grok Bot may ask whether to keep routines running

286* Re-test after a website, app, or source format changes.286* Re-test after a website, app, or source format changes.

287 287 

288For more on schedules, Slack triggers, and webhooks, see288For more on schedules, Slack triggers, and webhooks, see

289[Routines](https://cursor.com/help/grok-bot/routines). See [Settings and notifications](/grok-bot/settings-and-notifications) for time zone289[Routines](https://grok.com/help/grok-bot/routines). See [Settings and notifications](/grok-bot/settings-and-notifications) for time zone

290and usage controls, and [Approvals, security, and290and usage controls, and [Approvals, security, and

291privacy](/grok-bot/approvals-security-and-privacy) for automation boundaries.291privacy](/grok-bot/approvals-security-and-privacy) for automation boundaries.

8private.8private.

9 9 

10Team Bots always run in the cloud. A Bot that runs on your own computer can't10Team Bots always run in the cloud. A Bot that runs on your own computer can't

11be shared. A few screens, such as **Browse shared Bots**, still say Team Bots.11be shared. A few screens, such as **Browse shared Bots**, still say shared

12They're the same thing.12Bots. They're the same thing.

13 13 

14## Who can use Team Bots?14## Who can use Team Bots?

15 15 

16Team Bots are available on Team and Enterprise plans, for members who have Grok16Team Bots are available on Team and Enterprise plans, for members who have Grok

17Bot. Choose **+** in17Bot. Choose **+** in

18the sidebar to see **Create a Bot** and **Browse shared Bots**. If **Browse18the sidebar to see **Create a Bot** and **Browse shared Bots**. If **Browse

19Team Bots** isn't there, you aren't on a Cursor team, or your Grok Bot app19shared Bots** isn't there, you aren't on a Cursor team, or your Grok Bot app

20needs an update.20needs an update.

21 21 

22In Slack, members of your workspace who aren't on the team can sometimes use a22In Slack, members of your workspace who aren't on the team can sometimes use a

157Bots**. See [How do admins manage Team Bots?](#how-do-admins-manage-team-bots)157Bots**. See [How do admins manage Team Bots?](#how-do-admins-manage-team-bots)

158 158 

159The app's row shows whose account the Bot uses. To stop, choose **Stop159The app's row shows whose account the Bot uses. To stop, choose **Stop

160sharing**, or remove the app. Teammates then connect their own.160sharing**, or remove the app. Teammates then connect their own. If a shared app

161needs reconnecting, only the Manager whose account it is can reconnect it,

162under the Bot's **Shared connectors**.

161 163 

162## Which computer does a Team Bot use?164## Which computer does a Team Bot use?

163 165 

219Slack thread, the Bot follows that thread and answers later replies without an221Slack thread, the Bot follows that thread and answers later replies without an

220@mention.222@mention.

221 223 

222Link your Slack account so the Bot knows who you are and can use your apps.224Link your Slack account so the Bot knows who you are and can use your apps. If

223Open **Settings** > **General** > **Team Bots** and choose **Link**. If you225you message a Bot before you link, it asks you to connect:

224message the Bot before you link, it replies with steps to link your account.226 

2271. Choose **Connect**. Your browser opens cursor.com.

2282. Sign in with the Cursor account on the Bot's team, then choose **Link

229 Account**. If you're already signed in, you go straight to that page.

2303. Choose **Open Slack** to return to Slack. The Bot answers the message you

231 sent.

232 

233You link once per Slack workspace. The link covers every Bot in that workspace,

234and Cloud Agents you start from Slack. To link before a Bot asks, open

235**Settings** > **General** > **Team Bots** and choose **Link**, or choose Slack

236under [Integrations](https://cursor.com/dashboard/integrations?view=slack-management)

237in the Cursor dashboard. There, a workspace marked **Connection expired** needs

238**Reconnect**, and a workspace that isn't listed needs **Add to another

239workspace**, or **Install Cursor in Slack** if none are linked.

225 240 

226## Who can talk to a Team Bot in Slack?241## Who can talk to a Team Bot in Slack?

227 242 

299with Team Bots and answer their **Allow** cards. A Team Bot can't be your314with Team Bots and answer their **Allow** cards. A Team Bot can't be your

300[primary Bot](/grok-bot/bots#your-primary-bot).315[primary Bot](/grok-bot/bots#your-primary-bot).

301 316 

317Sharing and browsing on the phone need Grok Bot 1.19.0 or later on iPhone and

318Android. Earlier versions still open the Team Bots already in your list.

319 

302To remove a teammate's Bot from your list, touch and hold it and choose320To remove a teammate's Bot from your list, touch and hold it and choose

303**Remove from sidebar**.321**Remove from sidebar**.

304 322 

377| **This Bot's owner has reached their usage limit** | This reply was billed to the owner's account, and the owner's usage ran out. Ask the owner to check their plan. |395| **This Bot's owner has reached their usage limit** | This reply was billed to the owner's account, and the owner's usage ran out. Ask the owner to check their plan. |

378| **This conversation can't run on your computer because your privacy mode is stricter than the bot owner's.** | Your privacy mode setting is stricter than the owner's, so this chat can't use your computer. |396| **This conversation can't run on your computer because your privacy mode is stricter than the bot owner's.** | Your privacy mode setting is stricter than the owner's, so this chat can't use your computer. |

379| In Slack, the Bot asks you to link a Cursor account | Link your Slack account under **Settings** > **General** > **Team Bots**, using the Cursor account on the Bot's team. |397| In Slack, the Bot asks you to link a Cursor account | Link your Slack account under **Settings** > **General** > **Team Bots**, using the Cursor account on the Bot's team. |

398| In Slack, the Bot still asks you to connect after you linked | You signed in with a different Cursor account, or linked a different Slack workspace. Unlink under **Settings** > **General** > **Team Bots**, then choose **Connect** again with the account on the Bot's team. |

380| In Slack, **some features will be limited** | The Bot answered you without a linked account. Link one so it knows who you are and can use your apps. |399| In Slack, **some features will be limited** | The Bot answered you without a linked account. Link one so it knows who you are and can use your apps. |

381| In Slack, **I haven't been shared with you yet** | Ask the Bot's owner or a Manager to add you under **Share this Bot**. |400| In Slack, **I haven't been shared with you yet** | Ask the Bot's owner or a Manager to add you under **Share this Bot**. |

382| In Slack, the Bot says it's someone's personal Bot | Only its owner can talk to it. |401| In Slack, the Bot says it's someone's personal Bot | Only its owner can talk to it. |

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

22self-serve Teams. [Admin controls](#admin-controls) marks each one.22self-serve Teams. [Admin controls](#admin-controls) marks each one.

23 23 

24[Plans and billing](https://cursor.com/help/grok-bot/plans) is the canonical24[Plans and billing](https://grok.com/help/grok-bot/plans) is the canonical

25plan and usage matrix.25plan and usage matrix.

26 26 

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

84 an independent review model called Auto Review.84 an independent review model called Auto Review.

85* Administrative control. Team admins can set Team Rules, Cloud Agent85* Administrative control. Team admins can set Team Rules, Cloud Agent

86 delegation, template sharing, and the local execution ceiling. Network86 delegation, template sharing, and the local execution ceiling. Network

87 Controls, Team Setup Scripts, Team Secrets, Allow Local Egress Routing, Allow87 Controls, Team Setup Scripts, Team Secrets, Local Egress Routing, Allow Sudo

88 Sudo on Bot Computers, Action Recording, Enforce Auto-review, Auto-review88 on Bot Computers, Action Recording, Enforce Auto-review, Auto-review rules,

89 rules, and the organization-wide enable switch are Enterprise only.89 and the organization-wide enable switch are Enterprise only.

90 90 

91The pieces fit together like this:91The pieces fit together like this:

92 92 

100 Rules, Cloud Agent delegation, public template sharing, and Execution on100 Rules, Cloud Agent delegation, public template sharing, and Execution on

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

102 the organization-wide enable switch, Network Controls, Team Setup Scripts,102 the organization-wide enable switch, Network Controls, Team Setup Scripts,

103 Team Secrets, Allow Local Egress Routing, Allow Sudo on Bot Computers,103 Team Secrets, Local Egress Routing, Allow Sudo on Bot Computers,

104 Action Recording, Enforce Auto-review, Auto-review rules, and computer104 Action Recording, Enforce Auto-review, Auto-review rules, and computer

105 management. Members never see this page.105 management. Members never see this page.

1063. The Bot. Shell, browser, and computer use inside the hosted computer. A Bot1063. The Bot. Shell, browser, and computer use inside the hosted computer. A Bot

131temporary files when work completes. When a workload needs its own computer and131temporary files when work completes. When a workload needs its own computer and

132credential set, give it its own Cursor user.132credential set, give it its own Cursor user.

133 133 

134[Shared Bots](/grok-bot/team-bots) are the exception to one Bot per user. A134[Team Bots](/grok-bot/team-bots) are the exception to one Bot per user. A

135Bot is either personal or shared: a member shares a cloud-hosted Bot with135Bot is either personal or shared: a member shares a cloud-hosted Bot with

136everyone on the team, or only with certain people and groups, and those members136everyone on the team, or only with certain people and groups, and those members

137can chat with it. Each member's chat is private, including from the owner and137can chat with it. Each member's chat is private, including from the owner and

291include an unsubscribe link, and incoming mail acts only through routines the291include an unsubscribe link, and incoming mail acts only through routines the

292member sets up. Turning it off removes the Bots' email tools and stops email292member sets up. Turning it off removes the Bots' email tools and stops email

293routines; existing addresses keep receiving mail. See293routines; existing addresses keep receiving mail. See

294[Give your Bot an email address](https://cursor.com/help/grok-bot/agent-email).294[Give your Bots an email address](/grok-bot/computer-and-apps#give-your-bots-an-email-address).

295 295 

296#### Connector policy296#### Connector policy

297 297 

323 323 

324#### Allow Local Egress Routing324#### Allow Local Egress Routing

325 325 

326Let members route Grok Bot's web traffic through their own computer. Off326Sets whether Grok Bot's web traffic goes through each member's own computer.

327disables the option in Grok Bot. The switch is under **Bot Computers** on the327Pick a mode in **Local Egress Routing** under **Bot Computers** on the Grok Bot

328Grok Bot page and is on by default. Turning it off stops active routes within328page:

329five minutes. Turning it back on restores each member's previous choice. See329 

330* **Always on** requires routing. Members can't turn it off. When none of a

331 member's computers is connected, Grok Bot refuses the sites it would route.

332 It does not use the cloud instead. Members on an older Grok Bot desktop keep

333 their own choice until they update.

334* **Members decide**, the default, lets each member choose in Grok Bot.

335* **Always off** blocks routing. The server stops routing through a member's

336 computer, even when that member's desktop setting is on.

337 

338Changes apply to new connections. When you change **Always off** back to

339**Members decide**, each member's previous choice applies again. A group can

340allow routing for its members when the team uses **Always off**. See

341[Group settings](#group-settings) and

330[Route traffic through your desktop](/grok-bot/settings-and-notifications#route-traffic-through-your-desktop).342[Route traffic through your desktop](/grok-bot/settings-and-notifications#route-traffic-through-your-desktop).

331 343 

332Available on the Enterprise plan.344Available on the Enterprise plan.

350 362 

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

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

353before running them and ask for approval when needed. This includes shared365before running them and ask for approval when needed. This includes Team

354Bots in chats where nobody can answer an approval, which otherwise run without366Bots in chats where nobody can answer an approval, which otherwise run without

355Auto-review. Turn it on before you rely on team Auto-review rules. A group can367Auto-review. Turn it on before you rely on team Auto-review rules. A group can

356lift the lock for its own members with **Don't enforce for this group**; see368lift the lock for its own members with **Don't enforce for this group**; see

6635. Disable Cloud Agent spawning if you do not need delegation.6755. Disable Cloud Agent spawning if you do not need delegation.

6646. Keep public template sharing off unless members should publish Bot6766. Keep public template sharing off unless members should publish Bot

665 templates outside the team.677 templates outside the team.

6667. Add team Auto-review rules. Enterprise only. Cover actions that should6787. Set Bot sharing to **Admins only** if Team Bots should go through a review

679 before teammates can use them. Team Bots carry their owner's apps, secrets,

680 and files into every teammate's chat.

6818. Keep Allow Shared Logins off unless a Team Bot should act through one

682 Manager's account for everyone who uses it.

6839. Add team Auto-review rules. Enterprise only. Cover actions that should

667 always ask first or can proceed automatically. Production deployments,684 always ask first or can proceed automatically. Production deployments,

668 external email, payments, and accepting legal terms are good **Ask first**685 external email, payments, and accepting legal terms are good **Ask first**

669 examples. Keep automatic rules narrow.686 examples. Keep automatic rules narrow.

6708. Gate sign-in to managed devices through your identity provider. Grok Bot68710. Gate sign-in to managed devices through your identity provider. Grok Bot

671 sign-in uses your SSO, so a device-aware sign-in policy applies to it. This688 sign-in uses your SSO, so a device-aware sign-in policy applies to it. This

672 gates sign-in, not the hosted computer itself.689 gates sign-in, not the hosted computer itself.

673 690 

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

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

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

746* [Plans and billing](https://cursor.com/help/grok-bot/plans)763* [Plans and billing](https://grok.com/help/grok-bot/plans)

747* [Privacy and Data Governance](https://cursor.com/docs/enterprise/privacy-and-data-governance)764* [Privacy and Data Governance](https://cursor.com/docs/enterprise/privacy-and-data-governance)

748 765 

749Contact your Cursor account team about Enterprise plan enablement, egress766Contact your Cursor account team about Enterprise plan enablement, egress

311 311 

312## A secret value seems missing312## A secret value seems missing

313 313 

314A saved value is not shown again, including in Shell. On a shared Bot, if the314A saved value is not shown again, including in Shell. On a Team Bot, if the

315name is still listed under **Secrets**, it is still stored. See315name is still listed under **Secrets**, it is still stored. See

316[Vault](/grok-bot/vault).316[Vault](/grok-bot/vault).

317 317 

28 28 

29Vault covers your whole account: everything you save is available to every Bot29Vault covers your whole account: everything you save is available to every Bot

30on your account, and you can't limit an item to one Bot. Your Vault isn't30on your account, and you can't limit an item to one Bot. Your Vault isn't

31available on [shared Bots](/grok-bot/team-bots): a shared Bot can't use the31available on [Team Bots](/grok-bot/team-bots): a Team Bot can't use the

32logins, cards, or contact info you saved. Add keys to a shared Bot under32logins, cards, or contact info you saved. Add keys to a Team Bot under

33**Secrets** instead. See [API keys and other33**Secrets** instead. See [API keys and other

34secrets](#api-keys-and-other-secrets).34secrets](#api-keys-and-other-secrets).

35 35 

36A shared Bot can have logins of its own. If you own or manage it, choose the36A Team Bot can have logins of its own. If you own or manage it, choose the

37wrench, **Manage**, and under **General** find **Bot's accounts**. Choose37wrench, **Manage**, and under **General** find **Bot's accounts**. Choose

38**Add**, then **Bot's vault login**, enter the **Website**, **Username or38**Add**, then **Bot's vault login**, enter the **Website**, **Username or

39email**, and **Password**, and choose **Save login**. The Bot can sign in with39email**, and **Password**, and choose **Save login**. The Bot can sign in with

40these logins for anyone on your team, and only managers can see or change40these logins for anyone on your team, and only managers can see or change

41them. To change or remove one, open its **More actions** menu and choose41them. To change or remove one, open its **More actions** menu and choose

42**Edit** or **Remove**. A shared Bot's logins don't appear in your own42**Edit** or **Remove**. A Team Bot's logins don't appear in your own

43**Settings → Vault**.43**Settings → Vault**.

44 44 

45## Add, import, and change items45## Add, import, and change items

54 * For contact info, enter the name, address, phone, and email, then choose54 * For contact info, enter the name, address, phone, and email, then choose

55 **Save contact info**.55 **Save contact info**.

56 56 

57On Grok Bot for iPhone 1.18.0 with iOS 26 or later, **New item** > **Login**

58shows only a back button, so a login typed there can't be saved. Cards and

59contact info aren't affected. This is fixed in iPhone 1.19.0; update Grok Bot

60from the App Store.

61 

57Under **Hints**, tell your Bots when to use an entry, such as “Use for work62Under **Hints**, tell your Bots when to use an entry, such as “Use for work

58purchases.” A Bot follows the hint when it chooses between entries.63purchases.” A Bot follows the hint when it chooses between entries.

59 64 

137securely**, and the card then says **Saved** and **Saved securely and kept142securely**, and the card then says **Saved** and **Saved securely and kept

138private**. The value isn't written into the chat or shown to the Bot.143private**. The value isn't written into the chat or shown to the Bot.

139 144 

140On a [shared Bot](/grok-bot/team-bots) you own or manage, you can also add a145On a [Team Bot](/grok-bot/team-bots) you own or manage, you can also add a

141secret from the Bot's details. Open **Secrets**, choose **Add secret**, enter an146secret from the Bot's details. Open **Secrets**, choose **Add secret**, enter an

142environment variable name, a short description, and the value, then choose147environment variable name, a short description, and the value, then choose

143**Save secret**. The description is visible to the Bot; the value is not.148**Save secret**. The description is visible to the Bot; the value is not.

144Secrets on a shared Bot are used in every teammate's chat, so only add keys149Secrets on a Team Bot are used in every teammate's chat, so only add keys

145you're happy for everyone who can chat with the Bot to use.150you're happy for everyone who can chat with the Bot to use.

146 151 

147A credential your company's setup scripts need, such as a license key for a152A credential your company's setup scripts need, such as a license key for a

162 their last four digits.167 their last four digits.

163* The secure secret card does not show the value after **Saved**. The footer168* The secure secret card does not show the value after **Saved**. The footer

164 says **Stored securely, never shown to your Bot**.169 says **Stored securely, never shown to your Bot**.

165* On a shared Bot, **Secrets** lists the name and description only. It never170* On a Team Bot, **Secrets** lists the name and description only. It never

166 shows the value again, including in Shell.171 shows the value again, including in Shell.

167* To change a value there, choose **Replace**, paste the new value, and choose172* To change a value there, choose **Replace**, paste the new value, and choose

168 **Replace value**. You can't read the old value back.173 **Replace value**. You can't read the old value back.

169 174 

170If a save fails, the form says **The secret was not saved. Try again.** If a175If a save fails, the form says **The secret was not saved. Try again.** If a

171shared Bot's **Secrets** list says **Something went wrong. Try again.**, choose176Team Bot's **Secrets** list says **Something went wrong. Try again.**, choose

172**Try Again**. **No secrets yet** means that Bot has no saved names, not that a177**Try Again**. **No secrets yet** means that Bot has no saved names, not that a

173value is hidden.178value is hidden.

174 179 

180the secure card, under **Secrets**, or in Vault. See [Update, recover, or reset185the secure card, under **Secrets**, or in Vault. See [Update, recover, or reset

181the computer](/grok-bot/computer-and-apps#update-recover-or-reset-the-computer).186the computer](/grok-bot/computer-and-apps#update-recover-or-reset-the-computer).

182 187 

183Shell not printing a secret does not mean it was wiped. On a shared Bot, if the188Shell not printing a secret does not mean it was wiped. On a Team Bot, if the

184name is still listed under **Secrets**, the value is still stored. If a shared189name is still listed under **Secrets**, the value is still stored. If a Team

185Bot's secret name is gone and you did not choose **Remove**:190Bot's secret name is gone and you did not choose **Remove**:

186 191 

1871. Fully quit Grok Bot and reopen it. On Mac, choose **Quit** from the menu bar,1921. Fully quit Grok Bot and reopen it. On Mac, choose **Quit** from the menu bar,

208 **Remove**.213 **Remove**.

209 214 

210**Settings → Vault** also lists **Payment accounts**, wallets you can connect,215**Settings → Vault** also lists **Payment accounts**, wallets you can connect,

211such as Link or X Money, and **Default payment method**, which Grok Bot pays216such as Link, X Money, or Shop Pay, and **Default payment method**, which Grok

212with first. On the phone, connected wallets are under **Payments** in217Bot pays with first. On the phone, connected wallets are under **Payments** in

213**Settings → Vault**: a connected wallet shows **Connected** and the account218**Settings → Vault**: a connected wallet shows **Connected** and the account

214it's signed in to, and one you haven't connected shows **Connect**.219it's signed in to, and one you haven't connected shows **Connect**.

215 220 

239## Related pages244## Related pages

240 245 

241* [Use the computer and apps](/grok-bot/computer-and-apps)246* [Use the computer and apps](/grok-bot/computer-and-apps)

242* [Shared Bots](/grok-bot/team-bots)247* [Team Bots](/grok-bot/team-bots)

243* [Approvals, security, and privacy](/grok-bot/approvals-security-and-privacy)248* [Approvals, security, and privacy](/grok-bot/approvals-security-and-privacy)

244* [Store secrets securely](https://cursor.com/help/grok-bot/secrets)249* [Store secrets securely](https://grok.com/help/grok-bot/secrets)