Grok Bot completely unresponsive after phone change + WhatsApp reconnect, multiple Recover/Reset failed

Hi team,

My Grok Bot has been completely unresponsive since this morning (around 2026-11-08 ~08:00 HKT).

Symptoms:

  • Messages are accepted by the bot, but there is no reply at all (empty response).

  • This affects both my main bot and newly created bots.

  • The issue started right after I changed to a new phone and asked the bot to reconnect WhatsApp (WhatsApp was logged out after the phone change).

What I already tried:

  • Fully quit and reopened the app multiple times

  • Settings → Computer → Recover computer (multiple times)

  • Reset computer (multiple times)

  • Waiting for a long time

  • Sent several in-app Feedback reports

None of the above fixed it. The bot still accepts prompts but never returns any text.

Official status page shows no active incidents, so this seems account/computer-specific.

Could you please help recover my Bot computer on the server side?

I need it urgently for work.

Thank you!

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Editor, Tab & Chat (autocomplete, Composer, in-editor agent)
  • Terminal & commands
  • Models, pricing & API keys (availability, Auto/Max, BYOK/Bedrock)
  • MCP & tools
  • Cloud Agents & Automations (cursor.com/agents, scheduled/event)
  • BugBot & Code Review
  • Cursor CLI
  • Cursor Mobile
  • Remote (SSH / Dev Containers / WSL)
  • Account, billing & login
  • Something else…

Describe the Bug
A clear and concise description of what the bug is.


Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

  1. …
  2. …
  3. …

Expected Behavior
What is meant to happen here that isn’t working correctly?


Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)


Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)


For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…


Additional Information
Add any other context about the problem here.


Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

Hi @datashare_withhody, this was a server-side issue on our end, not your Bot’s computer or your new phone, so there’s nothing to recover on your account.

From about 07:47 to 09:50 HKT on Nov 8, replies failed for a group of users in your region before they reached the model. That’s why both your main Bot and the new ones went silent, and why Recover and Reset didn’t change anything. It was fixed shortly after, and your Bot has been replying normally since about 10:00 HKT.

Your WhatsApp reconnect request was sent during that window, so it may not have gone through. If WhatsApp still shows as logged out, ask your Bot to reconnect it again now.