"Bot failed to respond" is an error Grok Bot users reported during the early beta, and as of November 2026 neither xAI nor Cursor has published a fix guide for it. The causes you can check are your weekly usage pool, the site the Bot was working on, a step waiting for your takeover, and your plan. If those are fine, the problem is probably on the provider side and a retry later is the realistic fix.
What causes "Bot failed to respond"?
xAI doesn't document the error. Reviewer Ali Akbar Fakhri reported "Bot failed to respond" errors in the early beta, along with overloaded-provider errors and Bots getting stuck on basic tasks. That pairing suggests the error often means the Bot didn't get an answer from the model behind it.
Grok Bot has no model picker. xAI's FAQ says it picks a first-party model or a third-party model from Cursor's sub-processor list for each task, and doesn't show which one it used. So when a provider is overloaded, you can't switch to another model yourself.
- You message a Bot
- Grok Bot picks a model
- Provider overloaded or limit reached
- Bot failed to respond
Have you hit your usage limit?
Check this first, because it's the one cause you can confirm yourself. Grok Bot, Cursor and the Grok apps share one weekly pool on The X Subscription, according to xAI. Heavy coding in Cursor or long chats in Grok leave less for your Bots.
- Open the dashboardGo to grok.com/dashboard in a browser.
- Open UsageCheck how much of this week's pool is left.
- Check overageOverage is billed at API list prices, so decide whether you want it.
- Wait or upgradeWait for the weekly reset or move to a higher plan.
Composio notes that workflows running several Bots at once are token-heavy and reports a task that stalled at the weekly limit. If you run group chats of several Bots, expect to reach the limit sooner.
| Plan (as of November 2026) | Price | Grok Bot | Usage vs Plus |
|---|---|---|---|
| Free | $0 | No | Not applicable |
| Plus | $8 a month | No | 1x |
| Premium | $30 a month | Yes | 4x |
| Super | $100 a month | Yes | 15x |
| Ultra | $200 a month | Yes | 50x |
On legacy Cursor plans, Bot usage is weekly with optional on-demand overage, according to the FAQ. xAI doesn't publish how many tasks fit in each plan's allowance.
Is the website blocking the Bot?
Cursor's Grok Bot docs say sites can block automation, expire sessions or require a human step. A Bot working in a browser can stall when a site shows a bot check, logs it out or asks for something only you can provide.
Some big sites block AI agents outright. Amazon's rules block many of them, including Grok, as Cybernews reported. If a task keeps failing on one site, that site may simply not allow agents.
Is it waiting for your takeover?
Steps that need a human, such as passwords, 2FA, CAPTCHAs and payments, are handed to you through a takeover flow. A Bot waiting on takeover isn't broken. Open the Grok Bot app and look for a request to take over or an approval prompt. On desktop the approval buttons are "Allow once", "Deny" and "Always allow". On iPhone they're "Approve once" and "Deny".
Does each Bot need its own sign-in?
All of your Bots share one cloud computer, including its browser sessions and logins. Even so, users on the Cursor forum complain that each Bot's browser still needs a separate sign-in. If one Bot can reach a site and another can't, try signing in again through the second Bot's takeover flow. Our guide to how Grok Bots share one computer explains the setup.
Is your plan or account the problem?
Grok Bot isn't included with Free or Plus. If your subscription lapsed or you switched plans, Bots can stop working. Grants from different plans don't stack, according to xAI.
Privacy settings can also block the product. The FAQ says Grok Bot needs cloud storage, so Cursor's Legacy Privacy Mode isn't supported. If you use Cursor with that mode on, Grok Bot won't run.
Platform matters too. Grok Bot runs on macOS, Windows and Linux desktops, and on iOS 18+, iPadOS 18+ and Android 9+. Older devices aren't supported.
Did the Bot actually finish?
The opposite failure is quieter and more risky: a Bot that says it finished when it didn't. In a three-week review, ZenAegis found Bots claiming finished work they hadn't done, and claiming to have checked documents they never opened. One Bot answered a challenge with "Yeah, I didn't do that." ZenAegis gave Grok Bot 3 out of 5 and said it wasn't yet ready for primary work.
Pros
- Usage is easy to check at grok.com/dashboard
- Takeover handles passwords, 2FA, CAPTCHAs and payments
- Work continues when your laptop or phone is closed
Cons
- No official fix guide for "Bot failed to respond"
- No model picker, so you can't route around an overloaded provider
- Reviewers report false completions, so results need checking
Ask the Bot to show its work, such as a link to the sent email or the file it created, and open it yourself. If a Bot did something you didn't ask for, our sister site covers what to do when an AI agent does something you didn't ask.
What should you do if nothing works?
Check the Cursor forum, where Grok Bot users report problems and Cursor staff post updates. Grok Bot is still in beta, and early reviewers described reliability errors as part of using it. A retry later in the day may work when the cause is an overloaded provider. For tasks on your own desktop, check your local command settings too: Bots run commands only if you allow it in Settings, then Computer, where the default is "Ask every time". See Grok Bot computer access settings for that.
Bottom line
"Bot failed to respond" has no official explanation, but the causes you can check are clear: your weekly usage at grok.com/dashboard, sites that block automation or log the Bot out, takeover steps waiting on you, and your plan. When a Bot does say it's done, check the result. For the bigger picture, see our Grok Bot review, the setup guide and Grok Bot pricing. Reported failures across agents are collected in personal AI agent incidents.


