Grok Bot Agent Computer partial state after Reset — Windows and phone both silent

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

Agent Computer is in a partial state. Windows Grok Bot app and the phone Grok Bot app are both silent. Bots do not reply.

Weekly Grok Bot usage is 31% used, reset in about 4 days. This is not a usage-limit issue.

What I already tried:

  • Fully quit from tray and ended leftover Grok Bot processes in Task Manager
  • Retry — no connection attempt
  • Recover Grok Bot’s Computer — stuck at 75%, then stopped without reconnecting
  • Reset Grok Bot’s Computer — result: partial state

Please rebuild the Agent Computer on the backend. Bots, files, and logins should be kept.

Operating System
Windows (desktop app) and phone Grok Bot app

Version Information
Grok Bot Windows: 0.53.0
Phone: Android Samsung S24

Timezone
IST, 16 Sep 2026 ~17:30

Account email
[email protected]

Steps to Reproduce

  1. Open Grok Bot on Windows. Bots do not reply. Phone Grok Bot app on the same account also does not reply.
  2. Check Settings → Usage. Weekly usage is 31% used, reset in about 4 days.
  3. Fully quit Grok Bot from the system tray. End leftover Grok Bot processes in Task Manager. Reopen the app.
  4. App shows Retry and Recover Grok Bot’s Computer.
  5. Click Recover. Progress reaches 75%, then stops without reconnecting.
  6. Quit again, reopen. Click Retry. No connection attempt. Same Retry / Recover screen returns.
  7. Quit again, reopen. Settings → Updates → Reset Grok Bot’s Computer.
  8. Reset finishes with “partial state.”
  9. Windows and phone apps still cannot use the Agent Computer.

Expected Behavior

Expected: Recover or Reset reconnects the Agent Computer and bots reply to a simple “hello.”

Actual: Computer left in partial state. Desktop and phone both silent.

Operating System

Windows 10/11

Version Information

Version Information
Grok Bot Windows: 0.53.0
Phone: Android Samsung S24
Grok App Version:1. 10.0 (201)

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the detailed report. Two different things overlapped here, so I’ll break them down.

  1. Bots weren’t replying (roughly 15:00 to 17:00 IST). This was on our side, not your computer. A message sent around 15:01 got stuck in processing, and everything you sent after that (from both Windows and your phone) queued behind it. Around 17:00 the queue cleared on its own, and the backlog was processed around 17:05-17:07, so you may have seen several replies arrive at once. The root cause on our side is already fixed.

  2. Recover stuck at 75% and partial state on Windows. Your Agent Computer is actually fine. Every Recover and Reset completed successfully for us in under a minute, and your bots, files, and logins are preserved. The issue is that your PC can’t resolve the machine’s network address via hostname lookup on cursorvm.com, even though cursor.com opens normally. That points to DNS on your internet connection, and that’s why the app shows partial state even though the rebuild finished. Please don’t press Reset or Recover again. Each click rebuilds the computer again without helping.

Try this on Windows:

  1. Switch DNS to public DNS: Settings > Network & Internet > Wi-Fi (or Ethernet) > Hardware properties > DNS server assignment > Edit > Manual > enable IPv4 > Preferred DNS 1.1.1.1, Alternate DNS 8.8.8.8 > Save.
  2. Open PowerShell (Start > type PowerShell) and run ipconfig /flushdns.
  3. Right-click the Grok Bot tray icon > Quit, then reopen Grok Bot and wait about a minute.
  4. Send “hello” to one of the bots.

For your phone: if it’s on Jio mobile data or the same Wi-Fi, it’ll likely hit the same lookup issue. On Samsung: Settings > Connections > More connection settings > Private DNS > Private DNS provider hostname > enter one.one.one.one > Save, then reopen Grok Bot. Alternatively, test once on a different Wi-Fi or via hotspot.

Let me know if the bot replies after step 4. If it still won’t connect after changing DNS, send your Grok Bot version from Settings and we’ll dig deeper.