fix(google): treat signed text as regular content in streaming #6400
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.
Summary
Change streaming to use SignedTextAsRegularText instead of SkipSignedText. Signatures are tracked via last_signature and attached to function calls through effective_signature = signature.or(last_signature).
Gemini 2.5 models include thoughtSignature on the first streaming chunk regardless of whether function calls follow. The old SkipSignedText behavior discarded text parts with signatures, causing content loss.
Signature placement by model:
Type of Change
AI Assistance
Testing
Unit test and tested with 2.5 models locally to verify the fix for their unique behaviour.