Grok Bot Connect Apps and Computer: Setup, Fixes and Recovery

Your Bots work from one persistent cloud computer with a browser, a command line and a filesystem. It belongs to your account, not to any single Bot. Browser sessions, files and command-line credentials are shared, so one Bot can continue from work another Bot saved. Work keeps running while your laptop is closed, and files, sign-ins and browser sessions persist between tasks.

Each Bot gets its own screen, so several Bots can use browser and desktop tools at the same time, one computer-use task per screen. Cursor's docs say those screens are work surfaces, not security boundaries. Don't place a credential on the computer if another of your Bots shouldn't be able to use it. Between users the isolation is strict, because each user's computer is dedicated and hardware-isolated.

To watch a Bot work, click the computer preview in the right-hand panel of a conversation. You see clicks, typing, navigation and the current status. You can leave the preview while the work carries on, and closing the app doesn't stop cloud work.

Keep durable files in clear project folders under /workspace, and copy important results there or attach them to the conversation. Cursor's docs say to treat temporary folders, manually installed packages and uncommitted app state as replaceable.

Yes, but only under the local execution policy. The cloud computer is separate from the machine in front of you. Through the desktop app, a Bot can run commands, read files and move files between the two. That access has its own control, separate from Auto-review, which governs work inside the hosted computer.

The setting is Execution on this computer, under Settings > Computer > Your computer. Until a desktop is listed there, the page shows Execution on Local Computer instead. The choices are Ask every time, Always allow and Never allow. Per-command approval is the default, and the approval card shows the exact command. Cursor recommends Never allow unless a Bot has a specific reason to work on local files.

If you use more than one machine, two details matter. Execution on this computer is per desktop: each listed desktop has its own setting, and it applies to that desktop alone. Your personal Auto-review rules work the other way. They are saved to your account, so they apply from every desktop and the mobile app.

On a team, an admin can cap local execution for everyone, and your own setting still applies when it is stricter than the team's. Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. approvals covers what Auto-review rules can and can't stop.

Apps give Bots a structured way to work with services such as Gmail, Notion and Slack. Cursor's docs call them more reliable than clicking through a website when an app exists, and the browser still covers services without one. Apps aren't in Settings, so start from Connect apps in the sidebar.

1. 1Select Connect apps in the sidebar, or follow an in-chat Connect card. In the mobile app, tap your avatar at the top left and select Connect apps.
2. 2Browse or search for the app, then add it.
3. 3When Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. asks you to Authorize or Authenticate, finish the provider login in your browser.
4. 4If sign-in doesn't finish, choose Reconnect on the app, or Reopen on the in-chat card, to bring the sign-in page back.
5. 5Confirm the app appears under Installed.

Don't skip the last step. Added means the app is installed, not that you are signed in. If the Bot says an app is missing, open it from Connect apps and choose Authenticate (Authorize on the phone) when it shows Needs auth or Disconnected. A Bot sends a connect card only when an app needs you to sign in, so don't wait for one.

Connections belong to the account you signed in to Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. with, and a connected app is available to every Bot you run. A teammate's shared Bot, which Cursor used to call a Team Bot, asks before it uses your accounts. App logins stay off the computer: OAuth tokens are held on Cursor's connector backend, and the Bot invokes tools without receiving them. To manage what's installed, select the connected count next to the Connect apps title, where you can also enable or disable individual app tools.

Websites without an app go through the browser. To sign in there, a Bot uses a login saved in Vault first, then a connected password manager such as 1Password, then asks you with a Secure Form. Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. Vault covers the setup for both.

The Bot hands you the computer for steps a form can't do: single sign-on, a passkey, a CAPTCHA it couldn't get past, an approval on another device, a QR code or a bank card verification. Complete only the blocked step, then tell the Bot to continue.

Two different admins can block an app. A Cursor team admin controls which apps are available in Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition.. A company Google admin controls whether Google lets the sign-in finish. An approval from one doesn't clear a block from the other.

Disabled by team admin is the Cursor control, so ask your Cursor team admin to enable the app. Cursor's teams FAQ tells admins to enable it in Teams MarketplaceAn organisation's private catalogue for distributing rules, skills, sub-agents, commands, MCP servers and hooks to its developers. Press Enter for the full definition., add its server URL to the MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. Press Enter for the full definition. allowlist if they use one, and have the member restart the app. If a permitted app still fails for regular members with a vendor-side permission error, check the provider's requirements, because some vendors restrict their MCP endpoints to their own administrators.

Blocking an app doesn't block that service's website. Closing that second path takes Network Controls, which is Enterprise only.

The Google block applies to Gmail, Calendar, Drive, Docs, Sheets and Slides on a company account. Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. signs in to Google as Grok, so that is the name the admin looks for. If the page says Your admin needs to review Grok, request access if the button is there, and wait for approval before you try Authorize again. The IT admin approves it in the Google Admin console:

1. 1Open Security, then Access and data control, then API controls.
2. 2Open App access control, then Manage third-party app access.
3. 3Add the app named Grok. If name search doesn't find it, use the client ID from the blocked page or the admin review email.
4. 4Set Grok to Trusted for the people who use Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition..

