Repository navigation
Conversation
This branch has not been 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.
Term2's named effort currently becomes a token budget even for current Gemini models, while Pi uses Google's named thinking levels. Send named levels for Gemini 3 Flash, 3.x Pro/Flash and 4+ IDs; retain budget behavior for older/unknown IDs and caller-owned thinkingConfig. Infer minimal as low conservatively and xhigh as high.
Native Gemini 4 Argon accepts the resulting LOW request without relay rewriting. The old budget request is also accepted; this change aligns the control and makes no cost or latency claim.
Validation: 15 real-SDK HTTP regressions (6 fail on base); independent 32-case SDK verification accepted. Final bounded full provider suite: 285 passed, 5 skipped; fake-Codex E2E: 18 passed; static guards, typecheck, lint and baseline gate pass. An earlier full run hit an image/retry composer timeout also reproduced on unchanged main; its logs remain retained. No successful live scenario was repeated.