Not responding

Grok Bot not responding: computer first, then usage

Silent bots, from plans and billing and staff posts. The computer can be healthy while every bot looks dead. Short index: Grok Bot not working. Do not start with Reset.

Three different failures share this search

Grok Bot not responding is what people type for three different screens. Cursor Help’s own order is computer status first, then the prompt, then support. Usage is the field case that the banner often hides. Do them in this order.

1. The app is open, the computer view loads, and bots do not answer. Stay on this page. This is the usage case.
2. The app is stuck on Connecting, Setting up, Cleaning up, or a percent bar. That is the stuck page. Usage is not the first test.
3. The words on screen are Can't reach your computer, Reconnecting, or a blank desktop. That is the can't-reach page, unless the computer view still works and only the replies are missing.

A white or black window with no roster is the white-screen page. Reinstalling from x.ai/bot does not answer a silent bot, and it does not clear a full meter.

Confirm the computer is actually there

Open the computer view. If it loads a desktop, the hosted machine is up. Staff and the billing notes treat this split as the whole diagnosis: silent bots with the computer still visible are weekly usage, not a dead box. Messages may still send. You see your bubble. No reply runs. iOS and the desktop app often skip the sentence usage limit reached, so the absence of a banner proves nothing. Dual banners, when they do appear, are usually blocked retries, not two bills.

Check Settings, then Usage, in the app, or the Cursor dashboard. Read the meter and the weekly reset time. Do this before Recover, Update, or Reset. Those three buttons change the computer. They do not add usage. Pro's Other Models amount is not the Grok Bot weekly pool. Cloud Agents that a bot launches bill Cursor plan usage separately. If you only look at the IDE usage chart, you can miss the bot pool and reset a healthy computer.

If the meter is full

You have two honest options. Neither one is Reset.

• Wait for the weekly reset shown on the usage screen. Routines that came due during the block were skipped. They do not queue up and run later as a surprise batch of sends. Messages you already sent during the block reply in a batch once usage is available again.
• Resume now by enabling On-Demand on the same Cursor account and setting a spend limit you accept. Bots should reply within a couple of minutes. The app may not warn you in the chat before paid spillover starts. If you do not want paid spillover, set the On-Demand cap to $0. That stops the paid tier. It does not stop promo or referral credits from being drained first. Charge order is weekly pool, then credits, then paid On-Demand.

Shrink routine windows while you are here. Delete idle specialist bots that poke each other. Every bot-to-bot message counts against the weekly pool, including review threads you asked them to stop. Telling a bot stay quiet in chat does not freeze the meter if a routine or another bot is still talking. The cost page is the longer version of this trap. This page is only the decision when the symptom is silence.

If the meter is not full

Then it is not the weekly pool, and you still should not Reset first. Work through the less destructive list. Fully quit the app and reopen. On macOS that is menu-bar Quit. On Windows, quit the tray. If one connector action hangs and the rest of the roster is fine, that is a plugin failure, not a dead computer. Zoom error 4700, Notion redirect, Gmail, Canva on iOS, X, and a broken GitHub header each have their own note on the troubleshooting index. Do not paste a bearer token into chat to get around them.

If every bot says Bot failed to respond or Couldn't send your message for hours, on the phone and on the desktop, while the computer screen is still visible, stop. Ask support before Reset. Reset rebuilds from the last snapshot and can drop the newest unsynced edits. Email hi@cursor.com with the Grok Bot version, the OS, the exact error line, the bot or routine name, the time and timezone, the request or conversation id, and what you already tried. Do not attach passwords, codes, or keys.

Trial ended is silence of a different kind

An exhausted trial does not delete data. Bots stop answering, and the computer view can still export. Do not Reset to save a trial. Expired access can also wear the Can't reach your computer label even though the cause is the plan. If Retry and Recover fail and the account no longer includes Grok Bot, pick a plan that includes it or link SuperGrok on the same email, then fully quit and reopen. Pricing keeps the dated plan notes. This page will not invent a price.

FAQ

Related

• Grok Bot guide — If you are not installed yet, start with the download, not Reset.
• Not working index — Every symptom card, including plugins and Linux.
• Usage and On-Demand — Pool, credits, and the week-burning habits.
• Can't reach — Use this when the computer view itself will not open.
• Recover versus Reset — What each button keeps, after you know it is not usage.

Sources

• Plans and billing
• No warning before On-Demand
• Bot-to-bot reviews burn the week
• Trial still exportable
• Official troubleshooting