Greater Transparency on Usage Limits and Quotas

Ideas Feature Requests
1

Feature request for product/service

Billing

Describe the request

I would like you to be more transparent about the usage limits in Cursor. We have two metrics that go from 0% to 100% - but we don’t know the reference for the baseline calculation of this percentage: 100% of how much, of what?

We also don’t know what happens after “Cursor Models” and “Other Models” both reach 100% usage. The response gets slower, but what happens after that, when this final limit of mine actually runs out? I could be doing something important and then this “almost infinite third limit” runs out, but I can’t see this “percentage” anywhere. I think it’s time we were able to see that. We are Cursor users and we want to see the service improve and be proud to continue using it amidst so many competitors. But we want you to be our friends too and look out for our interests. It’s a two-way street.

Screenshot / Screen Recording

cursor100p.png
cursor100p.png421×204 4.93 KB

Operating System (if it applies)

Windows 10/11

4

beginner here but +1 on this tbh. I run a few agents + routines every day and the 0–100% bars are the only thing I see, so I kinda end up guessing when to slow down. even a rough “100% ≈ X requests / Y tokens” note or a small history graph would help a lot imo. and yeah, a heads-up before the last limit actually runs out would save ppl mid-task. just knowing the baseline would make planning way easier, I think so.