fix(antigravity): drop messages whose parts become empty after thought filtering - #3366
Open
Lucifer07 wants to merge 1 commit into
Open
fix(antigravity): drop messages whose parts become empty after thought filtering#3366Lucifer07 wants to merge 1 commit into
Lucifer07 wants to merge 1 commit into
Conversation
…t filtering
When an assistant message contains only reasoning/thought parts (no text,
no tool calls), the part filter strips every part, leaving parts: []. The
Antigravity/Gemini API rejects this with HTTP 400 INVALID_ARGUMENT
("Request contains an invalid argument."), breaking long agent
conversations that include thinking-only turns.
Filter out such messages after mapping contents so no empty-parts message
is sent upstream.
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
1 participant
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
When an assistant message contains only reasoning/thought parts (no text, no tool calls), the part filter in
open-sse/executors/antigravity.jsstrips every part, leavingparts: []. The Antigravity/Gemini API rejects this with HTTP 400INVALID_ARGUMENT("Request contains an invalid argument."), breaking long agent conversations that include thinking-only turns.Fix
Filter out messages whose parts become empty after the thought-part filtering, so no empty-parts message is sent upstream.
Verification
Reproduced the exact 400 through a live router, then confirmed the fix returns 200 with a valid stream for: thinking-only assistant turns, normal requests, and tool-call histories.