Skip to content

fix(antigravity): strip parametersJsonSchema before sending to v1internal - #66

Closed
mahdiwafy wants to merge 1 commit into
Vanszs:mainfrom
mahdiwafy:fix/antigravity-parametersJsonSchema
Closed

fix(antigravity): strip parametersJsonSchema before sending to v1internal#66
mahdiwafy wants to merge 1 commit into
Vanszs:mainfrom
mahdiwafy:fix/antigravity-parametersJsonSchema

Conversation

@mahdiwafy

Copy link
Copy Markdown

Problem

After merging PR #61 (Gemini CLI tool schema fix), sending requests through Antigravity via v1internal fails with:

parameters_json_schema must not be set when parameters is set.

All 82 tool declarations are rejected by Google's API.

Root Cause

PR #61 correctly converts tool schemas from parametersparametersJsonSchema for Cloud Code Assist, which requires the latter. However, AntigravityExecutor.transformRequest() spreads the incoming function declarations (...fn) and then sets parameters — resulting in both fields present on the same declaration. The Antigravity v1internal API rejects this combination.

Fix

Strip parametersJsonSchema after building each function declaration in the antigravity executor tool pipeline. The v1internal endpoint uses the standard parameters field.

Impact

Zero — this is purely a compatibility fix. No features, schemas, or provider support is affected.

…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.
@mahdiwafy

Copy link
Copy Markdown
Author

Superceded and merged locally into the main working branch (fix/claude-5-models). Closing to clean up PR list.

@mahdiwafy mahdiwafy closed this Jul 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant