Guide
Grok Bot’s computer and apps: the shared cloud computer, connected apps, and Bot email
By Atlas AI Resources · Published November 17, 2026
Every Grok Bot works from a cloud computer, and most of what it can reach comes from the apps you connect. This page starts with our own advice on what that sharing means for a small fleet, then summarizes what SpaceXSI’s docs page Use the computer and apps says about the shared computer, connecting apps, what each app can and can’t do, Bot email addresses, and files.
1. Our advice: one computer means one trust zone
Sections 1 and 2 are our own advice, not SpaceXSI’s.
- Splitting work into Bots is not splitting access. A one-job Bot keeps a job focused, but every Bot on your account can use the same files, browser sessions, command-line logins, and connected apps. Decide what goes on the computer as if every Bot can use it, because per the docs, every Bot can.
- Write the limits into the job. Since access is shared, the real fence is each Bot’s instructions plus approvals: “read Gmail, never send,” “draft in Drive, never share.” See keeping AI agents safe from prompt injection.
- Prefer the app over the website. When a service has an app, use it. It is more reliable than clicking through a site, and the app’s login stays off the computer.
- Label second accounts plainly. “work” and “personal” are easier to name in an instruction than anything clever, and the label is how you tell a Bot which one to use.
2. Our advice: keep durable work in folders
Give each Bot its own folder in /workspace, and keep anything you’d hate to rebuild there or attached to the chat. Treat installed packages as replaceable. If you run a small fleet, pass work between Bots by file path with a short note.
3. Per the docs: one computer, shared by all your Bots
- Persistent. The computer has a browser, command line, and filesystem. Work continues while your laptop is closed, and files, sign-ins, and browser sessions persist between tasks.
- Shared. Browser cookies and signed-in sessions, files, and command-line credentials are shared, and one Bot can continue from work another saved. The computer belongs to your user account, not to one Bot. The docs say: “Do not place a credential or file on it if another Bot on your account should not be able to use it.”
- Separate screens, not separate boundaries. Each Bot gets its own screen, so several can use the browser in parallel, though one Bot runs one computer-use task at a time. The docs call the screens “separate work surfaces, not separate security boundaries.” Between users, each computer is dedicated and hardware-isolated.
- Watching. Click the computer preview in a conversation’s right-hand panel to watch clicks, typing, and navigation. Closing the app or your laptop doesn’t stop cloud work.
4. Per the docs: sign-ins and taking over
A Bot signs in with a login saved in Vault first, then a connected password manager such as 1Password, then a Secure Form it sends you. It hands you the computer for single sign-on or a passkey, a CAPTCHA it couldn’t pass, an approval on another device or a QR code, a bank card verification, or a site that requires a human. Take control, finish only that step, and tell the Bot to continue. Never paste passwords or one-time codes into ordinary chat. Because the browser is shared, a sign-in for one Bot is available to your other Bots. More on this in Grok Bot Vault and secure sign-in.
5. Per the docs: connecting an app
- Steps. Open Connect apps from the sidebar (on the phone, tap your avatar), add the app, finish Authorize or Authenticate in your browser, and confirm it shows under Installed. If sign-in doesn't finish, choose Reconnect on the app (or Reopen on the in-chat card) to bring the sign-in page back, and finish within about 10 minutes or start again from the card. Type
@in chat to attach an app to a task. - Added isn’t signed in. If a Bot says an app is missing, open it and choose Authenticate if it shows Needs auth or Disconnected.
- Or just ask. “Add the Linear app” works: the Bot installs it and shows a Connect card if you need to sign in. A Bot can also add an MCP server that isn’t in the catalog, by URL or by a command on its computer (see what is MCP). A server on a private network or with a private certificate authority asks for your approval first. In the desktop app, Add a custom connector takes a Remote HTTPS URL or a Command.
- Account-wide, logins off the computer. A connected app is available to every Bot you run. OAuth tokens are held on Cursor’s connector backend, and the Bot calls tools without receiving them.
- Team policy. A blocked app shows Disabled by team admin. Blocking an app doesn’t block that service’s website; closing that path takes Network Controls, which is Enterprise only.
- Removing. Removing an app signs you out of it, so reinstalling means signing in again. Apps your team requires can’t be removed.
6. Per the docs: what a connected app can and can’t do
An app can do only what the authorized account can already do. It can’t raise your access or change sharing. Some specifics from the docs:
- Google Calendar reads, creates, and updates events, but can’t change Google Meet settings or add a Zoom link. Put the Zoom link in the location or description yourself.
- Google Sheets edits only what the account can edit; a file shared as Viewer stays view-only. Editing a Doc in place uses the Google Docs app.
- Slack posts as the Slack user you connected, only in channels that user can post in.
- Gmail connects one mailbox at a time and keeps your Gmail signature on drafts. Some other apps, like Notion, can connect a second account.
- Stripe ends every connection a fixed time after sign-in, so you reconnect it from time to time.
- X: the X plugin needs X API credits on your X developer account. Separately, Bots can search and read public X posts without connecting an account; that access is read-only and doesn’t sign in as you (see Grok Bot on X).
Second accounts. In Connect apps, open the app, choose Add Another Account under Accounts, give it a label like work or personal, and authorize. Tell the Bot which one by label (“Use my work Notion”). If you don’t see Add Another Account, that app connects one account at a time.
7. Per the docs: when an admin or your phone blocks the connection
- Google. Grok Bot signs in to Google as Grok. If a company account says “Your admin needs to review Grok,” an IT admin adds the app named Grok under App access control in the Google Admin console and sets it to Trusted. Reconnecting or changing browsers doesn’t clear an admin block.
- Microsoft 365. A work or school account may need the organization’s admin to approve the app; send them the Approval link from the sign-in page, then connect again. The phone app doesn’t show that link, so connect once from your computer to get it.
- Phone. Some providers don’t finish sign-in on a phone and show Connect on your computer. Connect there once; apps belong to your account, so it then works on the phone too.
8. Per the docs: giving your Bots an email address
- One address, for good. You can claim one address at
mail.grokbot.com, by asking a Bot (“Get yourself an email address”) or under Connect apps → Email. It can’t be renamed or deleted, and addresses are never reissued. - Plus aliases. Mail to
[email protected]lands in the same inbox, so each service can get its own alias. The docs note an alias is “a label, not a lock,” so keep a sender filter on routines that should act only for certain senders. - Reading. There’s no inbox view or new-mail notifications; ask a Bot what arrived. New mail doesn’t wake a Bot on its own; a routine that watches for mail from chosen senders or a domain does.
- Sending. Email from a routine, or any turn you didn’t start with that request, waits as a draft until you press Send. There’s no option for unattended sending. Up to 50 recipients and 10 attachments (10 MB each, 25 MB total) per email.
- Safety. A Bot treats email from other people as information, not instructions.
- Teams. On a Cursor team, agent email is off until an admin turns on Agent Email.
9. Per the docs: files, updates, and your own computer
- Files. Keep durable project files in
/workspace. Files, browser state, and supported sign-ins survive normal updates and recovery; folders likenode_modulesor a Python virtual environment aren’t saved. Conversations live outside the computer, so deleting files never deletes chats. When the disk is almost full, the Bot names the biggest files and deletes nothing unless you say yes. More in Grok Bot files, Pages, and results. - Update, Recover, Reset. These live under Settings → Computer. Work from the least destructive option first; the full order is in Grok Bot troubleshooting.
- Your local computer is separate. A Bot runs commands on your own Mac or Windows machine only when that’s enabled and you approve it, with Ask every time as the default.
Sources
The shared computer, sign-ins, connecting apps, per-app limits, admin blocks, 1Password, Bot email, files, and Update, Recover, and Reset.
The overview that links this page under “Use the computer and apps.”
Related: Grok Bot Vault and secure sign-in · Grok Bot files, Pages, and results · Grok Bot troubleshooting · What is MCP · Grok Bot in meetings · Complete Grok Bot setup guide