METAGROK
GROK BOT / understand-grok-bot-usage-and-failed-to-respond

Understand Grok Bot usage and “Bot failed to respond”

understand-grok-bot-usage-and-failed-to-respond

Use this when you need to read Grok Bot usage or a Bot answers “Bot failed to respond.” Grok Bot is a separate product from grok.com and the Grok mobile apps. Its usage is a separate pool from the SuperGrok weekly bar for Chat, Imagine, Voice, and Build.

Who gets Grok Bot

Sources differ on plan wording. The get-started page lists "every paid individual Cursor plan or the Cursor Teams plan, or an individual SuperGrok, SuperGrok Plus, or SuperGrok Heavy subscription linked to your Cursor account" (docs.x.ai/grok-bot/get-started, checked 2026-09-25). The FAQ says Grok Bot is "included with every paid individual Cursor plan and with the Cursor Teams plan" and that "you can link an individual SuperGrok, SuperGrok Plus, or SuperGrok Heavy subscription" (docs.x.ai/grok-bot/faq, checked 2026-09-25). The SuperGrok card on x.ai/pricing lists "Grok Bot access" (checked 2026-09-25). The docs say "linked," while the pricing card and xAI's news say "included." Cursor's Plans and billing page also lists X Premium+ (cursor.com/help/grok-bot/plans, checked 2026-09-25).

Subscriptions include weekly usage. Eligible users can add on-demand usage billed from model and token cost. Dual Cursor + SuperGrok uses whichever has more usage.

Read Bot usage

  1. Open Usage & Billing in Grok Bot when that page is available.
  2. The account menu may show Weekly usage.
  3. If neither is there, open the Cursor account page, or ask an org admin.

Teams spend is on cursor.com/dashboard/usage. Invoices combine Cursor and Grok Bot. Docs say there is no Grok Bot-specific spend cap yet.

If the Bot is stuck because usage is exhausted or an on-demand spending limit is reached, review Usage & Billing. Paid Bot work waits until weekly usage resets or on-demand is available.

“Overbooked” and “Bot failed to respond”

The product can show Bot failed to respond with “Something went wrong while generating the reply. Try again.” Cursor staff named a related service-side error string overbooked. It is load rejection. There is no overbooked setting.

Staff (Aug 2026): if you see overbooked then failed-to-respond, and Usage & Billing is not at zero, try later. Requests were rejected in waves under heavy model load.

Staff also saw a stuck cloud computer that did not pick up messages. Reset and Update did not recover it. They restored the box server-side (Colin, Sep 1: boxes recovered). If a reachability error appears, follow Fix Grok Bot “Can’t reach your computer”. If those steps fail and usage remains, report the issue with version, OS, and time.

Related

Pitfalls

  • SuperGrok Settings → Usage on grok.com is the Chat/Imagine/Voice/Build pool. Bot weekly and on-demand live under Usage & Billing.
  • Overbooked load is a service-side rejection. Staff restored some stuck computers themselves after Reset and Update failed.
  • Point at live Bot access and pricing pages for current numbers. This how-to does not freeze a token price.