METAGROK
GROK BOT / control-grok-bot-on-demand-after-weekly

Grok Bot

Control Grok Bot On-Demand after weekly usage hits 100%

control-grok-bot-on-demand-after-weekly

Control Grok Bot On-Demand after weekly usage hits 100%

Grok Bot subscriptions include weekly usage. Eligible accounts can add on-demand usage billed from model and token cost. Cursor staff confirmed that when the Bot weekly allowance is gone, further Bot work can spend referral or promo credits, then paid On-Demand if On-Demand is enabled — and today there is no in-product warning or confirmation before that spill.

This how-to covers the documented spend order and the controls that exist now. It does not invent a missing confirmation UI.

Check Bot weekly and On-Demand

  1. Open Grok Bot and go to Usage & Billing when that page is available.
  2. Read the Grok Bot weekly percentage and reset time.
  3. Open the Cursor dashboard at cursor.com → Usage / Billing for the same account.
  4. Confirm whether On-Demand (usage-based) is enabled.
  5. Note any spend limit in dollars and any referral or promo credit balance.

Bot troubleshooting also says: if usage is exhausted or an on-demand spending limit is reached, review usage and billing from the account access page or Usage & Billing. Paid Bot work waits until weekly usage resets or on-demand is available.

Documented spend order (staff, Sep 1, 2026)

On the On-Demand spill thread, Cursor staff (deanrie) confirmed this order:

  1. Grok Bot weekly allowance
  2. Referral or usage credits
  3. Paid On-Demand (only if On-Demand is enabled)

Staff also said the Bot weekly pool is separate only until it runs out. After it is depleted, usage spills into the main Cursor balance in the order above. Staff called the missing warning and missing per-product On-Demand breakdown a feature request; current behavior is intentional.

Controls that exist today

  1. Watch the Grok Bot weekly meter. Staff’s practical advice: pause the Bot when the bar is close to 100% if you want to avoid spillover.
  2. Set an On-Demand or usage-based spend limit in dollars at Dashboard → Usage / Billing.
  3. Set the limit to $0 if you want to stop paid On-Demand charges.
  4. Know the limit: staff corrected themselves — a $0 On-Demand limit stops paid On-Demand, and it does not stop referral or promo credits from being spent before On-Demand.
  5. Disable or pause heavy routines and long chats that keep burning tokens while the weekly bar climbs. See Fix a Grok Bot routine that did not run for routine controls, and Reset a Grok Bot chat without cloning the Bot when a fat transcript is the burn source.
  6. Email hi@cursor.com with screenshots if you need Cursor to verify which credit line a charge hit.

There is no timeline yet from staff for a warning prompt or a per-product On-Demand breakdown.

Pitfalls