Grok Bot not working — quit and Retry before you Reset

Can’t reach, DNS, and a phone that will not join

Retry first. A resolver that cannot look up cursorvm.com will fail the same way after Reset.

White screen, install, and uninstall

A blank window is not proof the bots were deleted. Hidden Bots and the other device come first.

Update, Recover, Reset, and silence

Update and Recover keep synced bots and files. Reset can drop unsynced work. None of them refill usage.

Plugins, routines, files, and the local machine

These are not a dead cloud computer. Reset does not repair OAuth, a queue, or the local helper.

Version for support is the account menu, About, Copy version info. Request ID is right-click the message, Copy request ID. Email hi@cursor.com. No passwords or keys. One-line staff notes for threads that do not have their own page stay in the list under this index.

All failure sources (89)

The cards above are the long pages. This list keeps all 89 input sources for edge cases that do not have their own page. Threads are field evidence, not official promises.

• Forum: Introducing Grok BotLaunch thread: what people actually asked in the first 48 hours.
• Bots are not a security boundaryMust-read: every Bot on the account sees the same logins and files.
• Always-on workers vs topic threadsCommunity consensus: a Bot is a standing coworker, not a chat tab.
• Free Cursor Ultra with Grok (Heavy bundle)How SuperGrok Heavy maps onto Ultra + Bot, and what does not stack.
• Reconnect issueReal screenshot of “can't reach your computer” after a reconnect.
• X login lock on the Bot computerCloud computers hit site risk controls. X locks are not theoretical.
• ExternalShell blocked despite Always allowAllow-lists still fail. Do not assume Always allow means always.
• Deleted Cursor account orphans the Grok linkAccount deletion can pin the Bot to a dead Cursor identity.
• Hacker News discussionHN thread on the launch — useful for the skeptical read.
• Native desktop on Arch / LinuxLinux desktop is not first-class; this is the request plus community packs.
• Does Grok Bot support local MCP?Staff-confirmed: Grok Bot cannot attach local or stdio MCP; use remote HTTP MCP or the cloud browser.
• Is Grok Bot Down Currently?Aug 20–21 outage thread: bots fail mid-turn; staff point to Reset Grok Bot’s Computer under Settings → Updates.
• Grok Bot 0.23.0 first setup: createAgent / Cannot reach your computerStaff: first-setup createAgent can fail before a computer exists (no Reset). A later note: bad ISP DNS for *.cursorvm.com can also block the computer while Cursor API still works — try 1.1.1.1 or 8.8.8.8.
• Grok Bot: Mac chat works, local computer reported offlineStaff-confirmed split: chat stays up while the Mac local-computer link drops; full quit reconnects, 0.23 shipped a fix.
• Computer refresh wipes WhatsApp linked-device session in Grok BotStaff: computer refresh keeps /workspace, the browser profile, and ~/.config — not ~/.local/state, so WhatsApp link sessions vanish.
• Grok Bot cloud workspace after trial exhaustionStaff: trial end deletes nothing; bots stop replying, but Computer view still lets you export until you Reset.
• Reset Computer window opens behind Settings (0.24.0)Staff: the Reset confirm dialog that opened behind Settings is fixed in the latest desktop; Tab then Enter was the workaround on older builds.
• Grok Bot webhooks failing with internal server errorStaff: webhook POSTs to api2.cursor.sh returned internal error; they rolled back a change and the same curl started working again.
• Grok Bot Gmail connector cannot download attachment bytesStaff: the Gmail connector lists attachment metadata only; no download tool. Use the cloud browser or park the file in Drive.
• Does logging into Grok Bot count as a separate computer?Staff: a Grok Bot login is its own Cursor device, and the cloud workspace can count as a second one toward Too many computers.
• Grok Bot Notion plugin OAuth Invalid redirect_uriStaff: Notion sign-in is stored on the account, so retry fails; Re-authenticate (not Connect) clears it and OAuth succeeds.
• Grok Bot now has ChannelsStaff: Grok Bot now has Channels (sidebar +, up to 6 bots per named space). A thread view that keeps the main chat visible is still in progress.
• Stuck Reconnecting can be a local cursorvm.com blockStaff: the cloud computer was healthy; the Mac never finished reconnect because traffic to cursorvm.com was dropped (VPN or firewall).
• Agent never surfaces Take over for loginStaff: login tasks should hand you the computer; ask it to hand me your computer, and skip passkeys with Try another way.
• Grok Bot Cursor Agent usage and model selectionStaff: agents Grok Bot starts run in your Cursor account and burn Cursor plan usage; Grok Bot chat has a separate allowance; unnamed-model agents use your Cloud Agent default.
• How to track Grok Bot releasesStaff: latest stable is 0.24.0; no public changelog yet (Settings → Updates plus X); there is no official Debian/Fedora desktop app.
• Grok Bot hanging at Cleaning up after resetStaff: the reset usually finishes on the backend; the dialog just misses the done signal at Cleaning up. Fully quit and reopen, then Recover — don’t Reset again.
• Grok Bot 0.24.0 Windows white flash then the app closesStaff: the cloud computer was healthy; a white flash then the process dying is usually local (endpoint security, locked %APPDATA%, or a partial install), not GPU.
• Bots workspace looks empty after a rebuildStaff: after a rebuild, logging in while the computer is still starting can show first-run UI; bots are not gone. Fully quit and reopen, and don’t create your first bot in that window.
• No compact / new session; full transcript is sent each turnStaff: desktop and iOS have no explicit Compact or same-bot new session. Auto-summary is not compact; the full transcript is sent, and there is no model picker.
• Overbooked then Bot failed to respond is model loadStaff: “overbooked” then “Bot failed to respond” is service-side Grok model load, not your account, usage, or computer; wait for a quieter window or reset again.
• Black screen after setup: hosted computer never finished startingStaff: black screen after “Setting up Grok Bot’s computer” means the hosted computer never finished starting; reinstall will not help, and if the same account still works on iOS do not Reset (that drops bots)—wait for a staff rebuild.
• 0.27.0 Windows: local host stays disconnected after clean registrationStaff: on 0.27.0 Windows the agent can say the local machine isn’t connected even after a clean daemon registration; fully quit every Grok process and launch once, and if it still fails it is service-side.
• Webhook URL and sender key are desktop-only, not on iOSStaff: a webhook routine’s POST URL and sender key only appear on the Grok Bot desktop app, not iOS; open the trigger card there (keep the desktop app updated).
• Official X plugin auth is broken on desktop, Cloud, and Grok BotStaff: official X plugin connect/refresh is failing across desktop, Cloud Agents, and Grok Bot (including “connected but tools=0”); no clean workaround while they fix X-side app config.
• Weekly Grok Bot usage can spill into paid On-Demand with no warningStaff: spend order is Grok Bot weekly allowance, then referral/promo credits, then paid On-Demand, with no in-app warning; a $0 On-Demand cap does not block credits, so pause near 100% weekly meter if you want no spill.
• Pro weekly pool is separate; overflow hits shared On-DemandStaff correction: on Pro, Grok Bot has its own included weekly pool, separate from Cursor plan usage; overflow still bills the shared On-Demand pool, so set a $0 On-Demand cap if you want no paid spill.
• Access is live for paid plans, not legacy request-basedStaff: Grok Bot is live for all paid individual plans (Pro / Pro+ / Ultra) and self-serve Teams with no percent or region rollout; legacy request-based pricing does not get it unless you opt into usage-based.
• Gmail plugin OAuth is broken; authorize from CursorStaff: the Grok Bot Gmail plugin OAuth is broken; authorizing Gmail from Cursor uses a different path and the connection is shared with Grok Bot until the plugin is fixed.
• iOS 1.3.2 sends a question list on the first tapStaff: iOS 1.3.2 sends a question list as soon as you tap one option; multi-select before send needs a newer Grok Bot app build.
• Grok-launched agents hide behind the Source filterStaff: Grok-launched cloud agents do appear on cursor.com/agents — enable the Source → Grok Bot filter; middle-click “Open in Cursor” opens the same agent in the browser.
• Days-long “Can’t reach your computer” needs a staff restoreStaff: a days-long “Can’t reach your computer” can be a stuck hosted box that Reset / Recover / reinstall cannot clear; staff restores it on their side, then fully quit and reopen the app.
• Fresh-install white screen is a local profile, not the cloud boxStaff: a fresh-install white window is a local profile bug, not a stuck cloud computer; fully quit, rename ~/Library/Application Support/Grok Bot to Grok Bot.bak, then relaunch — reinstall alone will not clear it.
• Grok-spawned Cloud Agents can ignore your non-Fast defaultStaff: Grok-spawned Cursor Cloud Agents can start in Fast even when your default is not; hover Cursor Grok 4.6 → Edit and uncheck Fast, and switch the follow-up box back if it flips.
• Local execution offline while chat still worksStaff: the local-exec helper can register then drop its server link, so the Mac shows offline while chat still works; fully quit and reopen, and if it fails again send ~/.grokbot/local-exec-daemon.log.
• Reset stuck at 50% Starting is a server-side bad stateStaff: a Reset hung at 50% “Starting Grok Bot’s computer” is a bad hosted state, not your install; Bot data is not lost — wait a few minutes, and reply on the thread if it still fails.
• Local CLI orchestration and always-allow are intended useStaff: local-CLI orchestration (including Cursor CLI), always-allow local execution, and authenticated browser sessions are intended Grok Bot use; third-party ToS stay separate, bots share one computer, and a continuous Pro orchestrator burns the weekly pool fast.
• Local-computer helper fails registrationStaff: the local-computer helper can start then fail registration after an update; full-quit plus sign-out recreates it, and desktop 0.31.0 is rolling out.
• Mac black screen is local DNS not cloudStaff: Mac 0.30.0 black screen with working iOS bots is a local network/DNS block to the healthy cloud computer, not a recreate-computer problem.
• Grok Bot does not spend Pro $20 IDE creditStaff: Pro’s $20 Other Models credit is not Grok Bot’s weekly pool; dashboard “Included in Pro” is shared billing — and with On-Demand off the Bot can still drain Cursor credits (referral/promo) before stopping (see 169982).
• Does GrokBot not have access to my Cursor Codebase?Staff: Grok Bot has no codebase plugin and does not index your repo; coding work is handed to a Cursor Cloud Agent on a GitHub-connected account (Dashboard → Integrations), with an optional GitHub PAT connector for read-only, auto-created repos from scratch, and no Origin access yet.
• Phantom in Grok Bot is a MessStaff: the Phantom plugin runs on @phantom/mcp-server and each new auth creates a separate dedicated agent wallet, not your personal Phantom wallet, so reconnects show a new address while funded funds stay on the old agent wallet (recover via chat history or Phantom Support).
• Grokbot custom connectorsStaff: there is no settings form for custom connectors; tell the Bot in chat to add an MCP server (public HTTPS streamable HTTP/SSE), confirm the details, and new tools appear from the next message — localhost-only MCP on your PC is unreachable from the cloud computer.
• Grok Bot: Drive MCP should write Google Docs body and Sheet cells, not only file metadataStaff: in-place Google Doc/Sheet editing lives in the dedicated Docs and Sheets connectors (edit content against the existing file ID), while Drive is file-level only; add both from the connector marketplace with the same Google account.
• Blank screen after opening Grok BotStaff: a blank/white screen usually means the desktop app cannot reach the cloud computer; Cloudflare WARP can intercept that traffic even on a hotspot — turn WARP off or use split tunneling/excluded routes, and prefer builds after 0.28.0 that show an error+retry instead of a blank screen.
• Cloud Agents created in Grok Bot not displayed in CursorStaff: Cloud Agents launched from Grok Bot keep running under your account but stay hidden on cursor.com/agents and the desktop sidebar until you enable filter Source > Grok Bot (once per client: web and desktop).
• Can't reach your computer from last 72 hoursStaff: when the cloud computer is healthy but the app still says Can’t reach, set both IPv4 and IPv6 DNS to 1.1.1.1/8.8.8.8 (JioFiber routers often keep IPv6 DNS) or confirm via a phone hotspot on another carrier.
• Grok Bot 0.30.0 stuck on "Setting up your Grok Bot" on macOSStaff: endless Setting up your Grok Bot on a free Cursor plan means no hosted machine is provisioned — needs Pro/Pro+/Ultra/Teams or linked SuperGrok/Plus/Heavy; the spinner instead of an access message is a known UX bug.
• Grok Bot Zoom plugin OAuth hardcodes http://localhost:8787/callback — Zoom rejects hostname localhost (error 4700)Staff: the catalog Zoom plugin OAuth hardcodes http://localhost:8787/callback, which Zoom rejects (error 4700); no user workaround until the redirect moves off localhost (e.g. 127.0.0.1).
• Unable to reconnect to my Grok Bot's computer after attempted updateStaff: bots/files/logins live on the remote computer; Can’t Reach plus failed Recover/Reset often means a lost app login session — fully quit, sign out/in (or reinstall and sign in), since Recover/Reset need a working session.
• Grok Bot Computer Stuck in Partial State — Reset Failed, Existing Cloud Computer UnreachableStaff: hold off on Reset/Recover after a scary partial-state dialog — data is remote and failed resets often failed on the app side; re-login, verify via mobile on cellular, and try public DNS / disable VPN before resetting.
• Grok Bot couldn't finish setupStaff: Can’t reach your computer on Linux Grok Bot 0.18.0 is not your network — Grok Bot is not officially available on Linux yet and that old build is rejected; supported platforms are macOS, Windows, and iOS.
• Grok Bot 0.30.0 (Windows) — setup fails with Can't reach your computer, all network checks passStaff: the app reaches a per-computer subdomain under cursorvm.com, not the apex — if nslookup test123.us8.cursorvm.com is Query refused while the apex works, change DNS on both IPv4 and IPv6 (router RA can keep the ISP resolver even after 1.1.1.1).
• Grok Bot draining Cursor credit poolStaff: after the Grok Bot weekly pool on Pro+ is gone, usage keeps going onto Cursor credits (referral/promo) first, then on-demand if enabled; a $0 on-demand cap stops paid overage but not credit drain, and claude-opus / grok-4.6-high-fast lines are models the Bot picks server-side.
• Grok Bot templates: preview shows skills, but the export ships skills: [] — skills are never deliveredStaff: Bot template preview lists skills, but import does not apply them (export ships skills: []); until that is fixed, copy the skill body from the preview and ask the new Bot to recreate it.
• Cloud computer wipes packages after rebuildStaff: Update Computer keeps files and logins but rebuilds the OS image, so apt/apps/daemons are gone; the box also sleeps when idle (background processes die) and can auto-update during idle — keep a package list in a file and ask the Bot to reinstall after an update.
• /review-bugbot is missing on cloud agents launched from Grok BotStaff: /review and /review-bugbot do not attach to cloud agents created by Grok Bot (decided at create time); start a new agent from cursor.com/agents on the same PR branch and include /review-bugbot there.
• Grok Bot Bug Report (empty roster / black screen after reconnect)Staff: empty bot list and black/white loading after reconnect usually means the Agent Computer was slow waking from sleep—nothing deleted; do not Reset; fully quit and relaunch once the box is awake.
• Grokbot and GitHub (Connected but Authorization header badly formatted)Staff: GitHub connector shows Connected but fails with “Authorization header is badly formatted”—tracked bug; workaround is press-and-hold the account → Remove, then reconnect and sign in again.
• Authorization death by 1000 clicksStaff: “Always allow” for local-computer actions lives only in the desktop app on that machine; iOS can only one-time-approve, and those approvals clear on every new message—set Always Allow under desktop Settings → Execution on Local Computer.
• Wrangler/box auth reminder stays stuck after auth already succeeded via another pathStaff: the “help on its computer” / Waiting-for-you reminder only clears when you answer that card (“I’m done, continue” or Skip) or send any chat message—it does not auto-dismiss if the Bot finished login another way.
• Fastmail Filters & Rules Save is a silent no-op (Chrome on the box)Staff: Fastmail Settings → Filters & Rules Save on the box Chrome fires zero network requests; workaround is manage filters/Sieve via Fastmail’s API (JMAP) with a token—the mail helper already uses that path successfully.
• VPN, SSO, Passkey, and YubiKey Within GrokbotStaff: Grok Bot’s cloud computer cannot join a corporate VPN today (don’t install a VPN client on it — that can knock the box offline); Atlassian Cloud / public SSO works via browser takeover (Okta etc.), YubiKey works on macOS/Windows under Settings → Security Key, and internal VPN-only sites need Execution on Local Computer on your VPN’d machine.
• Unable to connectStaff: chats and agents live on the hosted Grok Bot computer — during an outage recovery that computer can be temporarily replaced with a blank one (roster looks empty); Cursor can restore it from saved data, then quit and reopen the app to see agents/history again.
• GrokBot Linux Execution on Local Computer not workingStaff: empty ListMachines / local execution failing on Grok Bot 0.30.0 Linux is a known bug with a fix already merged for the next desktop update; interim workaround is an unlocked system keyring (gnome-keyring or KWallet), fully quit leftover Grok Bot processes, then relaunch.
• New report, Windows, leftover daemon on 0.30.0Staff: 0.30.0 fixed one macOS daemon exit/no-respawn path, but Windows leftover local-exec-daemon is a different known failure; when the machine is unreachable, Quit from the tray, end remaining “Grok Bot” and local-exec-daemon processes in Task Manager, relaunch, and wait about a minute to re-register.
• Grok bot failed to respondStaff (kevinn): “Bot failed to respond” on every bot—including fresh copies—means the shared cloud computer is stuck, not something you can fix by restarting or recreating bots; after staff recovery, fully quit (Cmd+Q / force-close iOS), update every install, keep one open, and test in a new chat.
• Grok Bot 0.30.0 Stuck on Black Loading Screen During Initial Setup on MacStaff (Colin): Team admin role alone does not provision a Grok Bot computer — Grok Bot is included with a paid team seat (Standard or Premium), not the admin role. If the signed-in account has no seat, the app sits on the black loading screen with no computer to reset. Fix: assign yourself a seat in Cursor dashboard Members, fully quit and reopen Grok Bot; or sign in with a seated team account.
• Grok Bot: weekly usage hits 100% after bot-to-bot reviews the user asked to stopStaff (mohitjain): Each bot-to-bot message burns a weekly-usage turn; asking bots in chat to “stay quiet” is only a hint. Reliable fixes: run work in one Command Agent with subagents (they finish and stop), and delete unused specialist bots (idle bots can still be woken; deleting also clears that bot’s chat — save first). Double limit banners are blocked retries, not double charges.
• Grok Bot Windows — fresh profile setup fails with “Can’t reach your computer” after backend fixStaff (deanrie): Grok Bot ignores the Windows system proxy / local HTTP proxy and connects direct to the Agent Computer — so DNS/TCP/CONNECT checks through a proxy can pass while the app fails. Use VPN/proxy TUN (Enhanced/Global/virtual adapter) mode, then verify with curl.exe --noproxy "*" -I https://test123.<region>.cursorvm.com (expect 404 awselb/2.0). User confirmed TUN fixed setup. Region may be us10 not us8.
• Grok Bot 0.30.0 stuck on black loading screen on Windows 11Staff (Colin): Healthy cloud computer + black spinner on both LAN and hotspot can be Zscaler Client Connector still tunneling (including on hotspot). Quit Grok Bot, pause/disable Zscaler, relaunch; ask IT to allowlist/exclude SSL inspection for *.cursorvm.com and **.cursorvm.com (both levels).
• Grok Bot cannot attach inline images to Cursor bug reports (chat drop and forum upload)Staff (mohitjain): To get a screenshot into Grok Bot chat, use the composer + button (or drag a saved file) and wait for the thumbnail before send — drag-from-browser/other-app or Enter-before-thumbnail usually drops it. Forum upload by the assistant is a current limitation; attach the screenshot yourself or reply to support email.
• Grok Bot routines don't auto-run on scheduleStaff (Colin): Editing bot instructions or which platform created a routine does not break schedules — late “Next run: Run now” usually means the slot fired but sat in a queue (often 10–37 min), and some runs finish without posting to chat; don’t recreate routines; message the bot for an on-demand check-in.
• Grok Bot 0.30.0 — Agent Computer unreachable after Update, Recover, and Reset all failedStaff (kevinn): An “Aw, Snap!” Chrome page on the Bot screen after idle wake is the Bot’s browser crashing inside a healthy computer — reload the tab or ask the Bot to reload, fully quit/reopen Grok Bot if needed, and do not run Update/Recover/Reset; idle machines take a moment to wake and a first message can miss, so resend is safe.
• Grok Bot Mac “unavailable” after password reset (expired session)Staff (deanrie): After a password reset, Grok Bot on Mac can keep an expired session and show “isn’t available on this account yet” even though SuperGrok/Cursor access and your cloud computer/Bots are fine — Log out from the bottom of that screen, fully Quit (Cmd+Q), reopen and Sign in with the new password; Check Access→download is a misleading expired-session UI, not a missing entitlement.
• Homepage “Approval needed” stuck after card timeoutStaff (Colin): A homepage “Approval needed” tile with nothing pending usually means an approval card timed out (~10 minutes unanswered); open the agent and send a short message or restart the app to clear a stuck badge — the tile is supposed to clear when the card expires.
• File contents and grokbot — viewer Copy vs DownloadStaff (Colin): The in-app file viewer only offers Download today; for .md/.txt you can click-drag to select and Cmd/Ctrl+C, while .docx/.pdf won’t highlight — ask the Bot to paste the full text into chat and use the message Copy action as a workaround.
• Grok Bot Canva connector failing — Invalid redirect URI on iOSStaff (deanrie): Canva “Invalid redirect URI” on Grok Bot iOS 1.4.0 is a known app-link vs web-redirect mismatch (not your Canva settings) — connect Canva from desktop Grok Bot on the same account and the connector syncs to iPhone.
• Local computer looks connected but CopyFromBox/Shell flaps after large transfer timeoutStaff (deanrie): A large CopyFromBox (or timed-out Shell) can drop the local machine from the agent list for ~1 minute while Settings still says connected — split big copies, wait a minute before retrying, and if stuck Cmd+Q then pkill -f local-exec-daemon and reopen.