Where does the bug appear (feature/product)?
Grok Bot
Describe the Bug
Grok Bot cannot connect to its hosted computer on macOS. The startup screen says “Can’t Reach Grok Bot’s Computer” and mentions firewall/VPN/proxy and *.cursorvm.com. After fully quitting and reopening the app, the main interface loads, but the Bots sidebar still says “Can’t reach your computer”.
I then used Recover computer and retried the reset once. Both attempts failed with: “The reset couldn’t finish. Grok Bot’s computer may be in a partial state — retry to run the reset again.” The computer remains unavailable. Please inspect the Agent Computer on the backend and help recover it while preserving existing data where possible.
Steps to Reproduce
- Open Grok Bot on macOS.
- Observe the computer connection error.
- Fully quit and reopen: the app shell loads, but the Bots sidebar reports the computer is unreachable.
- Click Recover computer.
- Observe Reset failed / possible partial state.
- Retry Reset once: the same failure occurs.
Expected Behavior
The hosted computer should reconnect and load my Bots. If recovery is needed, it should complete successfully rather than leave the computer unavailable.
Operating System
MacOS
Version Information
Grok Bot desktop 0.44.0
macOS
For AI issues: which model did you use?
N/A — this is a hosted computer connection/recovery issue.
Additional Information
Network troubleshooting already performed:
- Clash Verge with TUN enabled.
- HTTPS requests through the local proxy reach the Cursor API (HTTP 200) and the documented cloud-computer test endpoint (HTTP 404 with a successful TLS connection). This verifies those endpoints are reachable, not that my actual hosted computer is healthy.
- Tried the existing Japan proxy node and an alternative US node; switching nodes and retrying did not resolve the app error. Restored the original node.
- Fully quit/reopened Grok Bot and tried Retry.
- Stopped further resets after two failed recovery attempts.
This appears similar to Grok Bot Agent Computer stuck in partial state on Mac and iOS, but I cannot confirm the same root cause for my account. Please check the backend state.
The app also displayed a Pro/SuperGrok subscription prompt after reopening; I do not know whether that is related to the computer failure.
Does this stop you from using Cursor
No - Cursor works, but with this issue