Reattach Windows Grok Bot after sign-in with Android sync

On Windows (reported on 0.39.0), signing out and back in can leave the desktop app on Reconnecting to your computer… with No saved Bots yet, even when DNS and HTTPS to *.cursorvm.com succeed. The bots may still exist remotely; the Windows client never gets a fresh gateway / computer descriptor.

A Sep 4, 2026 forum report (George_Burchell) cleared it without Recover or Reset: install Grok Bot on Android, sign into the same Cursor account, accept sync with your computer, then watch Windows reconnect with bots, messages, and routines intact. Staff (Colin) had asked for a Grok Box restart in that thread; the OP’s Android sync path is what restored the roster.

Try this before Recover

1. Confirm network basics on Windows: *.cursorvm.com resolves, TCP 443 works, no forced proxy/VPN blocking the path (see Fix “Can’t reach your computer” in Grok Bot).
2. Fully quit Grok Bot (tray Quit), reopen, same account.
3. Install Grok Bot from Google Play on an Android device (Install Grok Bot on Android).
4. Sign in with the same Cursor account that owns the Windows bots.
5. When Android offers to sync with your computer, accept.
6. Return to Windows — wait for reconnect. Existing bots should reappear without creating new ones.

When this is the right cluster

Use this path when:

• Sign-out / sign-in on Windows emptied the sidebar or stuck on reconnecting.
• Phone or another device can still reach the account.
• You have not already wiped state with Reset.

Prefer other how-tos when:

• Bots vanished after Recover → Find Grok Bots that vanished from the sidebar after Recover.
• Active Sessions revoke made apps show a fake can’t-reach → Fix Grok Bot after Active Sessions revoke.
• No Bot plan is linked → Fix can’t-reach when no Bot plan is linked.

Official computer order still applies

If Android sync is unavailable, follow Bot troubleshooting: Retry → restart app → Recover Agent Computer when offered → Settings → Beta → Update Agent Computer → Reset Agent Computer only if you accept losing recent unsynced work. Recover / Update preserve durable files and logins when they succeed.

Pitfalls

• Sync must use the same account ID you verified on Windows.
• Do not create a brand-new Bot on Android first if your goal is to reattach the old computer — accept the sync prompt for the existing computer.
• Privacy Mode Active was present in the report; staff did not call Privacy Mode the cause of this gateway miss.