Grok Bot 0.44.0 macOS — “Can’t reach your computer”; Retry and Recover fail even after re-login

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

Grok Bot previously worked, but now I cannot access my Bot computer or load my Bots.

Initially, the app showed “Can’t Reach Grok Bot’s Computer” and suggested allowing *.cursorvm.com. It now shows:

Can’t reach your computer. Your Bots are safe, they just can’t be loaded right now. If it doesn’t come back on its own, recover it. Your files and logins are kept, but installed apps and packages are removed.

Retry stays on “retrying,” and Recover fails with “unable to reset.”

Already tried without success:

Fully quit and reopened Grok Bot.
Signed out and signed back in.
Retried the connection and attempted Recover.
Network checks:

test123.us9.cursorvm.com and test123.us10.cursorvm.com resolve through the configured DNS, ISP DNS, 1.1.1.1, and 8.8.8.8.
HTTPS requests to cached computer endpoints under *.cursorvm.com return HTTP 404, confirming DNS/TLS/HTTP connectivity—not that the assigned computer is healthy.
Wi-Fi HTTP, HTTPS, and SOCKS proxies are disabled.
The remote computer previously accessible through Tailscale was reported offline during troubleshooting.
Please check my assigned cloud computer and any failed or stuck recovery operation. I would like to restore access while preserving my Bots, files, and logins. I cannot access the remote desktop or terminal to troubleshoot it directly.

Steps to Reproduce

Open Grok Bot and sign in to my existing account.
Attempt to load my existing Bots/computer.
The app displays “Can’t reach your computer.”
Click Retry — it remains retrying and does not reconnect.
Click Recover — it fails with “unable to reset.”
Fully quit/reopen and sign out/in — the same issue persists.
Expected: The existing computer reconnects, or Recover successfully restores it.

Actual: The computer remains inaccessible, and both Retry and Recover fail.

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Product: Grok Bot desktop app, not Cursor IDE
Version: 0.44.0
OS: macOS 15.6.1
Issue observed: September 8, 2026, IST (UTC+05:30); previously working the day before
Request/conversation ID: Not available from the inaccessible Bot screen

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Hey, thanks for the detailed report and the screenshot. I can see that same screen with *.cursorvm.com / Zscaler.

Good news: this isn’t a network issue or DNS, and your Bot computer isn’t “broken”. The cause is different: the 1-week free trial for Grok Bot on your account ended on 6 September at about 1:23 IST, overnight into the 7th. After that, the app can’t connect to the computer anymore, and Retry and Recover can’t fix it because the account doesn’t have active Grok Bot access right now. The app should show this directly instead of “can’t reach your computer”. This is a known issue with how this state is displayed, and I’ve shared this case with the team.

Your Bots, files, and logins are saved. They’ll be available again as soon as your account has access:

  1. Go to Sign in on the same account and pick a plan that includes Grok Bot.
  2. If you already have a SuperGrok subscription on grok.com, link it at Cursor - The best way to code with AI using the same email.
  3. Then fully quit Grok Bot from the menu bar icon, reopen it, and sign in with the same account.

If after step 3 you still see “Can’t reach your computer”, reply here and I’ll take another look.