Hi everyone,
I’m using Cursor with a Pro plan and just got this message:
“You’ve saved $137 on API model usage this month with Pro Student. Switch to Auto for unlimited requests or set a Spend Limit to continue with Sonnet.”
I’m confused about a few things:
I thought the Pro plan gave unlimited usage – why am I seeing this warning now?
Does this mean I can no longer use Claude (Sonnet) unless I switch to Auto or set a spending limit?
Any help clarifying this would be really appreciated. Thanks!
exactly, got the same error!
Now I don’t know if this is the same rate limit as before(which will get off after a few hours) or is this a monthly thing?
Honestly, I love cursor but these things are kind of putting me off from buying cursor subscription.
Please clarify cursor team? <3
Hi, we give unlimited agent usage when using the auto model router to route to frontier models with capacity.
When selecting the model yourself, it’s subject to local rate limits that reset every few hours (currently five hours per session, similar to session durations as OpenAI and Anthropic), and burst limits that refill more slowly that allow for bursty usage above a local session limit.
Since you’re hitting a rate limit here, you’ve gone through both the burst limit and local session limit (you’re usage so far this month would have cost $137 if using the providers API directly, so the rate limits here are very generous. We’ll work to provide more clarity in app and in the dashboard on when the rate limits reset)
Cursors new plan is not counting requests. That was the old plan and is clearly wrong in the extension. As the extension says its ‘(estimated)’ and there fore not correct.
Note that usage is by resources usage:
heavier models use more resources than regular or lighter models. switching to lighter models or auto allows more usage.
more context in chat to process means also more resources are used. reducing context size also allows more usage.
Be that as it may, I am still confused. I was on a new chat in my project and hadn’t opened it in 3 days. So there had been no big code changes or usage of Cursor. I send 4 messages on Sonnet 4 and then get the message to say I am limited. I mean, something can’t be right there.
@common47 Sure, if you file a separate full Bug Report then Cursor Team can look into your issue and usage. Feel free to tag me with @ there so I dont miss your post.
Using expensive models uses up your requests faster. If you used OPUS it would make sense you end up hitting the limit after a few requests. Don’t use max thinking, it ends up being quite costly for the request. Unless you have usage-based pricing on, you will hit your limit pretty fast. This message disappeared after a few hours, so we can still use the same model.
This is the solution that Cursor employees found for this problem.
