Fix Grok Bot can’t-reach after you revoke Active Sessions

You cleared sessions on cursor.com (Active Sessions / Sign out everywhere). Desktop or iOS Grok Bot then shows can’t reach your computer, Retry, Update, or Reset that do nothing. Bots and routines can still be running on the account. Cursor staff (Colin, Sep 4, 2026) traced this to a dead app session that the client mislabels as a connection problem. A Grok Bot version bump (for example 0.39.0) is not the cause.

This path is separate from a password-reset “unavailable” screen and from a real network can’t-reach.

Sign out of the app, then sign in again

Staff recovery:

1. On each stuck device, open Grok Bot.
2. Sign out from the app (account / signed-in row). Do this even when the error looks like a computer problem.
3. If Sign out is missing, fully quit the app first — on Mac, quit from the Dock or menu bar tray so it is not left suspended — then reopen and Sign out.
4. Sign in again with the same Cursor account in the browser, then return to the app.
5. Wait for the computer to reconnect. Retry a simple Bot action.

Repeat Sign out → Sign in on every Mac, Windows, and iPhone install that still shows can’t-reach after the Active Sessions revoke.

What not to burn first

1. Skip Update Agent Computer / Reset Agent Computer until Sign out → Sign in has failed on that device. Staff said the computer and bots were still fine while the app held a revoked session.
2. Skip a second Cursor account. The access is on the same account; the client needs a fresh session.
3. Privacy Mode is unrelated to this mislabel; do not flip it to “fix” can’t-reach after an Active Sessions revoke.

Confirm it was a session revoke

1. Check whether you (or someone with account access) clicked Sign out / revoked sessions on cursor.com around the time the app broke.
2. If bots kept running in the cloud while the desktop showed can’t-reach, treat that as evidence the hosted computer is up and the local session is stale.
3. If Sign out → Sign in does not clear it, collect the exact error string, Grok Bot version, OS, and approximate UTC time, then reply on the forum thread or contact support. Distinct from Fix Grok Bot “Can’t reach your computer” and Fix “Grok Bot isn’t available…” after a password reset.

Pitfalls

• Retry / Update / Reset on a revoked-session client wastes time; Sign out → Sign in is the first move.
• Quit from the Dock/tray when Sign out is missing — a suspended Mac app can keep the dead session.
• Revoking Active Sessions again without signing the apps back in will recreate the same stuck state.