feat(livekit-plugins-google): structured responses for Live API tool calls#1
Open
feat(livekit-plugins-google): structured responses for Live API tool calls#1
Conversation
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.
LiveKit automatically converts the result of a tool call to a string (reference), and this string was being returned in the Live API
FunctionResponse.responseasoutput. So, for example:Would get returned to the Live API as:
{ "output": "{'weather': 'sunny', 'temperature_f': 70}" }However, our Live API integration requires returning the actual result, not the string representation.
With this change, we:
FunctionResponseif the tool call did not return anything.FunctionResponse.responseto the actual result by callingast.literal_evalon the string representation.FunctionResponse.schedulingtoSILENTto let the model decide when to use the result (reference).