Grok Bot
When client Update, Recover, and Reset all fail
When client Update, Recover, and Reset all fail
Official Grok Bot troubleshooting tells you to Retry, restart the app, then Recover, then Update Agent Computer, and only then Reset. Sometimes every client control fails the same way: Update sticks mid-transfer and ends in “Update failed,” Recover fails, Reset hangs at “Starting…” and falls back to Update failed again, and both desktop and phone show “Can’t reach your computer.”
On thread 170258, Cursor staff (kevinn) fixed that class of outage with a backend reset and update of the Agent Computer. Client-side buttons alone were not enough.
Confirm you are in this class
- The error is on Mac and iPhone (or every device), not one desktop with a healthy phone.
- Settings → Update Agent Computer fails (often mid “Transferring your data”).
- Recover computer fails.
- Reset Agent Computer stalls, then returns to Update failed.
- DNS / hotspot / VPN checks already look fine, or you already ruled out plan and seat issues.
If only one desktop is broken while iPhone works, start with session and attach paths instead: Fix can’t-reach from a stale Grok Bot session and Fix Grok Bot can’t reach computer.
What to do
- Stop looping Update / Recover / Reset. Each failed Reset can leave more partial state.
- Collect version, OS, exact error text, Bot name, time zone, and any request / conversation ID (troubleshooting checklist).
- Use in-app Send Feedback (or the forum) and ask staff to restore the Agent Computer on the backend. Say you want chats and files kept.
- After staff confirms a backend fix, fully quit the app, reopen, and retry a short message before you touch Reset again.
When rebuild is the wrong ask
Many “please rebuild” threads are actually plan, seat, or network problems where the computer was already healthy. Triage that first: When a computer rebuild will not fix Grok Bot.
Pitfalls
- Partial-state after a failed Reset is its own path: Fix Grok Bot Reset stuck in partial state.
- Chrome “Aw, Snap!” / Error code 9 on a reachable computer is shared RAM pressure, not a failed Update: Fix Chrome OOM / Error code 9.
- Do not paste passwords, tokens, or one-time codes into feedback.