Repository navigation
fix(review): recognize Gemini Flash context capacity - #204
Merged
Merged
Conversation
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.
Gemini Flash falls through to the unknown-model context limit, fragmenting reviews across the fallback cascade; recognizing
google/gemini-3.8-flashassigns it the existing conservative 128,000-token ceiling.Google documents 1,048,576 input tokens and 65,536 output tokens, corroborated by the OpenRouter endpoint catalog.
Unknown IDs retain the 32,000-token fallback, while the cascade, 16,000-token output reservation, 32 KiB batch ceiling and 24-batch large-review selection cap remain unchanged.
Regression tests cover exact normalized matching, lookalike rejection and serialized request budgeting across the complete fallback cascade; complete coverage remains required for the normal pre-push review.