Fix Grok Bot after a failed Reset leaves a partial state

A Reset Agent Computer can hang on “Wiping your data,” then fail with Reset failed. The reset couldn’t finish. Grok Bot’s computer may be in a partial state. Forum reports (Windows Grok Bot 0.30.0, Sep 2, 2026) then show a first-run “Create your first Bot” screen, Recover bringing sidebar Bots back, and Couldn’t Reach Grok Bot’s Computer that Retry does not clear. Generic reachability steps: Fix Grok Bot “Can’t reach your computer”. Sidebar empty after Recover: Find missing Grok Bots after Recover.

Stop the damage

1. Do not run Reset again. A second wipe on a partial-state computer is the riskiest move while the first job may still be stuck.
2. Fully quit Grok Bot (not only close the window).
3. Sign out and sign back in with the same Cursor account if the app still shows first-run with no chats.
4. Choose Recover / Recover Agent Computer when offered — not another Reset.

Official troubleshooting still ranks Recover and Update Agent Computer above Reset. Recover and Update preserve durable files and logins. Reset restores the last saved snapshot and can drop recent unsynced work.

If Bots return but the computer stays down

Reported healthy local network does not prove the Agent Computer finished recover:

1. Retry once, then fully restart the app.
2. Open Settings → Beta → Update Agent Computer if Recover already ran and the computer stays unreachable.
3. Check phone hotspot or a different network only as a network control. Forum reporters saw DNS and HTTPS to *.cursorvm.com succeed while the app still showed firewall/Zscaler copy after a partial reset — treat that banner as possibly stale after a failed wipe.
4. Skip inventing a second Reset or a manual VM rebuild. Cursor staff (Kevin Neilson) said they were investigating the Sep 2 partial-state report on their side.

Collect for support

Include: Grok Bot version (for example 0.30.0 Stable), OS, exact Reset-failed and can’t-reach text, whether Recover restored the sidebar, approximate time and time zone, and that a second Reset was not run. Skip passwords and secrets. File or bump a Cursor forum Bug Report so staff can clear a stuck reset/recover job if the computer is unhealthy on their side.

Pitfalls

• First-run UI after a failed Reset does not mean every Bot was deleted; Recover can restore the sidebar while the VM stays disconnected.
• Successful nslookup / curl to the published Agent Computer test host does not clear a stuck reset job.
• iPhone builds may only show Retry on can’t-reach; finish recover/update from desktop when you have one on the same account.