Documentation 2026-10-27 23:58 UTC to 2026-10-28 23:01 UTC

29 29 

30## Review an action30## Review an action

31 31 

32When an action needs approval, the conversation shows the proposed operation32Auto Review checks each action your Bot is about to take, for example before it

33and its inputs. Review the target, scope, and values before approving.33runs a command, uses a connected app, or uses its computer. Most actions run on

34**Allow once** lets the Bot continue with that action, **Always allow** can34their own. When one needs your OK, the Bot shows an approval card in your chat

35save a matching rule, and **Deny** blocks it. The controls are the same on35with the proposed operation and its inputs, and waits for your answer. An action

36iPhone.36that matches one of your **Ask first** rules always gets a card. Review the

37 37target, scope, and values before approving.

38An Auto Review approval from a chat you are in waits for your answer. An38 

39approval from work that started without you, such as a routine, a trigger, or a39Auto Review takes into account what you asked for in your own messages. Text

40message from another Bot, expires after about 10 minutes; the card then shows40from somewhere else, such as an email or a web page, doesn't count as your

41**Expired**, and the action does not run. An expired card may offer **Always allow this in41request. Some cards carry a warning, such as **This can't be undone**, **This

42the future**, which adds the proposed rule to your **Allow automatically** rules42changes sign-in or security settings**, or **This shares your data outside this

43without running the expired action. To finish the task, ask the Bot to try43chat**.

44again.44 

45* **Allow once:** the Bot does the action now. No rule is saved.

46* **Always allow:** the Bot does the action now and saves an Allow rule to your

47 Custom Rules, so similar actions run on their own. The card shows **Saved to

48 Custom Rules**.

49* **Deny:** the Bot doesn't do it. It won't try that action again or ask you

50 about it until you send another message.

51 

52Some cards use other labels. A card for a terminal command shows **Allow** and

53**Skip**, plus **Manage settings**, which opens your Auto Review settings. A

54card paused by one of your **Ask first** rules shows **Allow** and **Not now**,

55and **Edit rule** opens your Custom Rules. When the card has no rule to offer,

56you see **Allow** instead of **Allow once**, and no **Always allow**. On the

57phone, tap a card to see the full request and all of its buttons.

58 

