/model switch no longer rejected as an invalid model when a shared usage limit is hit
When /model's check hits a five-hour or seven-day limit, the result is flagged sharedLimitReached and the switch can go ahead instead of failing as invalid_model
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
ModelsArea: what it touches
Bug FixesKind: in v2.1.301,
ImprovementsSection of the release
Unclear It is not clear what you see after a switch that hits the shared limit is accepted.
What
When you switch models with /model, Claude Code first checks the model with Anthropic. That check can be refused with a 429, the error meaning you have hit a usage limit.
When the 429 is not about needing credits and the limit is the five_hour or seven_day one, the result is now marked sharedLimitReached: true.
A switch that would otherwise fail with invalid_model is now allowed when sharedLimitReached is true and the caller passes acceptSharedLimitRefusal. This works like the existing path for credits-required refusals.
The model check now passes acceptSharedLimitRefusal: true, alongside the existing acceptSessionModeRefusal.
Before this release, such a switch was rejected as invalid_model unless credits or another condition allowed it.
Why
Hitting your plan's usage limit during the check no longer makes a valid model look invalid. The switch goes ahead, and the limit can be reported for what it is.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear what you see after a switch that hits the shared limit is accepted.
