There is a critical billing / quota enforcement bug that can break usage metering and allow effectively unlimited overdraft / unpaid AI usage.
On Dashboard → Spending, set Monthly Limit to 2147483646.99 through the set-hard-limit API. Billing/usage then fails: UI shows “Included in Pro” and “Failed to load usage data”, and usage accounting stops working correctly.
Separately, Team billing/refund bugs can keep MCP/AI sessions alive after refund, or incorrectly refund an existing Pro user after Team pull-in. Combined, this can allow continued MCP requests without valid paid entitlement — unlimited overdraft risk.
Please treat this as high severity for billing integrity.
Steps to Reproduce
Bug A
Open Dashboard → Spending
Set Monthly Limit / hard limit via set-hard-limit
Enter 2147483646.99 and save
Observe “Included in Pro”, “Failed to load usage data”, broken metering
Bug B
Use a paid Pro / Pro+ account
Start Cursor client AI chat with MCP
Add account to Team and trigger Team refund
MCP/AI session may stay alive and keep requesting (more common on TW/JP nodes)
Bug C
Start with an active Pro user
Pull that Pro user into a Team
Team refund incorrectly refunds the user’s Pro
MCP sessions can continue without proper entitlement
Expected Behavior
Hard-limit input must not break billing. Refund / entitlement loss must immediately revoke AI/MCP access and kill active sessions. Team must not auto-refund an existing Pro user incorrectly.
Hey, thanks for the detailed report. I’ll go through it point by point.
Main thing: there’s no unlimited AI usage or billing bypass here. The monthly or hard limit only affects on-demand overage, and overage is only available on a paid plan with a payment method attached. Included and free quota is metered server-side regardless of that limit value, so setting a huge number can’t unlock unpaid usage.
What’s actually happening with Bug A: an extreme limit value close to 2 147 483 647 breaks the usage summary card UI, which is why you see Failed to load usage data. This is a known display issue, and metering still works correctly. As a workaround, go to Dashboard > Spending and set a normal USD limit or No Limit.
For Bug B and Bug C refund keeps the MCP session alive or Team pull-in incorrectly refunds Pro: we couldn’t reproduce it or find any confirmation of that behavior. If you’ve seen it on specific requests, please send the Request ID and approximate timestamps for those sessions so we can check them directly.
You can get the Request ID like this: chat menu top right > Copy Request ID.
Thank you so much for reporting such bug(s), really, really, really, “thank you”
Bug A:
After testing, setting 2147483646.99 will casue 500 internal error and the limit never changes.
0 or < 0 value aren’t allowed to be changed.
Bug B & C:
Once an account added to team and got kicked out, all user’s following session will be kicked out (401), the running chat will be stopped and returned error telling user to login again, so no.
And as I know, after recent update, the tool calling bug is already gone - no more keep alive session can be run since every request now will run a pre-check to verify the user’s state.
@deanrie Agreed when on-demand is enabled. If it is disabled, the overage can’t/won’t be billed afterwards right? Because as I currently don’t know where I am on the spending, I also don’t want to get billed afterwards if it would seem that I went over my allowed limit. I hope that makes sense, and the spending gets fixed quickly.
Some accounts can indeed do this. It’s already circulating on various hack forums, which is likely why Cursor’s performance dropped yesterday. Please verify this on your side.
@Floriant_Sturm re your question: if on-demand or usage-based pricing is turned off, you won’t be charged for overage after the fact. Once the included quota is used up, requests just stop instead of getting billed, so there won’t be any silent charges over the limit.
On cost visibility, this is the same issue from that thread. The usage-summary card can show “Failed to load usage data” if your account has an extreme limit value set. Metering still works correctly, only the display breaks. To fix the card, go to Dashboard > Spending and set a normal USD limit or choose No Limit.
@in_ja about “hack forums” and the performance drop, there’s no link here. An extreme hard limit value only breaks the usage-summary card in the dashboard. It doesn’t unlock unpaid usage. Included and free quota are metered server-side no matter what limit value you set. We checked this, there isn’t an unlimited-usage scenario here.
If you have specific data that suggests otherwise, send it over and we can check directly. We need a Request ID, rough timestamps, and the account where you saw it. You can get the Request ID like this: chat menu in the top right > Copy Request ID. Without details, we can’t confirm the behavior you described.
I have a Pro+ subscription.
I exhausted my usage allowance and tried using the “Auto” setting; the agent worked, and the billing section indicated “Free.”
I assumed it was working as intended, but I was charged today, and I noticed that the “On-demand” setting—which I had previously turned off—was enabled.
I just ran a test by setting a fixed limit of $50 and using “Auto,” and it worked again.