59For email the Bot sends from [its own

60address](/grok-bot/computer-and-apps#give-your-bots-an-email-address):

61 

62* When you ask for an email in chat, it goes out once Auto Review allows it. If

63 Auto Review needs you, you see an approval card first.

64* Email from a routine, an incoming message, or other work you didn't start

65 with that request waits as a draft until you press **Send**.

66* A forward, or an email with an attachment Auto Review can't fully read,

67 always waits for your OK.

45 68 

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

47to explain it in plain language or produce a draft first.70to explain it in plain language or produce a draft first.

48 71 

72### If you don't answer

73 

74When the work started from a chat message, the card waits for an answer and

75doesn't expire on a timer. When a routine, an incoming message, or other

76background work raised the card, it expires after 30 minutes. If you send a new

77message instead of answering, any open card in that chat closes, and changing

78your Auto Review settings also closes open cards.

79 

80A closed card shows **Expired** and says the Bot didn't do the action. If the

81card offered a rule, you can still press **Always allow next time**; the Bot

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

83Bot to try again.

84 

85### Shared Bots and group chats

86 

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

88own 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 asked

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

91can approve; everyone else sees who the card is waiting on, and group chat cards

92don't offer **Always allow**.

93 

94An approval card asks whether the Bot may take an action. A [Secure

95Form](/grok-bot/vault#secure-forms) collects a password, key, or other secret,

96and a connect card asks you to sign in to an [app](/grok-bot/computer-and-apps#connect-an-app)

97so the Bot can use it.

98 

49## Configure Auto Review99## Configure Auto Review

50 100 

51With Auto Review on, Grok Bot evaluates tool calls and computer actions before101Auto Review is on by default. For each action, it either lets the action run or

52they run. Open **Settings → General → Auto-review** to add rules.102has the Bot ask you first, and your Custom Rules can change that choice for the

103actions you care about. Built-in safety checks always apply, whatever your rules

104say.

105 

106The **Auto-review** switch is in **Settings → General**, under **Bot**; on iPhone

107and Android, it's in the **Bot** group of **Settings**. With Auto Review off,

108the Bot runs actions without checking them first, and your Custom Rules are

109hidden and not used but kept; turn it back on to use them again.

110 

111While Auto Review is on, **Custom Rules** appears under the switch on desktop;

112on the phone, tap **Custom Rules** in the **Bot** group. To add a rule:

113 

1141. Under **When Grok Bot wants to:**, describe one action in plain words, like

115 “reply to emails for me.”

1162. Under **It should:**, choose **Allow automatically** or **Ask first**.

1173. Press **Add Rule**.

118 

119On desktop, use the edit button next to a rule, make your change, and press

120**Save Rule**, or press **Cancel** to keep it as it was; use the delete button to

121remove it. On the phone, tap a rule to open it, then press **Save Rule** or

122**Delete Rule**.

53 123 

54* **Ask first** rules always stop matching actions for you.124* **Ask first** rules always stop matching actions for you.

55* **Allow automatically** rules let matching actions proceed only when the125* **Allow automatically** rules let matching actions proceed only when the

56 automated review does not identify another reason to stop.126 automated review does not identify another reason to stop.

57* If both kinds of rule match, **Ask first** wins.127* If both kinds of rule match, **Ask first** wins.

58 128 

59If your team admin enforces Auto Review, the same table also shows locked team129You can have up to 20 **Allow automatically** rules and up to 20 **Ask first**

60rules that you cannot edit or delete. Your own rules apply on top and can only130rules, and each rule can be up to 1,000 characters. If you already have 20 Allow

61make behavior stricter. See131rules, **Always allow** on a card removes your oldest Allow rule to make room

132and tells you which rule it removed.

133 

134If your admin requires Auto Review, the switch stays on and shows **Required by

135your admin. You can't turn this off.** Team rules appear in the same table with

136**Required by your admin. You can't edit or delete this rule.** Team rules always

137apply; your own rules apply only to you, on top of the team's, and can only make

138behavior stricter. Your team can also share rules that apply to your Bots

139instead of your own rules; built-in safety checks still apply. See

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

63 141 

64Write narrow rules around a known action and scope:142Write one short, narrow rule for each action, around a known action and scope:

65 143 

66* Ask first before sending any external email.144* Ask first before sending any external email.

67* Ask first before changing a production dashboard.145* Ask first before changing a production dashboard.

74Personal Auto-review rules are saved to your account, so they apply from every152Personal Auto-review rules are saved to your account, so they apply from every

75desktop and the mobile app.153desktop and the mobile app.

76 154 

77## Enter passwords and verification codes yourself155## Keep passwords and payment details out of the chat

78 156 

79For passwords, passkeys, two-factor codes, CAPTCHAs, and payment confirmations,157Bots sign in and check out without seeing secret values. A Bot uses a login

80the Bot should hand you control of the computer.158saved in [Vault](/grok-bot/vault) first, then a connected password manager such

159as 1Password, then asks you with a Secure Form. Values from Vault and Secure

160Forms are filled into the page without being shown to the model.

81 161 

821. Choose **Take over** on the request in the conversation, or open the162When a form can't do the step, such as single sign-on, a passkey, a CAPTCHA, an

83 computer and choose **Take control**.163approval on another device, or a bank card verification, the Bot hands you the

164computer:

165 

1661. Choose **Take over** on the request in the conversation, or open the computer

167 and choose **Take control**.

842. Complete the sensitive step.1682. Complete the sensitive step.

853. Choose **I'm done**, then tell the Bot to continue.1693. Choose **I'm done**, then tell the Bot to continue.

86 170 

87Do not send a password or one-time code in ordinary chat.171Do not send a password, one-time code, or API key in ordinary chat. For an API

88 172key or another secret, enter it in the secure secret card when the Bot asks; the

89If the Bot presents a secure secret request for a supported connection, enter

90the value in that request. It is not a general-purpose password manager. The

91value is masked, excluded from the transcript, and not shown to the model.173value is masked, excluded from the transcript, and not shown to the model.

92 174 

93When a web page needs you to type something yourself, such as a login, a175A card saved in Vault fills in at checkout without a separate approval each

94checkout address, or a phone number, the Bot can show a form in the chat, one176time. If you want to approve every payment, don't save the card: leave

95form per step, and fill your answers into the page for you.177**Securely save to Bot's vault** unchecked when you enter it in a Secure Form,

178or remove it in **Settings → Vault**.

96 179 

97If you sign in with a hardware security key, such as a YubiKey, the Bot's180If you sign in with a hardware security key, such as a YubiKey, the Bot's

98browser can use a key plugged into your desktop while **Use hardware security181browser can use a key plugged into your desktop while **Use hardware security

116team's applies. These settings do not prevent the Bot from using its cloud199team's applies. These settings do not prevent the Bot from using its cloud

117computer.200computer.

118 201 

202Your team's cap also applies when a Bot uses apps on your phone. See

203[Let a Bot use your phone's apps](/grok-bot/mobile#let-a-bot-use-your-phones-apps).

204 

119The first time a Bot asks to run a command on your computer, the conversation205The first time a Bot asks to run a command on your computer, the conversation

120shows **Allow Grok Bot and all Bots to run commands on your local computer?**206shows **Allow Grok Bot and all Bots to run commands on your local computer?**

121with **Always allow**, **Allow once**, **Never**, and **Deny once** (Esc).207with **Always allow**, **Allow once**, **Never**, and **Deny once** (Esc).

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

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

148 234 

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

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

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

238with to use.

239 

149## Cursor account and data settings240## Cursor account and data settings

150 241 

151Grok Bot uses Cursor authentication and account data settings.242Grok Bot uses Cursor authentication and account data settings.

185* Review installed connectors and active routines regularly.276* Review installed connectors and active routines regularly.

186* Pause a routine when its source system or expected workflow changes.277* Pause a routine when its source system or expected workflow changes.

187* Preserve source links and an action log for important decisions.278* Preserve source links and an action log for important decisions.

188 

189For information on using Grok Bot in X Chat, see

190[Using Grok Bot in X Chat](https://help.x.com/using-x/about-grok#using-grok-bot-in-x-chat).

15* Approval boundary15* Approval boundary

16* Recurring schedule16* Recurring schedule

17 17 

18Good jobs include **Talent Scout**, **Expense Manager**, and **Bug18Jobs like **Talent Scout**, **Expense Manager**, and **Bug Reproduction** give a

19Reproduction**. A job such as **General Helper** gives the Bot less guidance and19Bot guidance and make its saved context reusable; a **General Helper** does

20makes its saved context harder to reuse.20neither.

21 21 

22Describe the role in operational terms:22Describe the role in operational terms:

23 23 

28 28 

29## Create a Bot29## Create a Bot

30 30 

311. Choose **New chat** (the **+** button) in the sidebar or press `Cmd/Ctrl+N`.311. Choose **New Bot** (the **+** button) at the top of the sidebar, or press

322. In **New chat**, select **Create new Bot**, or type a name and choose32 `Cmd/Ctrl+N`. On a team, the **+** button opens a menu; choose **Create a

33 **Create “name” Bot**.33 Bot**.

343. Grok Bot creates and opens a Bot named **New Bot**.342. In **Create New Bot**, type a name, pick a shape and color for its picture,

35 and choose **Create**.

363. Grok Bot opens a chat with the new Bot.

354. In your first message, give the Bot its job, sources, and approval374. In your first message, give the Bot its job, sources, and approval

36 boundaries, and ask it to remember them. Send a real first task with a38 boundaries, and ask it to remember them. Send a real first task with a

37 clear finish line; see [use cases](/grok-bot/use-cases) for starter prompts.39 clear finish line; see [use cases](/grok-bot/use-cases) for starter prompts.

385. To rename the Bot, add a label, or change its picture, click the Bot's name405. To rename the Bot, add a label, or change its picture, click the Bot's name

39 at the top of the chat to open its details. See [Change a Bot's name,41 at the top of the chat to open its details. See [Change a Bot's name,

40 picture, and what it does](https://cursor.com/help/grok-bot/edit-bot).42 picture, and label](#change-a-bots-name-picture-and-label).

41 43 

42Your existing Bots can also suggest or create a focused Bot when a job should44Your existing Bots can also suggest or create a focused Bot when a job should

43have a long-lived owner. Ask before creating several Bots if you want to keep45have a long-lived owner. Ask before creating several Bots if you want to keep

44the roster small.46the roster small.

45 47 

48## Your primary Bot

49 

50Your primary Bot is your main point of contact. It checks in with you on its

51own and coordinates work with your other Bots.

52 

53If you don't have a primary Bot, Grok Bot shows **Introducing your primary

54Bot**. Choose **Create primary Bot** to add one, or choose **Choose an existing

55Bot**, select one of your Bots, and choose **Confirm**.

56 

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

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

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

60be your primary Bot.

61 

46## Edit a Bot62## Edit a Bot

47 63 

48When you discover a durable preference, boundary, or responsibility that should64When you discover a durable preference, boundary, or responsibility that should

53 approval.”69 approval.”

54* **Task:** “Draft follow-ups for these twelve accounts.”70* **Task:** “Draft follow-ups for these twelve accounts.”

55 71 

56A [Team Bot](/grok-bot/team-bots) also has a description, which its owner or a72The Bot keeps lasting rules in its memory. Personal Bots no longer have a

57manager edits under **About** in the Bot's details.73description or a **Bot settings** page; to change what a Bot does, tell it in

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

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

76 

77### Change a Bot's name, picture, and label

78 

79Each Bot has its own name, picture, and label. Only the Bot's owner can change

80these; **Rename Bot** does not appear for a Bot you don't own.

81 

82To rename a Bot on desktop, right-click it in the sidebar and choose **Rename

83Bot**, or double-click its name in the sidebar. Type the new name and press

84Enter. If the sidebar is collapsed to icons, expand it first. You can also click

85the Bot's name at the top of the chat to open its details, then click the name

86to edit it. The label under the name works the same way; it shows **Add a

87label** when the Bot doesn't have one.

88 

89To change the picture on desktop, open the Bot's details and click its picture,

90then choose a tab:

91 

92* **Bot** changes the look of the Bot's character.

93* **Generate** makes a picture from a short description. Describe the picture,

94 choose **Generate**, then choose **Set avatar**.

95* **Upload** uses your own image. Drag in an image or choose **Browse files**,

96 adjust it, then choose **Set avatar**. The image must be smaller than 25 MB.

58 97 

59## Pin or hide a Bot98On the phone, tap the Bot's name at the top of the chat to open its profile and

99tap **Edit**. Change the **Name** or the **Title** (the phone's name for the

100label) and tap **Done**. To change the picture, tap the picture or **Avatar**

101and choose **Shape**, **Generate**, or **Upload**. **Upload** offers **Choose

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

103to 25 MB.

104 

105## Organize your roster

60 106 

61* **Pin** active Bots to keep them at the top of the sidebar.107* **Pin** active Bots to keep them at the top of the sidebar.

62* Group Bots by project, client, or business with sections: right-click a Bot108* Group Bots by project, client, or business with sections: right-click a Bot

63 and choose **Move to new section**, or **Move to** once you have sections.109 and choose **Move to new section**, or **Move to** once you have sections.

64 Sections sync between desktop and iOS.110 Sections sync between desktop and iOS.

65* **Hide from sidebar** removes a Bot from the main list without deleting its111* **Hide from sidebar** removes a Bot from the main list without deleting its

66 work.112 work or pausing its routines. Hidden Bots stay active and keep their history.

67* Open **Hidden Bots** at the bottom of the sidebar and choose **Show in113* To restore a hidden Bot, open **Hidden Bots** at the bottom of the sidebar and

68 sidebar** from the Bot's menu. On iPhone and Android, choose **Unhide** in114 choose **Show in sidebar** from the Bot's menu. On iPhone and Android, choose

69 the hidden Bots list; when every Bot is hidden, the home screen shows **Show115 **Unhide** in the hidden Bots list; when every Bot is hidden, the home screen

70 Hidden Bots**.116 shows **Show Hidden Bots**.

71 

72Hiding does not pause the Bot or its routines.

73 

74## Duplicate a Bot

75 

76On iPhone, duplicate a Bot when you want the same role as a starting point for

77a different scope—for example, one Account Health Bot per region.

78 117 

79The copy is named "`<name>` copy" and carries the profile, settings, enabled118On iPhone, **Duplicate** a Bot to reuse a role for a different scope, like one

80skills, routines, and avatar. It does not copy conversation history, learned119account-health Bot per region. The copy carries the profile, settings, enabled

81memory, or chat attachments. Rename it and provide the new scope before120skills, routines, and avatar, but not conversation history, learned memory, or

82assigning work.121attachments, so rename it and give it the new scope before assigning work.

83 122 

84## Share a Bot123## Share a Bot

85 124 

86Share a template when someone else should start from the same Bot.125Share a template when someone else should start from the same Bot.

87 126 

881. Open the **Share menu** and choose **Create template**. The Bot builds1271. Click the Bot's name at the top of the chat to open its details, choose

89 the template; when it is ready, **Copy link**, **View template details**,128 **Share**, then choose **Create a copy**. The Bot builds a template and posts

90 and **Update template** appear.129 it in the chat.

912. Choose who can open the link: **Public link** or **Team-only**. Accounts on1302. Choose **Publish** on the template card, then **Copy link**.

92 an Enterprise plan default to **Team-only**; other accounts default to a1313. Send the link. The recipient opens a preview on [x.ai](https://x.ai) and can

93 public link.132 choose **Add to Grok Bot**. They need the Grok Bot app to finish adding it.

943. Send the link. The recipient opens a preview on133 

95 [x.ai](https://x.ai) and can choose **Add to Grok Bot**. They need the Grok134On iPhone and Android, open the Bot's menu and choose **Share as Template**.

96 Bot app to finish adding it.135 

97 136After you publish, the same **Share** menu offers **View template details**,

98A public link can be opened by anyone who has it and shows the Bot's shared137**Update template** to push your latest changes to the shared copy, and

99configuration, including its identity, description, skills, and routines; a138**Delete Template** to turn off the link.

100Team-only link opens only for members of your team. Remove API keys, internal139 

101URLs, customer data, and anything else you would not put in a public document140A new template link is public. If your team allows only team-only sharing or

102before you share.141has turned template sharing off, the app doesn't offer **Create a copy**, and

103 142publishing a template shows `Your team doesn't allow public templates` or

104Adding a shared Bot creates a copy on the recipient's account. It does not give143`Template sharing is turned off`. Enterprise teams start with template sharing

105them your computer, logins, or conversation history. To give the team one Bot144limited to the team; an admin can change it under

106they all talk to, publish a [Team Bot](/grok-bot/team-bots).145[Public template sharing](/grok-bot/teams-and-enterprises#public-template-sharing).

107 146 

108Shared Bots are created by other users, not by . Adding one accepts147A public link can be opened by anyone who has it and exposes the Bot's shared

109the [third-party bot terms](https://x.ai/legal/bot-sharing-terms).148configuration: its identity, description, skills, and routines. A team-only

149link opens only for members of your team. Remove API keys, internal URLs,

150customer data, and anything else you would not put in a public document before

151you share.

152 

153Adding a shared template creates a copy on the recipient's account. They never

154get your computer, logins, or conversation history. To give your team one Bot

155to chat with instead of a copy each, [share the Bot

156itself](/grok-bot/shared-bots).

157 

158Shared templates are created by other users, not by Grok Bot. Adding one

159accepts the [third-party bot terms](https://x.ai/legal/bot-sharing-terms) shown

160at that point.

110 161 

111On the Teams plan and the Enterprise plan, admins control whether members can162On the Teams plan and the Enterprise plan, admins control whether members can

112publish Bot templates publicly. See [Public template163publish Bot templates publicly. See [Public template

113sharing](/grok-bot/teams-and-enterprises#public-template-sharing).164sharing](/grok-bot/teams-and-enterprises#public-template-sharing).

114 165 

115## Add a Bot from Marketplace166## Add a Bot from a template

116 167 

117**Marketplace** in the sidebar also lists Bots that you can add. Choose **Add**168To browse Bot templates, open **Connect apps** in the sidebar and choose

118on a Bot, or open it and choose **Import Bot**, to create your own copy from169**Bot templates**. The gallery opens on x.ai in your browser. Open a template

119its template.170link and choose **Import Bot** to add your own copy of that Bot.

120 171 

121## Delete a Bot172## Delete a Bot

122 173 

123Deleting a Bot removes its active profile, conversation, and routines from Grok174To delete a Bot, right-click it in the sidebar and choose **Delete**. This

124Bot. Shared computer files and sign-ins are not isolated by Bot and may remain175erases its profile, conversations, memory, routines, and attachments, including

125on the computer. Backend retention follows the applicable Cursor terms.176the shared facts it saved for your other Bots. It can't be undone. Files and

177sign-ins on the shared computer aren't isolated per Bot and can remain there;

178clean them up separately. Backend retention follows the applicable Cursor terms.

126 179 

127If you may need the work later, hide the Bot instead.180If you may need the work later, or want to keep the Bot's memory, choose **Hide

181from sidebar** instead.

128 182 

129## What a Bot remembers183## What a Bot remembers

130 184 

131A Bot can retain stable working preferences, important facts, and summaries185A Bot retains stable preferences, important facts, and summaries from its work,

132from its work. This helps it keep a role over time without replaying every prior186which lets it keep a role over time without replaying every prior message. It

133message.187saves lasting things, such as:

188 

189* How you like to work, and your preferences

190* Rules you ask it to keep, like “Always ask before you send an email.”

191* Facts about you, like your name and time zone

192* A dated log of what it has worked on with you

193 

194Logins, cards, and contact info, like addresses and phone numbers, belong in

195[Vault](/grok-bot/vault), not in memory.

196 

197### When a Bot saves something

198 

199A Bot decides on its own when something is worth keeping. It doesn't ask first.

200It often mentions a save in its reply, but not every save shows up in the chat.

201To make sure it keeps something, ask it to remember, for example: “Remember that

202I'm out every Friday.”

203 

204### Across chats, Bots, and calls

205 

206What a Bot saves in one chat, it remembers in all your chats with it. Each Bot

207has its own memory, but a few facts about you, such as your name and time zone,

208are shared by all your Bots. When one Bot learns one of these, your other Bots

209know it too.

210 

211In a [voice chat](/grok-bot/chat-and-collaboration#start-a-voice-chat), a Bot

212can draw on your earlier calls and your recent chat with it. After you hang up,

213you can ask it about the call in chat.

214 

215In a [group chat](/grok-bot/chat-and-collaboration#start-a-group-chat), your

216Bot can use what you told it in your private chat. If something should stay out

217of a group chat, tell your Bot. Each Bot in a group keeps its own memory; your

218Bot's memory isn't shared with the other Bots there, but everyone in the group

219can read what your Bot says.

220 

221### See, correct, or remove a memory

222 

223There is no memory screen for a personal Bot. Ask in chat instead:

224 

225* To see it: “What do you remember about me?”

226* To correct it: “That's out of date. I moved to Denver.”

227* To remove it: “Forget that I'm on the launch team.”

228 

229If a fact that all your Bots share is wrong, tell any of your Bots the right

230version. To remove a shared fact completely, ask the Bot that saved it.

231 

232### What resets or deletes memory

233 

234| What you do | What happens to memory |

235| -------------------- | --------------------------------- |

236| Reset a conversation | Memory is kept. |

237| Delete a Bot | That Bot's memory is deleted. |

238| Delete your account | All your Bots' memory is deleted. |

239 

240When a message is blocked, the notice can offer **Reset**. If you choose it, you

241see **Reset this conversation?** The conversation history starts over, and the

242Bot's memory, files, routines, and settings are kept.

243 

244### Who can see or change memory

245 

246A personal Bot's memory is yours, and only you can change it. A [shared

247Bot](/grok-bot/shared-bots) can save things it learns for the whole team, and

248it tells you when it does. It doesn't save anything about you personally for

249the team; what it remembers about working with you stays between you and the

250Bot. A teammate's shared Bot doesn't get the facts your own Bots share about

251you.

252 

253### Import memory from another assistant

254 

255To bring over what another AI assistant knows about you, open Settings →

256**General** and choose **Start Import** under **Import**. Copy the prompt into

257a chat with your other assistant, paste its answer into the second box, and

258choose **Add to Memory**. Grok Bot sends it to your

259[primary Bot](#your-primary-bot) and opens that chat.

260 

261### Memory is not a source of truth

134 262 

135Memory is not a substitute for an authoritative source:263Memory is not a substitute for an authoritative source:

136 264 

3# Message and collaborate3# Message and collaborate

4 4 

5Grok Bot is designed to feel like messaging a teammate. Keep requests natural,5Grok Bot is designed to feel like messaging a teammate. Keep requests natural,

6but make the outcome and decision boundary explicit.6but make the outcome and the decision boundary explicit: what the Bot may

7change, and where it must stop for you.

7 8 

8## Message a Bot9## Message a Bot

9 10 

14* Dictate into the composer15* Dictate into the composer

15* Start a voice chat16* Start a voice chat

16* Play a voice memo a Bot sent17* Play a voice memo a Bot sent

17* Reference a saved skill with `/`18* Ask for a saved [skill](/grok-bot/skills-routines-and-automations) by name

18* Mention a Bot, group, routine, or app with `@`19* Mention a Bot, group, routine, or app with `@`

19* Reply to a specific message20* Reply to a specific message

20* React to a message21* React to a message

25 26 

26### Dictate a message27### Dictate a message

27 28 

29Voice typing turns your speech into text in the composer. You read it, edit it,

30and send it like any other message, and the Bot replies in text.

31 

28On desktop, choose **Start voice input** in the composer, or press `Cmd/Ctrl+D`32On desktop, choose **Start voice input** in the composer, or press `Cmd/Ctrl+D`

29while the prompt is focused. Speak, then stop; the app types what you said33while the prompt is focused. You can also hold the keys while you talk.

30into the composer so you can edit it before you send.

31 34 

32On iPhone and Android, use **Start dictation** in the composer. See35On iPhone and Android, use **Start dictation** in the composer. Stop dictation

33[Grok Bot for Mobile](/grok-bot/mobile).36before you start a voice chat. See [Grok Bot for Mobile](/grok-bot/mobile).

34 37 

35### Play a voice memo38### Play a voice memo

36 39 

40 43 

41### Start a voice chat44### Start a voice chat

42 45 

43Choose **Start voice chat** when the composer is empty to talk with the Bot46A voice chat is a live spoken conversation with one Bot: the Bot answers out

44live. While you are on the line, the app shows **Voice chat**. On desktop the47loud and keeps listening until you hang up. Voice chat works in the desktop app

45sidebar can show **Voice chat in progress**. When the call ends, the48and the phone app.

46conversation can include a **Voice chat** card.49 

501. Open the chat with the Bot and leave the composer empty.

512. Choose **Start voice chat**, the waveform button in the composer.

523. Allow microphone access if your computer or phone asks.

53 

54The call shows **Connecting…** on desktop or **Calling…** on the phone, then the

55Bot starts talking. **Start voice chat** shows only when the composer is empty;

56if the composer is empty and you still don't see it, update Grok Bot. While you

57are on the line, the app shows **Voice chat**, and on desktop the sidebar can

58show **Voice chat in progress**.

59 

60During a call you can **Mute** or **Unmute** your microphone, **Hang up**, or

61choose **Show transcript** to read along. In a call with your own Bot, **Show

62settings** changes the **Voice**, the **Speed**, and the **Language**;

63**Auto-detect** picks the language from what you say. You can open other chats

64while the call runs; on desktop, choose **Return to the voice chat** to go back.

65Only one voice chat runs at a time, so starting another asks **End the current

66voice chat?**; choose **End and Chat** to switch.

67 

68Voice 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's

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

71 

72If 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, the

74call ends with **Voice chat failed**, and the notice may say **Connection

75lost**, **No connection**, or **The call ended unexpectedly**. Choose

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

77again.

78 

79If 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 try

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

82pick one under **Microphone**.

83 

84When the call ends, the conversation includes a **Voice chat** card with the

85call's length; open it to read the full transcript. If the call left work to

86do, the Bot may follow up in the chat with next steps or results. Grok Bot may

87ask **How was the call?**; choose **Good** or **Bad** to send feedback.

47 88 

48### Review a draft before it is sent89### Review a draft before it is sent

49 90 

52or **Send message** for a Slack draft in the desktop app. Choose **Discard** to93or **Send message** for a Slack draft in the desktop app. Choose **Discard** to

53drop the draft.94drop the draft.

54 95 

96Bots draft outgoing messages for your review by default. A draft card shows

97**Needs approval**. If you'd rather have a Bot send without preparing drafts,

98open that menu on one of its drafts and choose **Disable drafts for Bot**. The

99Bot then sends directly, subject to your

100[Auto Review](/grok-bot/approvals-security-and-privacy#configure-auto-review)

101settings. The choice applies to that Bot only, and only its owner sees it; it

102isn't offered in group chats. Email from the Bot's [own

103address](/grok-bot/computer-and-apps#give-your-bots-an-email-address) that you

104didn't request in chat, such as email from a routine, always waits as a draft. To get

105drafts back, choose **Needs approval** on a draft card or ask the Bot. If the

106change doesn't save, the card shows `Couldn't save. Try again.`; choose

107**Retry**.

108 

55### Redirect work in progress109### Redirect work in progress

56 110 

57Send a new message when priorities change. A direct message from you takes111Send a new message when priorities change. A direct message from you takes

60Send a direct “Stop now” message when work should end immediately. This does not114Send a direct “Stop now” message when work should end immediately. This does not

61undo actions the Bot already completed.115undo actions the Bot already completed.

62 116 

117### Chat in X Chat

118 

119You can also chat with your Bots in X Chat, in the X app on iOS and Android and

120on x.com. They're the same Bots you use in the Grok Bot app. X Chat support is

121rolling out gradually, so it may not show up for you yet even if your plan

122includes it, and it needs the latest version of the X app.

123 

124You need a plan that includes Grok Bot. On [The X

125Subscription](/x-subscription/overview), that's **Premium**, **Super**, or

126**Ultra**; **Plus** doesn't include Grok Bot. Legacy Cursor plans and linked

127SuperGrok or X Premium+ accounts that include Grok Bot also work. See [Grok Bot

128on The X Subscription](/x-subscription/grok-bot).

129 

130Your Grok account also needs to be connected to a Cursor account. Connecting

131from X Chat works only for personal accounts. It isn't available when your

132email is on a domain your company manages, your Cursor account is on a team, or

133your Cursor account is on a [legacy request-based

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

135If a Cursor account already uses your email, you need to agree before it's

136connected.

137 

138| What's happening | What to do |

139| --- | --- |

140| Your plan doesn't include Grok Bot | Choose **Premium** or higher on The X Subscription. |

141| Your Cursor account, or its team, uses Privacy Mode (Legacy) | Switch your Cursor account to Privacy Mode. On a team, a team admin changes the team's privacy setting. |

142| Your Cursor account is on a legacy request-based plan | Grok Bot isn't available on legacy request-based plans. |

143| 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. |

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

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

146| 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) |

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

148| 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. |

149 

150X Chat uses the Grok account your X account is connected to. If you have more

151than one Grok account, that may not be the one you use with Grok Bot, and

152trying again doesn't help. To connect your X account to the Grok account you

153use with Grok Bot:

154 

1551. In a browser, sign in at [accounts.x.ai](https://accounts.x.ai) with the Grok

156 account you use with Grok Bot.

1572. In the same browser, sign in to [x.com](https://x.com) with your X account.

1583. Open [x.com/i/jf/grok/entry](https://x.com/i/jf/grok/entry). Choose to link

159 another account, then allow access for the Grok account you signed in with.

1604. Quit and reopen the X app, or reload x.com, and open your Bots again.

161 

162If that Grok account is already connected to a different X account, this

163doesn't work. If none of these match, [contact

164support](/grok-bot/troubleshooting) with your X handle and the email on your

165Grok account.

166 

63## Start a group chat167## Start a group chat

64 168 

65Use a group when several Bots need one shared outcome and visible handoffs.169Use a group when several Bots need one shared outcome and visible handoffs.

170You can also add a Bot a teammate [shared with you](/grok-bot/shared-bots), but

171not alongside Bots that run on your own computer.

66 172 

671. Choose **New chat** (the **+** button) in the sidebar.1731. Choose **New chat**, press `Cmd/Ctrl+Shift+N`, or open the command palette

682. In **New chat**, select two to six Bots.174 with `Cmd/Ctrl+K` and choose **New group chat**.

1752. In the **To:** field, add two to six Bots.

693. Open the group, then edit its generated name if needed.1763. Open the group, then edit its generated name if needed.

704. Describe the shared outcome and who owns the next step.1774. Describe the shared outcome and who owns the next step.

71 178 

72On iPhone or Android, use **+ → New Group Chat**. Group membership can be179On iPhone or Android, use **+ → New Group Chat**. Group membership can be

73edited later.180edited later.

74 181 

182To rename a group on desktop, right-click it in the sidebar and choose **Rename

183chat**, or click the group's name at the top of the chat and click the name in

184its details to edit it. On the phone, tap the group's name at the top of the

185chat, tap **Edit**, change the **Name**, and tap **Done**. To change what the

186group is for, tell the Bots in the group.

187 

188Group chats don't have the per-Bot **Notifications** switch. See [Control

189notifications](/grok-bot/settings-and-notifications#control-notifications).

190 

75### Direct a message191### Direct a message

76 192 

77* Write normally to let the participating Bots decide who should respond.193* Write normally to let the participating Bots decide who should respond.

81* Use `@everyone` sparingly for a group-wide update.197* Use `@everyone` sparingly for a group-wide update.

82 198 

83Bots can post into the group and pass work among themselves. A useful kickoff199Bots can post into the group and pass work among themselves. A useful kickoff

84looks like:200assigns one owner per stage:

85 201 

86> @Researcher gather the source material and link every claim. @Writer turn the202> @Researcher gather the source material and link every claim. @Writer turn the

87> findings into a launch draft. @Reviewer check the draft against the sources203> findings into a launch draft. @Reviewer check the draft against the sources

91include files, questions, and forms, as in a one-to-one conversation, and your207include files, questions, and forms, as in a one-to-one conversation, and your

92answer to a question or form goes back to the Bot that asked. Approval208answer to a question or form goes back to the Bot that asked. Approval

93requests, secret and login requests, and email or Slack drafts do not appear in209requests, secret and login requests, and email or Slack drafts do not appear in

94a group. Bot-to-group handoff messages are currently text-only, so a Bot should210a group. Bot-to-group handoff messages are text-only, so a Bot should send an

95send an image directly to another Bot when that teammate must inspect it.211image directly to another Bot when that teammate must inspect it.

212 

213### Keep replies in the group

214 

215When you write in a group chat, the Bots answer there. A Bot can also message

216you in its own chat, or message another Bot to hand off work; those messages

217show up in the Bots' own chats, not in the group.

218 

219To keep a Bot's replies in the group, tell it there: “Reply here in the group.

220Don't message me privately about this.” To make it a lasting rule, ask each Bot

221to remember it: “Remember: in group chats, reply in the group.”

222 

223### Stop Bots from messaging each other

224 

225There is no switch for this. Bots message each other to hand off work, and they

226follow your instructions about it.

227 

2281. Tell the Bots in the chat, for example: “Don't message other Bots. Ask me

229 first.”

2302. To keep the rule, ask each Bot to remember it.

2313. If a Bot keeps starting new work, open that Bot's chat and ask it to stop.

232 

233To quiet a helper Bot without deleting it, turn off its notifications or hide

234it. Every Bot reply counts toward your usage, including replies in a group and

235messages between Bots, so fewer Bots in a group means fewer replies.

96 236 

97## Let Bots hand work off237## Let Bots hand work off

98 238 

107* A blocker belongs to another role247* A blocker belongs to another role

108* A long-running job should continue without you coordinating every step248* A long-running job should continue without you coordinating every step

109 249 

110Ask for a single owner at each stage. Too many parallel handoffs can create250Ask for a single owner at each stage. Parallel handoffs create duplicate work

111duplicate work and noisy updates.251and noisy updates.

112 252 

113A handoff needs a Bot acting for one person. From the app or your own Slack DM,253A handoff needs a Bot acting for one person on that turn. Where you talk to it,

114any Bot can hand off work. From a Slack channel thread, only a254and whether it's a personal Bot or a [shared Bot](/grok-bot/shared-bots),

115[Team Bot](/grok-bot/team-bots) can, on behalf of the person who mentioned it.255decide this:

116See [Can a Bot message other Bots from256 

117Slack?](https://cursor.com/help/grok-bot/group-chats#can-a-bot-message-other-bots-from-slack)257| Bot | Where you ask | Can it message other Bots? | Acting for | Where the reply lands |

258| --- | --- | --- | --- | --- |

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

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

261| 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 |

262 

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

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

265give it work. See [How do I add a shared Bot to

266Slack?](/grok-bot/shared-bots#how-do-i-add-a-shared-bot-to-slack)

118 267 

119## Use threads and reactions268## Use threads and reactions

120 269 

149 298 

150* Jump to / search palette: `Cmd/Ctrl+K`299* Jump to / search palette: `Cmd/Ctrl+K`

151* Search Bots: `Cmd/Ctrl+Shift+F`300* Search Bots: `Cmd/Ctrl+Shift+F`

152* New Bot / new chat: `Cmd/Ctrl+N`301* New Bot: `Cmd/Ctrl+N`

302* New group chat: `Cmd/Ctrl+Shift+N`

303* Show all keyboard shortcuts: `Cmd/Ctrl+/`

153* Find in this chat: `Cmd/Ctrl+F`304* Find in this chat: `Cmd/Ctrl+F`

154* Compact sidebar: `Cmd/Ctrl+B`305* Compact sidebar: `Cmd/Ctrl+B`

155* Focus prompt: `Cmd/Ctrl+I`306* Focus prompt: `Cmd/Ctrl+I`

173* Zoom in, out, or reset: `Cmd/Ctrl+=` / `Cmd/Ctrl+-` / `Cmd/Ctrl+0`324* Zoom in, out, or reset: `Cmd/Ctrl+=` / `Cmd/Ctrl+-` / `Cmd/Ctrl+0`

174* Fullscreen: `F11`; on macOS also `Control+Cmd+F`325* Fullscreen: `F11`; on macOS also `Control+Cmd+F`

175 326 

327To see every shortcut in the app, open the account menu and choose

328**Support → Keyboard shortcuts**, or press `Cmd/Ctrl+/`.

329 

176## Keep conversations effective330## Keep conversations effective

177 331 

178* Lead with the result you need, not a detailed imitation of every click.332* Lead with the result you need, not a detailed imitation of every click.

2 2 

3# Use the computer and apps3# Use the computer and apps

4 4 

5Grok Bot works from a persistent cloud computer. It can use a browser, command5Your Bots work from a persistent cloud computer with a browser, command line,

6line, files, and connected tools without depending on your laptop remaining6and filesystem. Work continues while your laptop is closed, and files,

7open.7sign-ins, and browser sessions persist between tasks.

8 8 

9## One computer, shared by all your Bots9## One computer, shared by all your Bots

10 10 

31## Watch computer work31## Watch computer work

32 32 

33Click the computer preview in the right-hand panel of a conversation to open33Click the computer preview in the right-hand panel of a conversation to open

34the computer and view the shared desktop. The preview34the computer and watch clicks, typing, navigation, and current status.

35shows clicks, typing, navigation, and current status.

36 35 

37You can leave the preview while work continues. Closing the Grok Bot app or36You can leave the preview while work continues. Closing the Grok Bot app or

38your laptop does not stop cloud work.37your laptop does not stop cloud work.

39 38 

40## Take over for a sensitive step39## Take over for a sensitive step

41 40 

42The Bot may ask you to take over for:41To sign in, a Bot uses a login saved in [Vault](/grok-bot/vault) first, then a

43 42connected password manager such as [1Password](#connect-1password), then asks

44* A password or passkey43you with a Secure Form. Values from Vault and the Secure Form are filled into

45* Two-factor authentication44the page without the Bot seeing them. When a site emails a one-time code, the

46* A CAPTCHA45Bot can read it from a connected Gmail or Outlook account or from [its own

47* A payment or identity check46inbox](#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 Link

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

49 

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

51 

52* Single sign-on or a passkey

53* A CAPTCHA it couldn't get past

54* An approval on another device or a QR code

55* A bank card verification

48* A site that explicitly requires a human56* A site that explicitly requires a human

49 57 

50Open the computer, take control, complete only the blocked step, and tell the58Open the computer, take control, complete only the blocked step, and tell the

51Bot to continue. The Bot doesn't type credentials and doesn't see your59Bot to continue. Never paste passwords or one-time codes into ordinary chat. For

52password. Avoid pasting passwords or one-time codes into chat.60an API key or other secret, enter it in the secure secret card when the Bot

53 61asks: the field is masked, and the value isn't written into the chat or shown to

54For a supported connection that presents a secure secret request, enter the62the Bot. See [API keys and other

55value there instead. The value is masked, is not added to the conversation, and63secrets](/grok-bot/vault#api-keys-and-other-secrets).

56is not shown to the model. See

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

58 64 

59## Sign in once65## Sign in once

60 66 

63available to your other Bots.69available to your other Bots.

64 70 

65Some websites expire sessions, enforce short timeouts, or request verification71Some websites expire sessions, enforce short timeouts, or request verification

66again. Ask the Bot to pause and notify you rather than attempting to bypass the72again. Ask the Bot to pause and notify you rather than attempting to work around

67check.73the check.

68 74 

69## Connect an app75## Connect an app

70 76 

71Apps give a Bot a structured way to work with services like Gmail, Notion, and77Apps give a Bot a structured way to work with services like Gmail, Notion, and

72Slack. Apps are installed as plugins from **Connect apps**.78Slack, and are more reliable than clicking through a website when one exists.

79Use the browser for services without an app or for visual workflows an app does

80not expose. App connections belong to the same account you used to sign in to

81Grok Bot.

73 82 

741. Open **Connect apps** from the sidebar, or follow an in-chat **Connect**831. Open **Connect apps** from the sidebar, or follow an in-chat **Connect**

75 card.84 card. In the mobile app, tap your avatar on the top left and choose

762. Browse or search for the app.85 **Connect apps**.

773. Choose **Add**.862. Browse or search for the app, then add it.

784. Finish the provider login in your browser if requested.873. When Grok Bot asks you to **Authorize** or **Authenticate**, finish the

795. In chat, type `@` to attach the app to the task. Type `/` to reference a88 provider login in your browser.

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

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

82Setup steps and known issues are in915. Confirm the app appears under **Installed**.

83[Connect apps](https://cursor.com/help/grok-bot/connect-apps).92 

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

85Prefer an app when one is available: it is often more reliable than clicking94 

86through a website. Use the browser for services without an app or for visual95**Added** means the app is installed, not that you are signed in. If the Bot

87workflows an app does not expose.96says an app is missing, open the app and choose **Authenticate** (**Authorize**

97on the phone) if it shows **Needs auth** or **Disconnected**.

98 

99You can also ask a Bot to do this for you, for example “Add the Linear app.”

100The Bot searches the catalog, installs the app on your account, and shows a

101**Connect** card when the app needs you to sign in. The app's tools are ready

102from your next message. A Bot can also add an MCP server that isn't in the

103catalog, by URL or by a command that runs on its computer; a server started by a

104command is available to your other Bots too. Adding a server on a private

105network, or one that uses a private certificate authority, asks for your

106approval first.

107 

108When a Bot removes an app for you, everything the app added goes with it and

109you are signed out, so reinstalling it means signing in again. Apps your team

110requires can't be removed.

88 111 

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

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

91 accounts.114 accounts.

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

93 connector backend, and the Bot invokes tools without receiving them.116 connector backend, and the Bot invokes tools without receiving them.

94* **Team policy applies.** An app blocked by your team's117* **Team policy applies.** An app blocked by your team's

95 [connector policy](/grok-bot/teams-and-enterprises#connector-policy) shows118 [connector policy](/grok-bot/teams-and-enterprises#connector-policy) shows

96 **Disabled by team admin**. Blocking an app doesn't block that service's119 **Disabled by team admin**; ask your admin to enable it. Blocking an app

97 website. Closing that second path takes **Network Controls**, which is120 doesn't block that service's website. Closing that second path takes

98 Enterprise only. See [Network policy](/grok-bot/security#network-policy).121 **Network Controls**, which is Enterprise only. See [Network

122 policy](/grok-bot/security#network-policy).

123 

124The **Email** app is different: it gives your Bots [their own email

125address](#give-your-bots-an-email-address) instead of connecting an account you

126already have.

127 

128### What a connected app can do

129 

130An app uses the account you authorize. It can do only what that account can

131already do in that service. It cannot raise your access, and it cannot change

132sharing.

133 

134* **Google Calendar:** the Bot can read calendars you can see, create and

135 update events, check free time, and respond to invitations on calendars you

136 can edit. It cannot change Google Meet settings, such as the waiting room or

137 host controls, and it cannot add a Zoom link, because Google's Zoom add-on

138 isn't available to the app. Put the Zoom link in the event location or

139 description yourself, or create the event in Calendar and ask the Bot to

140 update the other fields.

141* **Google Sheets:** the Bot can read and edit cells in spreadsheets the

142 connected Google account can edit. A file shared as Viewer stays view-only.

143 Finding and opening files uses the **Google Drive** app, which can search and

144 read files that account can open.

145* **Slack:** the app posts as the Slack user you connected, not as a separate

146 bot that has to be invited. It can post only in channels that user can post

147 in. To use another Slack workspace, connect that workspace. This is separate

148 from a Slack message that [starts a

149 routine](/grok-bot/skills-routines-and-automations#trigger-work-from-an-event).

150* **Gmail:** the app can search and read mail, draft and send, and apply labels

151 on the connected mailbox. Gmail connects one mailbox at a time; to use a

152 different one, disconnect the current mailbox and authorize the other.

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

154 Notion, can connect a second account.

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

156 

157### If Google says an admin needs to review Grok

158 

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

160Docs, Sheets, or Slides finishes signing in. Grok Bot signs in to Google as

161**Grok**, not Cursor. This is separate from the Cursor **Disabled by team

162admin** control.

163 

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

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

166wait for the admin to approve Grok before you try **Authorize** again. An IT

167admin approves **Grok** in the Google Admin console:

168 

1691. Open **Security**, then **Access and data control**, then **API controls**.

1702. Open **App access control**, then **Manage third-party app access**.

1713. Add the app named **Grok**. If name search does not find it, use the client

172 ID from the blocked page or the admin review email.

1734. Set Grok to **Trusted** for the people who use Grok Bot.

174 

175That approval covers the Google apps those people connect. It does not turn an

176app back on in Cursor.

177 

178If the page says **Access blocked**, Google refused the sign-in. A personal

179Gmail account does not need a company admin; a company account often hits this

180when Grok is not on the allowlist, or when the admin has blocked third-party

181apps. Ask the Google admin to trust **Grok** with the steps above. Changing

182browsers or connecting the app again does not clear a Google admin block. If the

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

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

185 

186### Connect 1Password

187 

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

189your 1Password account. You approve each login in 1Password, and 1Password fills

190it in; your Bots never see the values. The new 1Password integration is rolling

191out gradually. It works with personal and Family 1Password accounts and needs

1921Password 8.12.42 or later.

193 

1941. Choose **Connect apps** and open **1Password**, under **Password Managers**.

1952. On your computer, choose **Connect 1Password**.

1963. Your browser opens. Sign in to 1Password there and approve Grok Bot. Grok Bot

197 updates when you're done.

198 

199On the phone, open 1Password from the **Password Managers** shelf in **Connect

200apps**, or search for it, then approve the connection in 1Password. If your phone

201says **1Password can only be set up on a Mac**, the new integration hasn't

202reached your account yet; set it up from Grok Bot on your computer instead. To

203stop using 1Password, open it in **Connect apps** and choose **Disconnect**.

204 

205When a login isn't saved in Vault, the Bot sends a card in the chat that names

206the website:

207 

2081. Choose **Review in 1Password**. The 1Password app opens, or 1Password opens

209 in your browser if the app isn't installed on that computer.

2102. In 1Password, choose the exact logins to share and approve the request.

2113. 1Password fills the login in the Bot's browser.

212 

213A login you share stays available in later chats. If 1Password stops allowing

214it, the Bot asks again. 1Password does not fill payment cards, and your Bots

215still ask you to help with steps it can't fill, such as a passkey, single

216sign-on, or a CAPTCHA.

217 

2181Password only offers logins from your own Personal vault, called Private on

219Family accounts, not from shared vaults. Move or duplicate the login into that

220vault, then ask the Bot to try again. If no approval prompt shows up at all,

221update the 1Password app to 8.12.42 or later.

222 

223The new integration no longer uses a service account, so if you used 1Password

224with Grok Bot before, connect it again. Logins in the vault you shared with the

225old integration aren't available until you move them to your Personal or

226Private vault; the 1Password page in **Connect apps** tells you how many. On a

227Mac, you can choose **Move to Private** instead and approve in 1Password if it

228asks. The old vault stays in 1Password.

229 

230| Message | What to do |

231| --- | --- |

232| **1Password didn't finish connecting** | Start connecting again. On the phone, if you already have a 1Password account, choose **I already have 1Password** and sign in with it. |

233| **This 1Password account is already connected to another Grok Bot account** | Disconnect 1Password from the other Grok Bot account first, or connect a different 1Password account. |

234| **Reconnect required** | 1Password no longer accepts the connection. Choose **Reconnect**. |

235| **Sign in to the 1Password account you connected to Grok Bot, then try again** | Sign in to the account you connected, then ask the Bot to try again. |

236| **Access requests aren't turned on for your 1Password account** | Ask your 1Password administrator to turn on access requests. |

237| **This request already ended in 1Password** | Ask the Bot to try again. It sends a new request. |

238| **1Password could not be opened** | Open the 1Password app yourself to review the request. |

239| A message that asks you to revoke Grok Bot's access under **Integrations** in 1Password | Revoke Grok Bot's access under **Integrations** in 1Password, then connect 1Password again. |

240 

241### Known app issues

242 

243* **Zoom error 4700:** Zoom authorization from the Grok Bot desktop app

244 currently fails with error 4700 (Invalid redirect). There is no workaround

245 yet, and no change on your end resolves it.

246* **SharePoint AADSTS50011:** when a Cursor team admin connects SharePoint from

247 the dashboard **Integrations** page with **Application-level permissions**,

248 Microsoft shows a redirect URI mismatch before the consent prompt. Nothing in

249 your tenant causes this. Connect with **Delegated permissions** instead:

250 choose **Connect team** (or **Reconnect**) on the SharePoint card, pick

251 **Delegated permissions**, enter your Microsoft tenant ID, and sign in with

252 Microsoft. Most work or school tenants need a Microsoft admin to consent once

253 to Sites.Read.All. Each member then signs in with their own Microsoft account

254 the first time a Bot uses SharePoint and sees only the sites their account

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

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

257 

258For more setup help, see [Connect

259apps](https://cursor.com/help/grok-bot/connect-apps).

260 

261## Give your Bots an email address

262 

263You can claim one email address at `mail.grokbot.com`, such as

264`yourname@mail.grokbot.com`, for your Bots to use. Your Bots can then receive,

265read, search, and send email from it. With an address, a Bot can:

266 

267* Sign up for services with its own address, and pick up the verification code

268 or link with your OK

269* Collect receipts, newsletters, and reports, and summarize them for you

270* Draft email for you, such as a digest or an update, and draft replies

271* Forward an email from its inbox with the original formatting, images, and

272 attachments, which needs Grok Bot 0.75.2 or later

273* Run a routine when email arrives, optionally only from specific senders

274 

275To claim an address, ask a Bot, for example “Get yourself an email address.” It

276asks what name you want, checks that the name is free, and shows an approval

277card; nothing is claimed until you approve. You can also open **Connect apps**,

278choose **Email**, type a name in **Choose a name** under **Email address**, and

279choose **Create address**. On iPhone and Android, open **Settings → Connect apps

280→ Email**. After you claim it, the app shows your address with a button to copy

281it.

282 

283Names use lowercase letters, digits, dots, hyphens, and underscores, start and

284end with a letter or digit, and are at most 64 characters. Reserved words such

285as support, admin, billing, security, help, info, team, cursor, grok, and xai

286aren't allowed.

287 

288* **One address, for good.** You get one address, and you can't rename or

289 delete it. Addresses are never reissued, even after the account that claimed

290 one is deleted.

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

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

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

294 team address.

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

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

297 starts a routine. There's no inbox view and no new-mail notifications, so ask

298 a Bot, for example “What arrived in your inbox today?” Mail that arrived in

299 the last minute may not show up in a search yet. Each incoming message can

300 include up to 10 attachments, up to 10 MB each and 25 MB in total; attachments

301 beyond those limits are skipped.

302* **Acting on mail.** New mail doesn't start a chat or wake a Bot on its own. To

303 act on it, set up a

304 [routine](/grok-bot/skills-routines-and-automations#trigger-work-from-an-event)

305 that watches for mail from anyone, from specific addresses, or from a whole

306 domain such as `*@example.com`. By default, the routine only runs for mail

307 from senders that pass standard email authentication checks, and routines

308 can't filter by subject.

309* **Sending mail.** When you ask a Bot in chat to send an email, it goes out

310 once [Auto Review](/grok-bot/approvals-security-and-privacy#configure-auto-review)

311 allows it; if Auto Review needs you, you see an approval card first. Email

312 from a routine, or from any other turn you didn't start with that request,

313 waits as a draft until you press **Send**, and there's no option for

314 unattended sending. If you've also connected Gmail or Outlook, the Bot asks

315 which account to send from when either could work.

316* **Safety.** A Bot treats email from other people as information, not

317 instructions. Each message it reads is marked as from you or from someone

318 else, and instructions inside an email never count as your permission to send

319 or act.

320 

321Sending limits:

322 

323* Up to 50 recipients per email, across To, Cc, and Bcc

324* Up to 10 attachments, up to 10 MB each and 25 MB in total; executable files

325 can't be attached

326* Newsletters and first-contact emails go to one recipient per message and

327 include a one-click unsubscribe link

328* If a message bounces, or someone unsubscribes or marks it as spam, the Bot

329 stops emailing that address and tells you who it skipped

330* There are also limits on how many new people a Bot can email, to protect the

331 address from being flagged as spam

332 

333If you delete your Grok Bot account, your mail and attachments are deleted, and

334the address is retired.

335 

336On a Cursor team, agent email is off by default; an admin turns on [Agent

337Email](/grok-bot/teams-and-enterprises#agent-email) before members can claim an

338address. If an admin turns it off later, Bots lose their email tools and email

339routines stop running, but mail sent to existing addresses is still received and

340kept, and members keep their addresses.

341 

342| What you see | What to do |

343| --- | --- |

344| **Agent email is not enabled for this account.** | Agent email isn't available on your account yet. |

345| **Your team admin has turned off Grok Bot agent email, so this account cannot claim or use an agent email address.** | Ask your team admin to turn on **Agent Email**. |

346| **That address is taken, and addresses are never reissued, so retrying it cannot succeed. Choose a different name.** | Choose a different name. |

347| A message about allowed characters, length, or a reserved word | Pick a name that follows the name rules above. |

348| **You can have one agent email address.** | You already have an address. Ask your Bot what it is, or open the **Email** app. |

349| **Couldn't create your email address. Try again.** (phone) | Check the name rules, or try on desktop, which shows the exact reason. |

350| **Too many email addresses checked in the last minute.** | Wait a minute, then try again. |

99 351 

100## Search and read X352## Search and read X

101 353 

110 362 

111## Work with files363## Work with files

112 364 

113The computer has a shared workspace at `/workspace`. Ask Bots to keep durable365The computer has a shared workspace at `/workspace`. Keep durable project files

114project files there and use clear project folders.366there in clear project folders.

115 367 

116Files, browser state, and supported sign-ins are designed to survive normal368Files, browser state, and supported sign-ins survive normal computer updates

117computer updates and recovery. Treat temporary directories, manually installed369and recovery. Treat temporary directories, manually installed packages, and

118packages, and uncommitted application state as replaceable. Copy important370uncommitted application state as replaceable. Copy important results into the

119results into the shared workspace or attach them to the conversation.371shared workspace or attach them to the conversation.

120 372 

121## Update, recover, or reset the computer373Conversation history is stored outside the computer, so deleting files inside

122 374it, including `rm -rf`, does not delete chats. Grok Bot keeps a durable copy of

123When the computer is unreachable, use **Recover computer** from the error state375synced computer data, and reopening the computer restores from that copy, so

124(the confirmation dialog calls it **Recover Grok Bot's Computer**). Recovery is376synced files usually come back. Project folders such as `node_modules` or a

125offered only there, not in Settings. For planned maintenance or last-resort377Python virtual environment are not saved; reinstall them after a computer

126recovery, open **Settings → Computer** and use the controls under **Bot's378update, **Recover**, or **Reset**. Files that exist only on your Mac or Windows

127computer**:379machine are not covered, so keep your own backups for those.

128 380 

129* **Update Bot's Computer** rebuilds the computer on the latest version. It381When the computer is almost full, your Bot tells you once in chat, names the

130 keeps your files and logins but removes installed apps and packages.382biggest files or folders with their sizes, and offers to delete them. Nothing is

131* **Reset Bot's Computer** rebuilds the computer from your last saved383deleted unless you say yes. Low disk space is not data loss, and cleanup applies

132 snapshot. Use it only as a last resort.384only to computer files, not to chats.

133 385 

134The app and the computer update separately. A software update only refreshes386## Update, recover, or reset the computer

135Grok Bot's software and keeps installed apps. Recover and Reset both rebuild

136the computer from your last saved data; if the computer can't be reached to

137save first, very recent changes don't come back. Conversations are stored

138outside the computer, so they survive even a reset.

139 387 

140Wait for active work to finish before recovery when possible. See388Open computer controls from **Settings → Computer**, under **Bot's computer**.

141[Troubleshooting](/grok-bot/troubleshooting) for the least-destructive order.389You can also get **Recover** from the reconnect screen when the app offers it.

390The app and the computer update separately.

391 

392| Action | What it does | What it keeps | What it removes |

393| --- | --- | --- | --- |

394| **Update** | Moves the computer to the latest version. Some updates only refresh Grok Bot's software; others replace the whole computer, and you may be able to schedule those for later. The text under **Update Bot's Computer** says which kind is waiting. | Software update: everything, including installed apps. Computer update: Bots, files, and logins. | Software update: nothing. Computer update: installed apps and packages. |

395| **Recover** | Saves what it can, then builds a new computer on the latest version from your saved data. Running work is interrupted. | Bots, files, and logins that were saved | Installed apps and packages, and very recent changes if the computer could not be reached to save them |

396| **Reset** | Builds a new computer on the latest version from your last saved data. Running work is interrupted. | Bots, files, and logins that were saved | Installed apps and packages, and very recent changes if the computer could not be reached to save them |

397 

398Conversations are stored outside the computer, so they survive even a reset.

399If Bots recently disappeared, or saving failed, [contact

400support](/grok-bot/troubleshooting) before you use **Recover** or **Reset**.

401 

402When the computer is unreachable, work from the least destructive option first:

403 

4041. Wait, then choose **Retry** if the computer says **Reconnecting** or

405 **Couldn't Reach Grok Bot's Computer**, or reopen the conversation. Bots,

406 files, and logins are safe while it reconnects. Do not **Reset** during this.

4072. Fully quit Grok Bot and reopen it, and check for an app update. On Mac,

408 choose **Quit** from the menu bar, not just close the window.

4093. Use **Update Bot's Computer** in **Settings → Computer** if an update is

410 offered.

4114. Choose **Recover computer** (the confirmation dialog calls it **Recover Grok

412 Bot's Computer**) if it still cannot reconnect, or if an update looks stuck

413 and **Recover computer** is shown. On a slow update, **Keep waiting** is the

414 safe default.

4155. Use **Reset Bot's Computer** only after those steps.

416 

417Do not start a second Update or Reset while one is already running; repeated

418resets can interrupt a restore that is still finishing. **Reconnecting** and

419**Recover** usually take a few minutes, and you can choose **Continue in

420Background**. An **Update** can also take a few minutes; if it says **Update

421still running**, keep waiting. If **Recover** or **Reset** fails, use **Retry

422Recovery** or **Retry Reset** once, then stop and [contact

423support](/grok-bot/troubleshooting).

424 

425If the computer's files aren't backed up yet, **Update** says they aren't ready

426and nothing changes; wait a moment and try again rather than resetting. If

427Settings says **An agent couldn't pause in time, so the computer was not

428updated**, let that Bot finish, then choose **Update** again.

429 

430A Bot cannot finish a turn while the computer says **Reconnecting** or

431**Couldn't Reach Grok Bot's Computer**. Fix the connection with the steps above,

432then send the message again. See [Troubleshooting](/grok-bot/troubleshooting)

433for missing chats and when to contact support.

142 434 

143## Your local computer is separate435## Your local computer is separate

144 436 

145The Grok Bot cloud computer is separate from the Mac or Windows computer in437The Grok Bot cloud computer is separate from the Mac or Windows computer in

146front of you. A Bot only runs commands on your local computer when that438front of you. A Bot only runs commands on your local computer when that

147capability is enabled and you approve it under your local-computer policy:439capability is enabled and you approve it under your local-computer policy:

148**Ask every time** by default, or **Always allow** or **Never allow**. That440per-command approval with **Ask every time** by default, or **Always allow** or

149policy is separate from the approvals that govern work on the441**Never allow**. That policy is separate from the approvals that govern work on

150cloud computer.442the cloud computer.

151 443 

152Review local-computer permissions in444Review local-computer permissions in

153[Approvals, security, and privacy](/grok-bot/approvals-security-and-privacy).445[Approvals, security, and privacy](/grok-bot/approvals-security-and-privacy#control-access-to-your-local-computer).

3# Manage Grok Bot computers3# Manage Grok Bot computers

4 4 

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

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

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

8organization admins and team admins on an Enterprise team two ways to manage8lets admins recreate or terminate computers across many members at once, or

9those computers. Under **Security & Compliance**, **Manage Member Computers and9[delete all of a member's Grok Bot data](#delete-all-grok-bot-data).

10Data** runs a recreate or terminate across many members at once, or deletes all10**Terminate Inactive Computers**, under **Bot Computers**, turns on

11of a member's Grok Bot data. Under **Bot11[automatic termination](#terminate-inactive-computers-automatically) for members

12Computers**, you can turn on12whose Bots go 30 days without a message. For the rest of the admin controls, see

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

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

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

16 14 

17**Manage Member Computers and Data is Enterprise only**. It appears for15**Manage Member Computers and Data is Enterprise only**. Organization admins

18organization admins and for team admins on an Enterprise team. Members never16and Enterprise team admins can use it. Members never see this control. Team

19see this control. Team admins can also17admins can also

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

21 19 

22## Recreate or terminate20## Recreate or terminate

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

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

33 31 

32## Delete all Grok Bot data

33 

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

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

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

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

38fresh the next time they use Grok Bot.

39 

40* **At most 100 members** per operation.

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

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

43 

34## Run an operation44## Run an operation

35 45 

36### Open Manage Member Computers and Data46### Open Manage Member Computers and Data

37 47 

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

39Under **Security & Compliance**, find **Manage Member Computers and Data** and49**Manage Member Computers and Data** under **Security & Compliance**, and select

40select **Manage**.50**Manage**.

41 51 

42### Select members52### Select members

43 53 

49Open **Manage selected** and pick **Recreate VMs** or **Terminate VMs**. A59Open **Manage selected** and pick **Recreate VMs** or **Terminate VMs**. A

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

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

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

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

54The menu also has **Delete All Grok Bot Data**, which goes further. It64want the member to start from empty. Both delete actions ask you to type

55permanently deletes each selected member's Grok Bot data on every team they65`DELETE` to confirm.

56belong to: their Bots (including Team Bots that teammates use), conversations,

57memory, routines, connected apps, email inboxes, files, and computers. Members

58stay on the team and start fresh the next time they use Grok Bot. It cannot be

59undone and works on up to 100 members at a time. Each operation is recorded in

60the [Audit Log](https://cursor.com/dashboard/audit-log). Both delete actions

61ask you to type `DELETE` to confirm.

62 66 

63### Confirm67### Confirm

64 68 

91 95 

92## Run operations through the API96## Run operations through the API

93 97 

94Organization admins can recreate, terminate, or delete members' computers, or98To roll out across many teams from a script, start the same operations with the

95delete all of their Grok Bot data, from a script with the Organization API.99Organization API. Organization admins can recreate, terminate, or delete

96Send a team, a list of members, and an100members' computers, or delete all of their Grok Bot data. You send a team, a

97action, then poll the operation for its counts and, for operations of up to101list of members, and an action, then poll the operation for its counts and, for