include name, arguments, result & error (as applicable) in function_call_XXX events so they are much more useful #283
+10
−2
Conversation
This file contains 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
…all_XXX events so they are much more useful
|
|
|
|
Link to slack discussion about the need for this change: https://livekit-users.slack.com/archives/C07FRP66XGE/p1736962087704659 |
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.
These events are perfect for observing when a function is called, completes or throws an error so that additional steps can be taken by the agent that cannot normally run directly within the function context (such as taking some additional action before hanging up or transferring a call). But the events as coded unfortunately did not include any context about the function in the event payload. This PR adds that important context information.