How is it possible that i just made 2 requests with Sonnet 4 and was then shown the message that I hit the rate limit? It just doesnt make sense. Made the first request at 1:06 pm and the second at 1:15pm, as it’s visible in the image. The third says errored but it was the one where I got the rate limit alert. I am having a hard time wrapping my head around this rate limit.
I have the same thing.
You’ll have used up your burst limit (more than $20 of compute) in a previous session. This still leaves your local rate limit allowance, which refills every few hours.
Looks like from the screenshot you made 4 requests against claude-4-sonnet-thinking, which potentially then used up your local rate limit depending on how many tokens were used for these requests.
ah I see thanks
so burst limit is 20 usd compute ya
this was not mentioned in document
Btw what do you mean last session?
and how we know this is new session or still using last one?
It all comes down to how many magic beans you’re willing to pay the wizards.
same here yesterday
Just wait 
Hey there @ChinaCraig , this is not a Cursor Rate limit on your account, this is our (Cursor’s) rate limit with our provider (Anthropic in this case), which can happen in extremely rare cases of heavy load from usage (or other issues on the model provider’s side)
Hey @fullofcaffeine @aldinokemal
Feel free to check out our updated pricing docs here:
We changed the wording on our Pricing | Cursor - The AI Code Editor page, as it was confusing some folks, who thought “Unlimited Agent” usage meant “Unlimited, un-rate-limited LLM calls to all models”, nothing has changed behind the scenes here in terms of usage.
We guarantee folks will get more than their money’s ($20) worth of API calls as well as all the other features Cursor has to offer. From my experience I’ve seen many folks sharing screenshots being able to use $160 worth of API calls on their pro plan before being asked to upgrade due to exceeding their rate limits.
@IsaacHopkinson You guys are really cherry picking what posts you answer right now huh
Man why are you outright lying to us when we see what is actually happening during usage??? This isn’t me bashing you, I love using cursor. But I know you are lying, you know you are lying and everyone reading this knows you are lying, why even say anything? There is a reason you guys are not being clear with your changes, stope treating us like we don’t see what’s happening.
So just to be clear — your system hit your provider’s limit, and now we’re the ones blocked from working? That’s not really “rare” when it stalls a live workflow. If you’re relying on third-party models, there should be a fallback in place. This kind of outage — without warning or recovery — shows a lack of proper failover planning and really hurts confidence in the platform. Honestly, it’s hilarious.
Wasted a full day ■■■■■■■ about with trying to understand all this pricing stuff, really really bad guys, pricing should be a) clear b) simple and c) not mislead.
There’s too many component parts to how “pricing” now appears to work. I still haven’t figured out, what’s a limit, what’s burst, fast request, slow, auto, max, got ■■■■ this is infuriating. I now got rate limited and apparently saved $228 since July 1?
Looking at alternatives tbh.
First of all, I paid the cursor. You should ensure that we can use it normally within the payment plan. You should consider the rate limit of the provider when formulating the payment plan. I can’t stand the rate limit on my first request of the day. I think you are shirking your responsibility.
Im reaching claude limit with 2-3 requests haha, if that continue I will stop paying that useless subscription.
I’ve had the exact same issue, 176$ since July 2. Now I get 2 requests a day at 9pm only … Claude Code is the best option honestly, but I wont be able to continue working this month unless I can get a full refund
At all is it possible to refund? I cancelled my subscription but I want refund.. I don’t know XD