It’s a meaningful step up from Sonnet 4.6. On CursorBench, our benchmark of ambiguous, multi-file tasks drawn from real Cursor sessions, Sonnet 5 scores 57% versus 49% for Sonnet 4.6.
Claude Sonnet 5 is available at an introductory price of $2 per million input tokens and $10 per million output tokens through August 31, 2026. After that, it moves to standard pricing of $3 per million input tokens and $15 per million output tokens.
Select Sonnet 5 from the model picker to get started. Available now in Cursor!
Look likes, Sonnet is cheaper than Opus, but in fact, it spend more tokens, so, it not cheaper than Opus.
This is exactly what the graphs make it look like to me too, but I haven’t looked into whether it’s actually true or not. Hard to assess without building the same thing in parallel with the two models.
Try it out, in some conditions, it produce results that are more accurate than opus because it relies more on tools and less of pure intelligence whereas opus do and can be sure of outdated things
Why is it again Max Mode only for legacy plans? With Opus and Fable I can somehow understand it due to their API price, but it doesn’t make any sense with a model like Sonnet.
Are we legacy users stuck forever on Opus & Sonnet 4.6 with no plans to ever get any newer model, even when it’s cheaper?
Hi @eden881 Thanks for the question. Sonnet 5 is actually not Max Mode only. You can use Sonnet 5 without Max Mode, however it is limited to the 300k context window. If you want to use the 1M context window with Sonnet 5, that requires Max Mode.
Hi @eden881 Thanks for following up. You’re correct, I was testing from the wrong type of account. When I switched to my Legacy request based test account I see the same thing you see - Max Mode is required for Sonnet 5 regardless of Context Size.
So this means for usage based accounts, it is true that you don’t need max Mode for the 300k context window but for request based legacy accounts you do need it. This has to do with the cost of the Sonnet 5 model, which is significant
Please let us know any issues. We recently shipped a change to enable Fable 5 in Bedrock. But that could have been a special case because Fable 5 requires specific data permissions