Hey, thanks for the detailed report. Two different things overlapped here, so I’ll break them down.
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.
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:
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.
Open PowerShell (Start > type PowerShell) and run ipconfig /flushdns.
Right-click the Grok Bot tray icon > Quit, then reopen Grok Bot and wait about a minute.
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.