Repository navigation
Add Gemini 4 Argon with bounded live eval coverage - #414
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.
Nexus can now use
gemini-4-argonthrough the Google provider, with the documented thinking levels, sampling restrictions, output limits, timeout, and introductory pricing. The existing Google default stays in place. Responses requiring Google's separate long-decode continuation protocol surface as incomplete instead of silently appearing complete.Live testing exposed Google's rejection of the existing tool-schema encoding. Send native
parametersJsonSchemaso the released Nexus tool catalog retains its JSON Schema constraints and works with Argon.The eval harness now supports bounded output and tool rounds, consumes current chat runtime events, fails on aborted/failed turns, records per-response usage, and evaluates chat context against the current runtime contract. The committed five-scenario configuration uses low thinking, 2,048 generated tokens per request, four tool rounds, and no retries. Skill guidance and generated mirrors document the verification findings.
Validation:
Official references checked: model documentation, latest-model integration guidance, pricing, thinking, long decode, and function declarations. The model ID and limits were also checked against the authenticated API.