Access blocked means Google refused the sign-in. A personal Gmail account doesn't need a company admin. A company account often hits this when Grok isn't on the allowlist or the admin has blocked third-party apps, so ask the Google admin to trust Grok with the steps above. If the page still says access is blocked after that, contact support with the Google account email and a screenshot of the page. Changing browsers or connecting again doesn't clear a Google admin block.

An app uses the account you authorize and can do only what that account can already do in that service. It can't raise your access, and it can't change sharing. When a Bot can't do something in an app, check this table before you reconnect anything:

Calendar can't add a Zoom link, because a link added from the Calendar website uses Google's Zoom add-on, which the app can't reach. Put the link in the event location or description yourself, or create the event in Calendar and ask the Bot to update the other fields.

The Slack app posts as the Slack user you connected, so there is no separate bot to invite. Another workspace needs its own connection.

Gmail connects one mailbox at a time, so a personal and a work mailbox can't both stay connected. To switch, disconnect the current one and authorize the other. Every Bot on the account can use a connected app, so disconnect Gmail if a Bot shouldn't use that mailbox. Some other apps, such as Notion, can connect a second account.

Cursor lists both as known issues and says its engineers are working on fixes. Zoom has no workaround yet. SharePoint has one, which a Cursor team admin applies from the dashboard.

Zoom authorization from the Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. desktop app currently fails with error 4700 (Invalid redirect). Cursor says no change on your end will resolve it, and that it will update its help article once Zoom can be connected.

SharePoint fails when a Cursor team admin connects it from the dashboard Integrations page with Application-level permissions. Microsoft shows AADSTS50011 (redirect URI mismatch) before the consent prompt. The Microsoft app named in the error belongs to Grok, so nothing in your tenant causes it and nothing in your Entra admin center will clear it. The workaround is to connect with Delegated permissions instead:

1. 1In the Cursor dashboard, open Integrations and find the SharePoint card.
2. 2Choose Connect team, or Reconnect if you already started setup, and pick Delegated permissions.
3. 3Enter your Microsoft tenant ID, for example contoso.onmicrosoft.com or the GUID from Microsoft Entra ID > Overview.
4. 4Sign in with Microsoft. Most work or school tenants need a Microsoft admin to consent once to Sites.Read.All.
5. 5Each member signs in with their own Microsoft account the first time a Bot uses SharePoint, and sees only the sites that account can already open.

If you already started Application-level setup and members see "This team does not have the SharePoint integration", the admin still needs to finish the Delegated sign-in. The app stays unavailable until that Microsoft step completes.

The computer controls are in Settings > Computer, under Bot's computer, and Recover also appears on the reconnect screen when the app offers it. The desktop app updates separately, through Check for Updates and Restart to Update in the Updates pane. Updating the app leaves the computer as it was.

The steps below follow Cursor's help page, which orders them least destructive first. Cursor's Work with Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. docs list Recover before Update, so the two pages disagree on the middle steps, though both keep Reset last.

1. 1Wait, then choose Retry if the computer says Reconnecting or Couldn't Reach Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition.'s Computer. Bots, files and logins are safe while it reconnects. Don't Reset during this.
2. 2Fully quit Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. and reopen it. On a Mac, choose Quit from the menu bar instead of closing the window.
3. 3Update the computer from Settings > Computer if an update is offered.
4. 4Recover if it still can't reconnect, or if an update looks stuck and Recover computer is shown. On a slow update, Keep waiting is the safe default.
5. 5Reset only after those steps.

Give each step time. Reconnecting and Recover usually take a few minutes, and you can choose Continue in Background. An Update can also take a few minutes when it is downloading a large image, and Update still running means keep waiting. If Recover or Reset fails, use Retry Recovery or Retry Reset once, then stop and contact support.

Never start a second Update or Reset while one is running, because repeated resets can interrupt a restore that is still finishing.

When Update won't run, the message says why. If the computer's files aren't backed up yet, Update says they aren't ready and nothing changes, so wait a moment and try again instead of reaching for Reset. If Settings says An agent couldn't pause in time, so the computer was not updated, let that Bot finish and choose Update again.

Chats are, and synced files usually are. Conversation history is stored outside the computer, so deleting files inside it, rm -rf included, doesn't delete chats. Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. keeps a durable copy of synced computer data and restores from it when the computer reopens. If the computer is still empty after Recover, stop making changes inside it and contact support.

Project folders such as node_modules or a Python virtual environment aren't saved, so reinstall them after a computer update, Recover or Reset.

Low disk space isn't data loss. When the computer is almost full, the Bot tells you once in chat, names the biggest files or folders with their sizes and offers to delete them. Nothing is deleted unless you say yes.

If chats or Bots look missing, check before you touch the computer. Fully quit and reopen Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition., then open the same account on another device, such as your phone. Look under Hidden Bots on desktop or Show Hidden Bots on the phone, and confirm you are signed in to the same Cursor account. Don't use Recover or Reset to look for chats.

If they are still missing on every device, contact support with your account email, the Bot name and a screenshot of the sidebar. For the Update required screen, sign-in loops and other app errors, see Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. troubleshooting.