[docs] Add troubleshooting for Sonnet 4.6 context window meter showing 200K instead of 1M (#61734)#61738
Open
giruuuuj wants to merge 1 commit into
Open
Conversation
This was referenced May 24, 2026
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
1 participant
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.
Summary
Adds a troubleshooting entry for the Sonnet 4.6 context window display/limit bug ? a regression in v2.1.150. The status bar shows 200K and the actual context is capped to 200K, even though Sonnet 4.6 supports 1M tokens per the API.
Root cause: v2.1.150's "internal infrastructure improvements" likely reset Sonnet 4.6's
max_input_tokensfrom 1M back to the default 200K in the model capabilities config. This is the same class of bug as the Opus 4.7 fix in v2.1.117. No user-side workaround exists ? requires a CLI patch to restore the correct value.Closes #61734