fix(antigravity): strip parametersJsonSchema before sending to v1internal - #66
Closed
mahdiwafy wants to merge 1 commit into
Closed
fix(antigravity): strip parametersJsonSchema before sending to v1internal#66mahdiwafy wants to merge 1 commit into
mahdiwafy wants to merge 1 commit into
Conversation
…rnal PR Vanszs#61's Gemini CLI fix converts parameters -> parametersJsonSchema for Cloud Code Assist. But Antigravity's v1internal API uses the standard 'parameters' field. The ...fn spread in transformRequest leaked parametersJsonSchema through while also setting parameters, causing Google API to reject with: parameters_json_schema must not be set when parameters is set. Delete parametersJsonSchema after building each function declaration in the antigravity executor tool pipeline.
Author
|
Superceded and merged locally into the main working branch (fix/claude-5-models). Closing to clean up PR list. |
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.
Problem
After merging PR #61 (Gemini CLI tool schema fix), sending requests through Antigravity via
v1internalfails with:All 82 tool declarations are rejected by Google's API.
Root Cause
PR #61 correctly converts tool schemas from
parameters→parametersJsonSchemafor Cloud Code Assist, which requires the latter. However,AntigravityExecutor.transformRequest()spreads the incoming function declarations (...fn) and then setsparameters— resulting in both fields present on the same declaration. The Antigravityv1internalAPI rejects this combination.Fix
Strip
parametersJsonSchemaafter building each function declaration in the antigravity executor tool pipeline. Thev1internalendpoint uses the standardparametersfield.Impact
Zero — this is purely a compatibility fix. No features, schemas, or provider support is affected.