Grok Bot gives no warning before weekly usage spills into paid On-Demand

Ideas Feature Requests
1

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

Grok Bot can transition from its included weekly usage allowance into paid On-Demand usage without presenting a clear warning or confirmation to the user.

I used Grok Bot until the weekly usage meter reached 100%. I did not see a prominent notification, modal, confirmation prompt, or other warning telling me that continuing to use Grok Bot would begin consuming paid On-Demand usage.

I only discovered the transition later by checking the Cursor dashboard.

The dashboard also makes it difficult to determine which product generated On-Demand usage. Grok Bot has its own weekly usage meter, but any additional paid usage appears in the shared On-Demand meter without clearly identifying Grok Bot as the source.

This makes it very easy for a user to believe they are still simply using Grok Bot while unknowingly consuming paid usage.

Steps to Reproduce

  1. Enable On-Demand usage on a Cursor account.
  2. Use Grok Bot until its weekly included usage reaches 100%.
  3. Continue using Grok Bot.
  4. Observe that there is no clear confirmation prompt or prominent warning that further usage will consume paid On-Demand spend.
  5. Open the Cursor dashboard.
  6. Observe that On-Demand usage can increase, while the shared On-Demand meter does not clearly identify Grok Bot as the source.

Expected Behavior

When Grok Bot reaches its included weekly allowance, Cursor should clearly warn the user before any paid usage begins.

For example:

“Your included Grok Bot weekly usage has been exhausted. Continuing will use paid On-Demand usage.”

Ideally, the user should have to explicitly confirm before Grok Bot begins consuming paid usage.

The On-Demand dashboard should also show the source of paid usage, for example:

  • Grok Bot
  • Cursor Agent / IDE
  • Cloud Agent
  • Other Cursor products

This would make it clear which product is consuming the user’s On-Demand budget.

Screenshots / Screen Recordings

on demand.jpg
on demand.jpg1919×1079 193 KB
on demand.jpg
on demand.jpg1919×1079 193 KB
email grok bot.jpg
email grok bot.jpg1826×959 205 KB

Operating System

Windows 10/11

Version Information

Grok Bot 1.3.2 (5446)

For AI issues: which model did you use?

Grok 4.5 High Fast and Grok 4.6 High Fast

Additional Information

I originally tried Grok Bot after receiving an email from Cursor introducing/promoting the feature.

The issue here is specifically the lack of an in-product warning when Grok Bot crosses from included weekly usage into paid On-Demand usage, and the lack of source attribution in the shared On-Demand meter.

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Can confirm that Grok Bot is spilling into other usage pools. Even only when at 30% of the weekly limit. It just chooses whatever pool it feels like it seems. And uses fast mode for whatever reason. Including my stashed referral credits. Directly contradicting the email sent out today to Pro plan users:

Grok Bot is now included with your Cursor Pro plan. Your plan now comes with a dedicated Grok Bot usage pool, separate from your Cursor usage.

6

Hey, thanks for the detailed feedback. Both requests are clear: (1) an explicit warning or confirmation before switching to paid On-Demand and (2) source attribution in the dashboard so you can see which product spent the On-Demand budget. I’ll pass this to the team as a feature request.

On current behavior: this is working as intended right now. After Grok Bot runs out of its included weekly allowance, further usage is billed from the shared On-Demand pool if it’s enabled. The dashboard meter is currently shared and doesn’t break down by product.

To avoid unexpected charges right now, there’s a practical workaround. Set an On-Demand or usage-based spend limit in the dashboard at cursor.com: Dashboard > Usage / Billing. You can set a cap in dollars, and if you want to fully prevent switching to paid usage, set the limit to $0 so spillover to On-Demand won’t happen.

Similar requests are already being discussed in a couple of threads. Feel free to take a look and upvote:

There’s no timeline yet for a warning prompt or a per-product breakdown, but if there’s an update, I’ll reply here.