Grok Bot can’t reach computer — white loading dot

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

Grok Bot desktop on Windows will not finish setup.

Plan: SuperGrok

Privacy Mode is Active.
After sign-in I get “Can’t reach your computer right now,” then a white screen with a loading dot. It has stayed that way for hours.
Tried: Try again, full quit, relaunch, rename the Roaming Grok Bot folder. Same result.
Expected: the Bot UI should load so I can create a Bot.

Actual: cloud computer never becomes reachable.
This does not stop me from using Cursor.
Please rebuild the agent computer for this account.

Steps to Reproduce

Install Grok Bot for Windows and open the app.
Sign in with Cursor account (SuperGrok on this email).
When prompted, leave Legacy Privacy Mode and set Cursor Privacy Mode to Active.
Return to Grok Bot. The app shows a white window with a loading dot.
After a while it shows: “Grok Bot couldn’t finish setting up” / “Can’t reach your computer right now.”
Click Try again, fully quit the app, and reopen it.
Sign in again when Cursor asks.
Onboarding briefly appears (“Meet Grok Bot”), then it goes back to the white loading dot.
Wait several hours and retry. Same loading dot.
Rename %APPDATA%\Grok Bot to Grok Bot.bak and relaunch so a new Grok Bot folder is created. Issue remains.

Expected: Setup finishes and the Bot UI loads.

Actual: Cloud computer never becomes reachable; app stays on the white loading dot.

OS: Windows 11

Expected Behavior

After signing in and switching off Legacy Privacy Mode, Grok Bot should finish creating/connecting to the agent computer and open the normal UI so I can create a Bot and give it a task.
It should not stay on a white loading dot for hours or fail with “Can’t reach your computer right now”

Operating System

Windows 10/11

Version Information

version Information

App: Grok Bot desktop (Windows)
Version: unknown — UI never loads, so I can’t open Settings / About
OS: Windows 11
Account: alex @ kaglew.com

To grab the version if you can:

File Explorer → C:\Users\al kagian\AppData\Local\Programs\Grok Bot
Right-click Grok Bot.exe → Properties → Details
Look for File version or Product version

Does this stop you from using Cursor

No - Cursor works, but with this issue

3

Account email: alex at kaglew.com

6

Hey, thanks for the detailed report. We’re checking the Agent Computer status on your account. A couple things that will help us narrow this down faster:

  1. How did you sign in to Grok Bot, via Grok/X account, Google, or email? And is your SuperGrok subscription on that same Grok account? If the subscription is on a different Grok login, sign-in can succeed but the plan won’t be picked up. It looks exactly like a setup failure.

  2. Are you behind a VPN, proxy, or on a work network? This is a common cause. The app connects to Agent Computer directly and does not use the Windows system proxy or a local HTTP proxy like 127.0.0.1:7890. So DNS/443/TLS checks through the proxy can look fine, but the app bypasses it, and the direct connection fails.

If you do have a proxy or VPN, try this:

  • Fully close Grok Bot, then in Task Manager end all Grok Bot processes.
  • Switch your VPN or proxy client from system proxy mode to TUN mode. Different clients call this Enhanced mode, Global, or Virtual network adapter. This routes all apps through the tunnel, including apps that ignore proxy settings.
  • Open PowerShell and run this command. It’s meant to bypass the proxy, like the app does:
    curl.exe --noproxy "*" -I https://test123.us10.cursorvm.com
    If TUN is working, you should quickly get HTTP/1.1 404 Not Found with Server: awselb/2.0. If it hangs, times out, or shows connection reset, the app will fail the same way, so TUN still isn’t active.
  • Once curl returns 404, launch Grok Bot and run setup again.

Switching Privacy Mode from Legacy to Active was the right move. That isn’t the cause.

Tell me what curl returned and which sign-in method you used, and we’ll dig into your account from there.

7

Hi @alex_kagianaris

Your box should be working again, please let us know if it’s not.