-
Notifications
You must be signed in to change notification settings - Fork 18.2k
Clarification needed: Are Opus and Sonnet limits independent or shared after Nov 24 update? #12487
Description
Summary
The November 24, 2025 announcement about Opus 4.5 states that Sonnet now has its own separate limit, but the official support documentation still describes limits as shared. This creates confusion about whether maxing out Opus usage will prevent access to Sonnet.
Conflicting Information
Announcement (suggests independent limits):
The November 24 update message states:
"We've increased your limits and removed the Opus cap, so you can use Opus 4.5 up to your overall limit. Sonnet now has its own limit—it's set to match your previous overall limit, so you can use just as much as before."
This wording strongly suggests that Opus and Sonnet are now tracked independently.
Support Documentation (suggests shared limits):
The official support article "Using Claude Code with your Pro or Max plan" states:
"Both Pro and Max plans offer usage limits that are shared across Claude and Claude Code, meaning all activity in both tools counts against the same usage limits."
It also notes that "Using more compute-intensive models will cause you to hit your usage limits sooner," which implies a shared pool.
User Reports:
GitHub issue #3588 shows a user who was cut off from Sonnet after heavy usage, though this may have been due to excessive API calls from hooks.
Questions
-
Are Opus and Sonnet limits now independent as of November 24, 2025?
- If I max out my Opus usage, can I still use Sonnet?
- If I max out my Sonnet usage, can I still use Opus?
-
Should the support documentation be updated to reflect the new limit structure?
-
What does "Sonnet now has its own limit" mean exactly?
- Completely separate tracking from Opus?
- Or does it mean something else?
Context
This clarification would help users understand how to effectively manage their usage across both models, especially for Max plan subscribers who want to use Opus for complex tasks while preserving Sonnet availability for routine work.