Fix “Can’t reach your computer” when the session is stale

Grok Bot’s “Can’t reach your computer” screen often points at network or Agent Computer problems. Sometimes the cloud computer is healthy and DNS works — the desktop (or phone) client is holding an outdated or invalid session. Staff confirmed that case on Grok Bot 0.39.0 macOS — can’t reach computer.

What stale session looks like

From the thread’s logs and Cursor staff reply:

• The UI still shows “Can’t reach your computer” with firewall / DNS wording.
• Client logs can show client_online=true together with ConnectError.Unauthenticated on profile, privacy, team, or entitlement checks, and access_denied on cloud-computer calls.
• The same account may fail from more than one device until you re-authenticate.
• Phone and desktop can disagree until both get a fresh session.

That is distinct from a dead Agent Computer, a blocked *.cursorvm.com path, or a missing plan link. For those paths, start with Fix Grok Bot “Can’t reach your computer” and Fix can’t-reach when no plan is linked.

Fix it: sign out and sign back in

1. Open Grok Bot Settings and confirm the signed-in Cursor account matches the one that works on your other device (if you have one).
2. Sign out of Grok Bot on the failing device.
3. Sign in again with the same Cursor account and finish the browser login.
4. Wait about two minutes for the client to reattach to the cloud computer.
5. If the message remains, fully quit the app (Cmd+Q on macOS), reopen, and sign in once more.

Staff’s guidance after the logs: re-logging in is the reliable recovery for this class of failure. They also noted the firewall/DNS copy can appear on auth failures, so network triage alone will not clear a stale token.

Checks that do not fix a stale session

Skip these once DNS and api2.cursor.sh / a regional *.cursorvm.com host already connect (any HTTP status that proves TCP works, including 404):

• Rebuilding or resetting the Agent Computer as the first step
• Changing Privacy Mode when staff already say it was saved correctly
• Allow-listing a misspelled hostname (the product uses *.cursorvm.com with a v, not cursorrm.com)

Use When a computer rebuild won’t fix Grok Bot if you are about to Reset.

Pitfalls

• Signing out refreshes the client session; it does not delete your Bots or wipe the shared cloud computer by itself.
• If Reset / Update / reinstall loops after a backend partial state, stop and follow staff guidance on that thread — see Fix Grok Bot Reset stuck in partial state.
• Collect version, OS, exact error text, and whether phone and desktop agree before filing a new forum report.