Grok Bot Computer Stuck in Partial State — Reset Failed, Existing Cloud Computer Unreachable

[Jerell]

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

Grok Bot initially disconnected, so I attempted Reset Grok Bot’s Computer. The reset failed with the message:

“Reset failed. The reset couldn’t finish. Grok Bot’s computer may be in a partial state — retry to run the reset again.”

Retrying the reset failed again. Afterward, the Grok Bot Windows desktop application stopped opening. I rebooted Windows and later reinstalled the latest Grok Bot Windows client.

The application now opens again, but the existing Grok Bot computer remains stuck on “Reconnecting” and then shows “Couldn’t Reach Grok Bot’s Computer.”

The affected environment contains established bots/agents, files, logins, configurations, conversations, and ongoing work. My priority is a data-preserving recovery of the existing cloud computer, not deletion, replacement, reset, or recreation.

Affected Conversation ID:
78994b14-2acc-4000-b23e-3ef77481b871

Steps to Reproduce

Opened Grok Bot on Windows.
The existing Grok Bot computer showed as disconnected/unavailable.
Selected Reset Grok Bot’s Computer.
The reset failed with: “Reset failed. The reset couldn’t finish. Grok Bot’s computer may be in a partial state — retry to run the reset again.”
Selected Retry Reset.
The reset failed again with the same error.
After the failed reset attempts, the Grok Bot desktop application would no longer open.
Rebooted Windows; the issue remained.
Reinstalled the latest Grok Bot Windows application.
Opened Grok Bot again.
The application now launches, but the existing Grok Bot computer remains stuck on “Reconnecting” and then shows “Couldn’t Reach Grok Bot’s Computer.”

Affected Conversation ID:
78994b14-2acc-4000-b23e-3ef77481b871

Expected Behavior

The existing Grok Bot cloud computer should reconnect successfully and remain accessible with its current bots/agents, files, logins, configurations, conversations, and ongoing work preserved.

If the cloud computer enters a partial or failed state, the reset/recovery process should either complete successfully or restore access to the existing environment without requiring deletion, replacement, or recreation.

My expected outcome is a data-preserving recovery of the existing Grok Bot environment.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Grok Bot for Windows — Version 0.30.0

For AI issues: which model did you use?

Grok Bot — N/A / not model-specific. This issue is with the Grok Bot cloud computer/environment becoming unreachable and stuck in a partial state, not with a specific AI model response.

For AI issues: add Request ID with privacy disabled

N/A — I do not have a Request ID for this incident. This is a Grok Bot cloud computer/environment failure, not a failed individual AI model request. The affected Conversation ID is 78994b14-2acc-4000-b23e-3ef77481b871.

Additional Information

I have already contacted Cursor Support directly regarding this issue. Support advised that my existing bots, files, and logins are currently being treated as intact and that the case is being escalated to a teammate for a data-preserving recovery of the existing environment.

Because of that, I am intentionally not performing any additional Reset, Recover, Delete, Replace, Recreate, or Update Computer actions while this is being investigated.

This environment is important and contains established AI agents/bots, project files, configurations, authenticated logins, conversations, and ongoing development work. Preserving the existing Grok Bot computer and its data is my highest priority.

I have also seen several recent Cursor forum reports involving Grok Bot computers becoming unreachable, stuck in partial states, or requiring backend intervention. This may indicate a broader cloud-computer/backend issue rather than a local Windows installation problem.

Affected Conversation ID:
78994b14-2acc-4000-b23e-3ef77481b871

Grok Bot Version:
0.30.0

Please check whether the existing cloud computer can be repaired or unstuck from the backend without deleting or recreating the environment.

Does this stop you from using Cursor

No - Cursor works, but with this issue

[deanrie]

Hey, thanks for the detailed report. And good call holding off on Reset or Recover, that’s the right move here.

First, the key point: your bots, files, logins, and configs live on the remote computer, not on your Windows PC. Reinstalling the app won’t touch them. And those failed Reset attempts seem to have failed on the app side and didn’t change anything in your environment, so the “partial state” message in the dialog sounds scarier than it really is.

I had the exact same case a few days ago, “Couldn’t Reach Grok Bot’s Computer” plus Recover or Reset failing, and it was fixed by a simple re-login. The app was losing the session in the background and getting stuck. Try this in order:

1. Fully quit Grok Bot, the entire process, not just the window. Check Task Manager to make sure nothing is still running. After a failed reinstall, an old instance can sometimes keep running.
2. Open it again, sign out in the app, then sign in with your current password.
3. If you can’t sign out or sign back in, reinstall the app and sign in again. Your data is on the remote computer, so nothing will be lost.

To confirm your environment is intact, install the Grok Bot mobile app, connect using mobile data (not your home Wi-Fi), and log into the same account. If your bots and files show up there, your environment is definitely fine, and the issue is local to your PC or network. In that case, try switching DNS to 1.1.1.1 or 8.8.8.8, temporarily disable VPN, firewall, or any network filters, then open the app again.

No need to run Reset or Recover, keep leaving them alone. Let me know how the re-login and the mobile test go, and what you see on the sign-in screen, and we’ll take it from there.

[Jerell]

Dean Rie,

Resolved — signing out of Grok Bot and signing back in fixed the issue. This was the one step I hadn’t tried yet

The existing Grok Bot computer reconnected successfully, and my environment appears to be intact. This looks like it was a Windows app session/authentication issue rather than damage to the cloud computer.

No additional Reset, Recover, or rebuild was required.

Thank you very much for the quick help and for pointing me in the right direction. I really appreciate it.

[deanrie]

Hey, glad that helped! Signing out and signing back in is the most common fix for this case. The app can lose its session in the background and get stuck on Reconnecting even though the cloud computer itself is fine. So your instinct not to touch Reset or Recover was totally right, nothing had to be recreated.

If you hit Couldn’t Reach Grok Bot’s Computer again, first fully close the app and check in Task Manager that the process isn’t still running, then sign out and sign back in. That fixes it most of the time.

Marking the thread as solved. Let me know if anything else comes up.

[repiatx (Hayrettin GÖK)]

Im stuck at “Setting up grok bot’s computer” cant logout. It stucks like this afterwards.

[Evan1 (Evan)]

Same with me right now.

[Colin]

@repiatx let’s continue over here!

Grok Bot 0.30.0 stuck on “Setting up your Grok Bot” on macOS

Hey @Mao_Wang, good news first! We checked your account and Grok Bot access has been active on it since Aug 30. There is nothing to rebuild or reprovision on our side. What we see now is that since then, no request from your Grok Bot app has reached our servers at all, not even a failed one. That means the app’s traffic is being dropped somewhere on the network path from your Mac, which matches the timeout you saw when entering the display name. Could you try this and tell us what happens: F…

@Evan1 I’ve tweaked some knobs on the backend. If you’re still facing an issue, please create a new thread.

Since @Jerell marked the original issue solved, I’m going to close this thread.