Fix Grok Bot “Can’t reach your computer” behind a system-proxy VPN (use TUN)

Cursor staff (deanrie, Sep 2, 2026): the Agent Computer can be healthy on Cursor’s side while the PC still cannot connect. Recreating the computer is not needed and will not help for this case.

Grok Bot does not use the Windows system proxy or a local HTTP proxy such as 127.0.0.1:7890. It connects directly. DNS, TCP, CONNECT, and TLS checks that travel through the proxy can pass while the app’s direct path gets reset. A US/Japan VPN left in system-proxy mode is not picked up by the app.

Staff’s example region host was us10 (*.us10.cursorvm.com). Testing a different region (for example us8) will not hit the host your computer uses.

Switch the VPN to TUN, then verify

Staff steps (Windows):

1. Fully close Grok Bot. In Task Manager, end all Grok Bot processes.
2. In the VPN or proxy client, switch from system-proxy to TUN mode. Clients may label this Enhanced, Global, Virtual network adapter, or TUN. That mode tunnels apps that ignore proxy settings.
3. In PowerShell, run a direct check against your computer’s region host (staff used us10 for that account):

curl.exe --noproxy "*" -I https://test123.us10.cursorvm.com

Replace us10 with the *.cursorvm.com region staff or diagnostics name for your Agent Computer.

4. Expect a quick HTTP/1.1 404 Not Found with Server: awselb/2.0 when TUN works. Hang, timeout, or connection reset means TUN still inactive — the app will fail the same way.
5. Once step 3 returns 404, start Grok Bot and let setup run again.

No TUN mode on your client

If the VPN/proxy app has no TUN / Enhanced / Global / virtual-adapter mode, tell staff which app you use. There is no other documented alternative in that thread.

Related reachability paths

• General recover order, DNS, hotspot, and temporary VPN disable: Fix Grok Bot “Can’t reach your computer”.
• Reaching corporate VPN-only work apps from the Bot computer (different direction): Reach VPN-only work apps from Grok Bot.

White screen on an old profile

Staff separated a white screen plus black-dot symptom on an old profile as a display issue in 0.30.0, fixed in a later update. A fresh profile was the right move for that display bug. It is separate from the system-proxy / TUN connectivity fix above.

Pitfalls

• Proxy-path success in a browser or curl without --noproxy "*" does not prove the app can connect.
• Recreating or Resetting the Agent Computer will not fix a local system-proxy tunnel miss.
• Keep TUN on while you need the VPN; do not assume every “Can’t reach” case wants VPN fully off.