First, work out which of three things is wrong

A silent Bot has one of three causes: the Bot is waiting on you, the shared computer is unhealthy, or the service is degraded. The symptoms look identical from the chat, so open the computer view before touching anything. The official docs say to check the sidebar status, watch the computer, and look for a prompt, approval, login page, or CAPTCHA the Bot is stuck behind.

If the Bot is waiting, answer it or send a redirect. If the computer view will not load or shows setting up or unreachable, follow the recovery order below. If several Bots died at once and the forum shows a fresh degradation thread, stop and wait.

Documentation: Official troubleshooting ↗ Grok Bot overview ↗

The official recovery order

These steps are from the official troubleshooting page for a computer that cannot be reached. Do them in order and stop as soon as Bots reply again.

Documentation: Official troubleshooting ↗

  1. Choose Retry from the error state.
  2. Quit and restart the Grok Bot app, then check for an app update under Settings, Beta.
  3. Select Recover computer (or Recover Agent Computer) and wait for it to complete.
  4. Under Settings, Beta, choose Update Agent Computer and wait for the replacement to come up.
  5. Only then use Reset Agent Computer, knowing unsynced files on the computer may be lost.

What the August incident looked like

Between August 20 and 23 the shared computer entered a stuck state for many accounts; Bots returned 'failed to respond' and the main forum thread collected 149 replies and more than a thousand views. Later threads describe every Bot frozen after a reset, a reset stalled at 50 percent, and Bots that sent messages but never replied on Windows. On September 17 Cursor posted that it was investigating a degradation affecting Cloud Agents and Grok Bot.

These are attributed community reports. The pattern they share is that user-side recovery did nothing during the incident window, and resets made things worse by discarding state. If your symptom matches a live thread, the useful action is to add your app version and timestamp to it and wait.

Documentation: Forum: some Bots became unresponsive (149 replies) ↗ Forum: all Bots unresponsive after reset ↗ Forum: service degradation notice ↗ CellCog problems tracker ↗

A Bot that goes quiet after a long tool wait

One report describes a Bot becoming unresponsive after a long-running tool call, with a recreated Bot showing 'Failed to send' until the app was restarted. If one Bot is silent while others work, the computer is probably fine. Send a 'Stop now' message, restart the app, and give the Bot a smaller bounded task before retrying the long one.

Documentation: Official troubleshooting ↗

  • You opened the computer view and looked for a login, CAPTCHA, or approval before resetting.
  • You checked the forum tag for a degradation notice with a matching timestamp.
  • You followed Retry, restart, Recover, Update before Reset.
  • You noted the app version and time in case you need to report it.

Quick answers

Why did all my Bots stop responding at the same time?

Every Bot in an account shares one cloud computer. When that computer is stuck, unreachable, or mid-update, all Bots fail together. That is why 'Bot failed to respond' tends to hit the whole account, and why the fix is on the computer, not the Bot.

Should I reset the Agent Computer?

Only as the last step. The official order is Retry, restart the app, Recover computer, Update Agent Computer, and then Reset. Reset can lose unsynced work, and forum users report resets that stall at 50 percent during service incidents.

How do I know if it is an outage and not me?

Check the Cursor forum's grok-bot tag for a pinned degradation notice and compare timestamps. During the August 20 to 23 incident, a thread reached 149 replies while nothing on the user side helped. If many people report the same symptom in the same hour, wait rather than reset.

Sources & next steps

Capabilities are grounded in the documentation below. The workflow design and acceptance checks are editorial suggestions.

Build your own workflow brief ↗