Grok Bot 0.43.0 Windows — Reset failed (partial state), still unreachable — ticket T-F58206 waiting for backend recreate

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

Grok Bot shows Can’t reach your computer. Bots and chats cannot load. A previous Reset failed with partial state.

Official ticket T-F58206. Sam (AI support) asked for Privacy Mode plus one Reset, then said a teammate would follow up for backend recreate. About 48 hours later there is still no human follow-up and the computer is still unreachable.

Steps to Reproduce

  1. Windows 10 19045, Grok Bot 0.43.0 Stable.
  2. Computer already unreachable after an earlier failed Reset (partial state).
  3. Settings (Ctrl+Shift+J) has only General, Computer, Updates. No Privacy Mode control (not Legacy).
  4. Settings then Updates then Reset Grok Bot Computer, once. Result: Reset failed. The reset could not finish. Grok Bot computer may be in a partial state.
  5. Did NOT click Retry Reset.
  6. Sign out/in, Recover, Update Agent Computer, and network checks already done earlier. Test hosts on cursorvm return HTTP 404 from awselb. No change.

Expected Behavior

After the ticket was escalated for backend recreate, the existing Agent Computer should be repaired/reprovisioned so the app can connect again. Client-side Reset should not leave the computer stuck in partial state.

Operating System

Windows 10/11

Version Information

Grok Bot 0.43.0 Stable (Windows 10 build 19045)

Additional Information

Ticket T-F58206. Sam on 2026-09-07 21:06 UTC+3 said a teammate would follow up. Email follow-ups on 2026-09-08 and 2026-09-09, no human reply.

Cursor user ID: auth0 user_01KYCXH2GZ53VR82JNFB6CW360
Grok Bot account slot: 1d21a825ed1884ec3ea86ea73272646495a166a4a13f1a4f388bcd6a4c137f19
Conversation ID: not available. Left sidebar has no agents, only the unreachable error.

Please ping Colin or deanrie for a backend recreate. Same class as other partial-state VM tickets. Do not ask me to Reset again.

Related forum topics: 170373 and 170006.

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hi @smolen2011 Thank you for the post.

Cursor isn’t offered in every region. Availability of the Service is governed by our Terms of Service (Cursor · Terms of Service) and Acceptable Use Policy (Cursor · Acceptable Use Policy), and we monitor and enforce those on an ongoing basis. What you’re seeing may reflect the current availability for your account and location.

For questions about your account or subscription, please email [email protected].

@kevinn this is not a region or subscription question.

I already have Grok Bot access and I am signed in. The Agent Computer is stuck in partial state after a failed Reset. Ticket T-F58206 is already open. Sam (AI) asked for Privacy Mode plus one Reset. Reset failed again. Sam then said a teammate would recreate the computer. There has been no human follow-up since 7 Sep.

Please do not close this as a geo or ToS issue. Please ping Colin or deanrie for a backend recreate of the existing computer. I will not run Reset again.

@mohitjain bump. Ticket T-F58206 still needs a backend recreate of the existing Agent Computer.

This is not a region or subscription issue. I already had Grok Bot access. The computer has been stuck in partial state since a failed Reset. Sam (AI) asked for Privacy Mode plus one Reset on 7 Sep; Privacy Mode is not in Settings (not Legacy); Reset failed again; I did not click Retry Reset. Sam then said a teammate would follow up. There has been no human email since 7 Sep.

Please do not close this as geo or ToS. Please recreate or reattach the existing computer on the backend. I will not run Reset again.

Cursor user ID: auth0 user_01KYCXH2GZ53VR82JNFB6CW360

Grok Bot slot: 1d21a825ed1884ec3ea86ea73272646495a166a4a13f1a4f388bcd6a4c137f19

App is now 0.47.0 on Windows 10. I accidentally signed out on 11 Sep and Cursor sign-in did not finish; I will complete login locally. The cloud computer itself still needs the backend recreate.