Just updated Cursor to 1.1.3
1.1.3
979ba33804ac150108481c14e0b5cb970bda3260
arm64
Looks like the claude-sonnet-4-thinking
model’s request usage just skyrocketed.
It used to be 0.8x, now it’s 10x more? Seriously?
Just updated Cursor to 1.1.3
1.1.3
979ba33804ac150108481c14e0b5cb970bda3260
arm64
Looks like the claude-sonnet-4-thinking
model’s request usage just skyrocketed.
It used to be 0.8x, now it’s 10x more? Seriously?
I was wondering how I managed to use >100 requests in the past 2hrs or so…
Maybe they just have a new unit system and these don’t map onto the old requests?
My 100 fast requests vanished after just 2 prompts! Not cool, Cursor Team. Changing limits without notice is unacceptable. Today’s blog post lacks clear info. Lol. @danperks
This is really bad, the roll out of this new pricing model has been terrible. I have about 20 developers (and I was going to roll out more) that I’m going to try to find a new solution for. This really is no good.
Ok I think this is a new unit that doesn’t map onto the old 500 limit. I’m well over 500 now and the requests still show “Included in Pro” in the dashboard.
Hi @catkins Where are you seeing that usage? Is that a 3rd party extensions/plugin? It’s likely that the 3rd party extension does not yet support the new pricing plan and is showing incorrect usage.
I’m looking at the usage events for your account, and I’m not seeing any 10x request usages. Can you take a look at Cursor - The AI Code Editor and see if you see anything wrong there?
The Claude 4 Sonnet is consuming usage limits much more quickly than previous models. This didn’t happen before.
Guess the cursor devs are vibecodeing and releasing without any kind of proper testing. They clearly need to support the legacy pricing plan with the corresponding cost metric. However they are now using the new new cost, even if the user opted for legac plan. The new cost for sonnet 4 is around 10x or more compared to the old one because they are counting each tool call as 1 request.
It’s obviously a bug, or they failed to clearly address this issue—intentionally or just cleverly dodging?
@marcosperez Are you using any third party extensions/plugins to track usage? We suspect some of these aren’t compatible with the new pricing information and are reporting wrong data.
If you’re using any, would be great to know so we can track down and see if there’s a fix we can put on our side to keep the tracking extensions backwards compatible.
It sounds like legacy plans are being charged at the normal rate:
@Zackh1998 The extension I use has the same issue:
There may be a bug in usage metrics processing … I added paid requests to my 1000 request 2x pro account yesterday and am getting 03 showing up for free now after being charged for it yesterday …
Hey @Zackh1998, search for the Cursor Pulse
extension—the pricing model looks like it’s changed. Check out my other post for more details:
We rolled out the new pricing plan by default to everybody earlier this morning; some amount of free usage while below rate limits is expected (only after rate limits are exceeded would we dip into the usage base pricing spend limit).
The Cursor team is tweaking the Pro quota algorithms while rolling out their shiny new $200/month Ultra plan!!
Taking a look a this; we’re going to try to make some of these usage based API endpoints backwards compatible so extensions like these don’t show incorrect usage (probably they’ll show no usage for requests that were under rate limits and not charged).
If you switch to legacy pricing it should work the same (although I’m not sure if it will incorrectly report the old events still, especially since it looks like the extension might cache some data on disk)?
To get the usage extension/plugin fully working with the new pricing system, it might require updating some of the code there.
@Zackh1998, my account’s already on usage-based now. It’s actually my colleague’s account that’s running into this.
probably they’ll show no usage for requests that were under rate limits and not charged
Does this mean that you won’t get charged for usage based calls (i.e. max mode) as long as you are under the rate limit?
why i got 1 dollar
Oh, got it. So basically, all the Pro plans are now “Unlimited Requests” with a “Limited Rate.”
@Zackh1998, if that’s the case, when does usage-based pricing actually kick in, or does it never?