From 9212ebcd1157f6c532310aaa2dc95616b48f1f24 Mon Sep 17 00:00:00 2001 From: mahdiwafy Date: Tue, 28 Jul 2026 18:31:26 +0700 Subject: [PATCH] fix(antigravity): strip parametersJsonSchema before sending to v1internal PR #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. --- open-sse/executors/antigravity.js | 3 +++ 1 file changed, 3 insertions(+) diff --git a/open-sse/executors/antigravity.js b/open-sse/executors/antigravity.js index 2e3a510695..956103663e 100644 --- a/open-sse/executors/antigravity.js +++ b/open-sse/executors/antigravity.js @@ -245,6 +245,9 @@ export class AntigravityExecutor extends BaseExecutor { ? cleanJSONSchemaForAntigravity(structuredClone(fn.parameters)) : { type: "object", properties: { reason: { type: "string", description: "Brief explanation" } }, required: ["reason"] } }); + // Strip parametersJsonSchema — v1internal uses parameters only; + // both fields cause 400 "must not be set when parameters is set". + delete allDeclarations[allDeclarations.length - 1].parametersJsonSchema; } } tools = allDeclarations.length > 0 ? [{ functionDeclarations: allDeclarations }] : [];