Fix finder
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
Question 2
Open status.cursor.com and find the Grok Bot row. Is an incident open?
Question 3
Send “hello” to a different Bot, or in a new chat. What happens?
The six fixes
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.
- Watch the status page until the incident is marked Resolved.
- Quit Grok Bot fully and reopen it.
- 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.
Your weekly usage has run out
The week's included usage is used up. Your Bots start again when the week resets.
- To wait, read the message: it says how long until the reset.
- To keep going now, turn on on-demand usage or move to a bigger plan. What to do when usage runs out has both.
The app can't reach your Bots' computer
Your Bots, files and logins are safe while the app reconnects.
- Wait a few minutes, then choose Retry.
- Still stuck? Follow the recovery order in Can't reach your computer.
Don't Reset while the app says Reconnecting.
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.
- Send the message again.
- Quit Grok Bot fully and reopen it.
- 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.
- 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: 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.
- Look for a card that's waiting for you, and answer it.
- Click a different Bot in the sidebar, then click back. That reloads the chat.
- Send “Stop now”, then ask again.
- 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.
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.
- Quit Grok Bot fully and reopen it.
- Check your weekly usage.
- Install any update that's waiting.
- Reset the computer one time. A reset removes the apps and packages installed on it.
- Still failing? Write to support.