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:
- Adding usage warnings during the billing cycle and be more more helpful in flagging if you're using API vs on-demand models
- Usage Guardrails to Stop Burning Through the Monthly Limit in Just a Few Days
There’s no timeline yet for a warning prompt or a per-product breakdown, but if there’s an update, I’ll reply here.