feat(live): Handle input transcription differently for Gemini Live 3.1 models#6045
Merged
Conversation
Add test for input transcription handling in Gemini 3.1.
Collaborator
|
Response from ADK Triaging Agent Hello @wuliang229, thank you for contributing to the We noticed that this PR introduces a feature/fix for Gemini 3.1 Live models. To help the review process proceed smoothly, please make sure your PR follows our contribution guidelines. Could you please update the PR description with the following:
Your help in providing this context is highly appreciated and will save review time. Thank you! |
wukath
approved these changes
Jun 10, 2026
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.
For Gemini 3.1 Flash Live, input transcriptions are now marked as finished in the first response containing text, rather than being accumulated as partial updates. This aligns with the expected behavior of the 3.1 API.