Grok Bot not responding? Fix "Bot failed to respond"

Bot failed to respond means the reply to your message failed, and the banner doesn't say why. Check the Grok Bot row on status.cursor.com first, because during an incident the only fix is to wait. With no incident open, send your message again.

#What the message looks like

The message is a red banner above the message box. Its title is Bot failed to respond, and the line under it reads "Something went wrong while generating the reply. Try again."

A Bot can also go quiet with no banner: you send a message and no reply comes. The finder in the next section handles both.

#Find the fix for your case

The same banner has several causes, and each has its own fix. Answer up to three questions about what you see, and the finder gives you the cause and the fixes to try, in order.

Not responding: which case is yours?

Answer up to three questions. You get the likely cause and the fixes to try, in order.

Start at question 1. Each answer links to the next question or to your fix.

Question 1

What do you see?

• A red banner: Bot failed to respondOr Failed to send under your messageGo to question 2
• No reply and no messageThe Bot has gone quietGo to question 2
• A message about my usage limitSuch as Weekly usage limit reachedYour fix: weekly usage has run out
• Reconnecting, or a notice that the app can't reach my computerIn the sidebar or over the chatYour fix: the app can't reach the computer

Change

Question 2

Open status.cursor.com and find the Grok Bot row. Is an incident open?

• Yes, an incident is openThe row doesn't read Operational, or an incident names Grok BotYour fix: wait for the incident to clear
• No, the row reads OperationalNo incident is openGo to question 3

Change

Question 3

Send “hello” to a different Bot, or in a new chat. What happens?

• It answersOnly one Bot or one chat is stuckYour fix: one reply failed, or one quiet Bot under it
• It fails or stays quiet tooNone of my Bots answerYour fix: every Bot fails

Change

The six fixes

Service incident

An incident is open: wait for it to clear

The fault is on Cursor's side, and nothing you do in the app makes it clear sooner.

1. Watch the status page until the incident is marked Resolved.
2. Quit Grok Bot fully and reopen it.
3. Send your message again. A message sent during an incident isn't retried for you.

Don't Reset the computer and don't reinstall the app. Neither fixes an incident, and a reset now can lose very recent changes.

Usage

Your weekly usage has run out

The week's included usage is used up. Your Bots start again when the week resets.

1. To wait, read the message: it says how long until the reset.
2. To keep going now, turn on on-demand usage or move to a bigger plan. What to do when usage runs out has both.

Connection

The app can't reach your Bots' computer

Your Bots, files and logins are safe while the app reconnects.

1. Wait a few minutes, then choose Retry.
2. Still stuck? Follow the recovery order in Can't reach your computer.

Don't Reset while the app says Reconnecting.

One request

One reply failed, and your computer is working

All your Bots share one cloud computer. Another Bot answered, so the computer is fine and the trouble is with this request or this chat.

1. Send the message again.
2. Quit Grok Bot fully and reopen it.
3. Start a new chat with the same Bot and send the request there: click New chat, type the Bot's name and click its row.
4. Same failure in the new chat? Send support the request ID.

Don't Reset the computer. It's the part that works.

One quiet Bot

One quiet Bot: check whether it's waiting for you

A Bot stops and waits when it needs an approval, an answer or a sign-in. A chat can also stop showing new messages while the Bot carries on.

1. Look for a card that's waiting for you, and answer it.
2. Click a different Bot in the sidebar, then click back. That reloads the chat.
3. Send “Stop now”, then ask again.
4. Quit Grok Bot fully and reopen it.

Don't use Update or Reset here. They restart the computer's connection, which makes the wait longer.

Shared computer

Every Bot fails: the computer they share is stuck

All your Bots work on one cloud computer. When it gets stuck, every Bot fails the same way, even a new one.

1. Quit Grok Bot fully and reopen it.
2. Check your weekly usage.
3. Install any update that's waiting.
4. Reset the computer one time. A reset removes the apps and packages installed on it.
5. Still failing? Write to support.

Each fix in your list links to its steps in the next two sections.

#Work through the fixes in order

The six fixes are in the order to try them, with the likeliest causes first. Stop as soon as your Bot answers. Only the last one removes anything, and its step says what.

Walkthrough

Fix a Bot that isn't responding

1. Marker 1Marker 2

   1. 1Find the row named Grok Bot. Cursor's other products have rows of their own.
   2. 2Operational means no incident is open. During an incident this word changes, and the page lists the incident with its updates.

   1Check the status page

   Open status.cursor.com in a browser and find the row named Grok Bot. The app doesn't show service status, so an incident appears only on that page.

   • An incident is open. Wait until the page marks it Resolved. Don't Reset the computer or reinstall the app while you wait: neither fixes an incident, and a reset can lose very recent changes. Then send your message again, because a message sent during an incident isn't retried.
   • The row reads Operational. Go on to the next fix.

