Hey, thanks for the detailed report. The network checks you included really helped.
You’re right, this isn’t a local connection issue. On that screen, “your computer” doesn’t mean your Mac. It means the cloud computer that Grok Bot spins up on our side, and that machine isn’t coming up for your account. The “check your connection” wording is misleading, your network is fine.
This is on our side, and we’re tracking it. Your account is one of the affected ones. There isn’t a user workaround right now. Retrying, reinstalling, and clearing cache won’t change anything, which is why you still saw the same errors after reinstalling 0.23.0. Reset Agent Computer also isn’t available because the computer has never been created even once.
Please keep the app updated and try again a bit later. I’ll reply here as soon as there’s an update.
Grok Bot gets stuck on a black “setting up” screen because your home router’s DNS cannot look up the special web address for Grok Bot’s cloud computer (*.cursorvm.com). The app can still sign you in, but then it waits forever because that address never resolves, so the window looks blank.
Fix: stop using the router for DNS and switch your Wi‑Fi to public DNS instead — Cloudflare 1.1.1.1 and Google 8.8.8.8 — then turn off “automatic DNS from router” (ipv4.ignore-auto-dns yes in NetworkManager / nmcli). Make it permanent on your Wi‑Fi connection, reconnect, confirm the cursorvm.com address resolves, and reopen Grok Bot.
I used Grok to help me fix the issue, and it worked!
Same first-setup failure on Grok Bot 0.24.0 (macOS): createAgent failed / “Can’t reach your computer.” Network looked fine (us8.cursorvm.com resolved + TLS ok, api2.cursor.sh 200). Switching Wi‑Fi DNS from the router/ISP to Cloudflare 1.1.1.1 and reconnecting made setup complete.
Hey, thanks for coming back and closing the loop. This is a really helpful data point, especially with the Xfinity/Comcast resolver details.
I can see the DNS Servers screenshot where 1.1.1.1 is set. Switching DNS from your ISP/router to a public resolver like Cloudflare 1.1.1.1 or Google 8.8.8.8 is a valid workaround for this kind of issue. If the ISP resolver is returning bad or inconsistent records for *.cursorvm.com, the client can’t reach the cloud computer even if the rest of Cursor’s APIs are working. So your recommendation is spot on. If createAgent fails but Cursor APIs still respond, the first thing to try is 1.1.1.1 or 8.8.8.8 before assuming the box itself is broken.
One note for anyone who finds this thread later. Not every failure like this is DNS related. Some cases are truly server-side, and switching DNS won’t help. But as a quick first step, it’s cheap and often fixes it.
I’ve shared your case with the team along with the resolver details. If it happens again, post here.
Windows Grok Bot version 0.28.0 is also the same issue， and restart Grok Bot, Grok Bot GUI show all blank, no any UI, using cursor to check and test network is OK, can’t how to solve this issue
It looks like your boxes are now up and running, so I’ll go ahead and close this thread. Please don’t hesitate to open a new one if you run into any other issues.
A big thanks to @Josh2 and @simpleshadow for sharing the DNS workaround! It’s a great help for users whose boxes are healthy but who can’t establish a network connection to them. This affects users in certain regions, and we’re actively working on a fix to make the workaround unnecessary.
windows
