-
Notifications
You must be signed in to change notification settings - Fork 3.7k
fix(google): allow generate_reply without a mutable chat context #7193
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
Darshak03
wants to merge
1
commit into
livekit:main
Choose a base branch
from
Darshak03:fix/gemini-generate-reply-immutable-ctx
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+82
−16
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🟡 Text input disappears before generation
With Gemini 3.1,
generate_reply(user_input=...)sends"."becauseinstructionsis absent. The immutable context path never forwards the user's text, so the model answers without it.Prompt for agents
Was this helpful? React with 👍 or 👎 to provide feedback.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The gap is real, but it is pre-existing and not in the code this PR touches, and this change strictly improves it.
Two corrections on the mechanism first.
generate_replyhas nouser_inputparameter — the abstract signature inllm/realtime.pyisinstructions,tool_choice,tools, and no plugin extends it.user_inputis a private parameter ofAgentActivity._realtime_reply_task, and it is never forwarded togenerate_reply. The text is delivered a step earlier:So the text is dropped by
_sync_chat_ctx, which builds turns only whenmutable_chat_contextis true. That is where the gap lives, and it predates this PR.On
maintodaygenerate_replyraisesRealtimeErrorfor these models, so this path produces no turn at all. After this change the turn happens, with the user text still missing — a broken path becomes a partial one. Audio input is unaffected either way, since_realtime_generation_tasksends audio straight to the model.Worth flagging for whoever picks the remaining gap up:
send_realtime_input(text=...)is itself a generation trigger — that is exactly why this PR uses it. Forwarding user text through it insideupdate_chat_ctxwould start a turn, andgenerate_reply's"."would then start a second one. Closing the gap needs either the plugin holding the unsent user text sogenerate_replycan send it as the trigger, or lettinggenerate_replycarry user content — neither of which belongs in this change.