When a duplicate Agent Computer blocks “Can’t reach”

“Can’t reach your computer” plus Reset stuck in partial state is sometimes a backend duplicate, not VPN, login, or a broken client. Staff on forum 171186 (mohitjain, Sep 10, 2026): the account had two Agent Computer copies; the app pointed at the copy that never finished starting, while bots lived on the other.

What staff said

• Cause is on Cursor’s side, not network or sign-in.
• Stop pressing Reset / Update / Recover for now — those controls cannot finish in this state and risk the healthy copy.
• Bots, files, and logins on the good copy stay safe while staff reconnects manually.

Windows and Android both failing together with partial-state Reset text is a strong match for this class on that thread.

What to do

1. Stop the Reset / Update / Recover loop.
2. Collect app version(s), OS on each device, exact error / partial-state wording, Bot names, and time zone.
3. Use in-app Send Feedback (or reply on the forum thread) and ask staff to reconnect the healthy Agent Computer on the backend. Say you want chats and files kept.
4. After staff confirms the reconnect, fully quit the app on each device, reopen, and send a short smoke message before you touch Reset again.

Nearby paths (different causes)

• Stale client session while the computer is healthy: Fix “Can’t reach” when the session is stale.
• Every client control fails and needs a backend reset: When client Update, Recover, and Reset all fail.
• General triage order: Fix Grok Bot “Can’t reach your computer”.

Pitfalls

• Partial-state after a failed Reset is its own recovery guide: Fix Grok Bot Reset stuck in partial state.
• Do not paste passwords, tokens, or one-time codes into feedback.
• Pausing burn while the computer is unreachable: Pause routines when Agent Computer is unreachable.