Fix · App

Bot not responding or “Bot failed to respond”

The Bot is silent, stuck, or says “Bot failed to respond”. Least destructive step first; Reset is the very last resort.

~5 min·Checked against the official docs 2026-10-31

1. ✓Mark step 1 as done

   1. Check whether Grok Bot is down

   Look at our status page or the official one (status.cursor.com, Grok Bot row). If there's an incident, wait for it to be resolved, then send your message again. Don't Reset the computer or reinstall the app.

   Why it happens: Neither fixes a service problem, and a Reset can lose very recent changes if the computer can't be reached to save them.
2. ✓Mark step 2 as done

   2. Wait a moment, then send the message again

   If there's no incident and the Bot says Bot failed to respond or Model provider is overloaded, wait a moment and send the same message again. Many failures are short.

3. ✓Mark step 3 as done

   3. Look for something waiting on you

   A Bot that looks stuck is often waiting. Open the computer view (the preview in the conversation's right-hand panel) and look for a question, an approval card, a login, a CAPTCHA or a secret request. Cards raised by background work expire after 30 minutes, so an old one may need you to ask the Bot to try again.

   Why it happens: A computer-use task already running on that Bot's screen may need to finish or be redirected before another one can start.
4. ✓Mark step 4 as done

   4. Check the computer is connected

   A Bot can't finish a turn while the computer says Reconnecting or Couldn't Reach Grok Bot's Computer. Wait, then choose Retry. Your Bots, files and logins are safe while it reconnects, and chats are stored separately from the computer.

5. ✓Mark step 5 as done

   5. Fully quit and reopen Grok Bot

   Quit completely: on a Mac, choose Quit from the menu bar, not just close the window. Reopen and try again. Cloud work keeps running while the app is closed.

6. ✓Mark step 6 as done

   6. Update or recover the computer, in that order

   If it still can't reconnect: open Settings → Computer and choose Update Bot's Computer if an update is offered. Then Recover computer if it still won't connect. Use Reset only after those steps. Recover and Reset both remove installed apps and packages and can lose very recent changes; project folders like node_modules aren't saved.

7. ✓Mark step 7 as done

   7. Rule out your usage limit

   If the Bot stopped and says you hit your usage limit, it isn't broken: your weekly usage is used up. Follow the usage-limit fix.

8. ✓Mark step 8 as done

   8. Redirect or stop the work

   If the Bot is busy on the wrong thing, send a short redirect. A direct message from you takes priority over background work. Send “Stop now” to end it immediately; this doesn't undo actions already completed.