Repository navigation
feat(web): the model picker shows when a provider or a model is near its plan's limit - #957
Merged
Merged
Conversation
…nd a model's own limit shows on its row
…l at its limit reads grey
badcuban
enabled auto-merge
November 16, 2026 11:00
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
This branch was previously deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The model picker gave no hint that an account or a model was close to its plan's limit. You found out from the usage popup in the composer, or when a turn failed.
Now:
isProviderUsageNearLimittakes{ modelLimits: false }for the account-only check; the composer's ring calls it as before. A scope label matches a model by whole words in order, so "Opus 5" doesn't match "Opus 5.5".