2. 

   2Send the message again

   With no incident open, wait a moment and send the same message again. On a message marked Failed to send, click Resend.

   Model provider is overloaded takes the same fix: wait a moment, then send again.

3. Marker 1Marker 2

   1. 1Needs approval is the tag on a card the Bot is waiting on. The Bot's row in the sidebar turns orange and starts Waiting for you.
   2. 2Answer with Allow once or Deny, and the Bot carries on.

   3If the Bot is silent, see whether it's waiting for you

   When a Bot goes quiet with no banner, check whether it stopped to ask you something. Scroll to the end of its chat and look for a card: an approval, a question, a sign-in or a request for a secret.

   No card? Click a different Bot in the sidebar, then click back, which reloads a chat that has stopped showing new messages. If the Bot is busy on the wrong thing, send “Stop now”, then ask again.

4. 4Quit Grok Bot fully and reopen it

   Quit the whole app, then open it again. Closing the window leaves the app running.

   • Mac: open the Grok Bot menu in the menu bar and choose Quit Grok Bot, or press Cmd+Q.
   • Windows: right-click the Grok Bot icon in the system tray and choose Quit.
   • Phone: swipe the app away, then open it.

5. Marker 1Marker 2Marker 3

   1. 1The percent is how much of this week's included usage is gone.
   2. 2Resets in counts down to the next week's usage.
   3. 3On-demand is paid usage past the weekly amount, shown as spent against your limit.

   5Check your weekly usage

   Click your picture at the bottom left of the app, then Weekly usage.

   At 100%, with on-demand off or spent, your Bots stop until the reset. Usage running out has what to do then. Below 100%, usage isn't the cause.

6. Marker 1Marker 2

   1. 1Check for Updates looks for a newer app. If it finds one, choose Restart to Update. Versions before 0.63 could show Bot failed to respond when weekly usage ran out.
   2. 2When a computer update is waiting, an Update button shows on this row. Click it, then click it again when it reads Click Again to Confirm.

   6Install any update that's waiting

   Open Settings from the same menu and choose Updates. The page holds two updates: one for the app, and one for your Bots' computer. A computer update keeps your Bots, files and logins, and removes the apps and packages installed on the computer.

   A computer update takes a few minutes. If a window says Update still running, choose Keep waiting.

#Reset the computer only as a last step

If every Bot still fails and no incident is open, the cloud computer your Bots share is stuck. Reset rebuilds it from your last saved data, which costs you the apps and packages installed on it and can cost very recent changes.

The button is in the desktop app, at the bottom of Settings > Updates.

• Kept: your Bots, your chats, and the files and logins that were already saved.
• Removed: apps and packages installed on the computer. You reinstall those afterwards.
• At risk: very recent changes, when the computer can't be reached to save them first.

Click Reset and confirm. The rebuild takes a few minutes, and the computer is ready as soon as the app reconnects. Reset once only: if the app says Reset failed, choose Retry Reset one time and then stop, because another reset can interrupt a restore that's still finishing.

#What only support can fix, and what to send

Some stuck computers can only be rebuilt from Cursor's side. Email hi@cursor.com when one of these is true.

• Every Bot still fails after one reset, and the status page shows no incident.
• Reset failed shows again after Retry Reset.
• One Bot fails on the same request in a new chat, while your other Bots answer.

The request ID lets support find the exact failure. Here is an email with that and everything else support asks for.

MessageAn email to hi@cursor.com

1. Account email: you@example.comthe address you sign in with
2. Version: 0.68.1 on a MacSettings, then Updates, shows it
3. Bot: Meeting Prepthe Bot that failed
4. On screen: Bot failed to respond (screenshot attached)the exact words
5. Request ID: paste it herefrom Copy request ID
6. When: today at 2:40 PM, Pacific timewith your time zone
7. Already tried: resent, quit and reopened, updated, reset oncesaves a round of questions

To get the request ID, right-click the message that failed and choose Copy request ID. If the menu doesn't offer it, that message has no ID you can copy: send the error text and a screenshot instead. Leave passwords, codes and secret values out of the email.

#Messages that look similar

A Bot also goes quiet behind these messages. Each one has its own page.

With your Bots answering again, the next step is knowing the computer they share, so an update or a reset never costs you work.

NextThe shared computer

One cloud computer sits behind all your Bots. See what lives on it, and what survives an update or a reset.

1. 6 October 2026
   First published.