add "processed_content" to ToolResult struct and support storing Elixir data from function results #192
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
- added test
- documentation updates
- LLMChain.execute_tool_call supports Elixir functions returning {:ok, "llm result text", elixir_data_to_keep}
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.
This allows an Elixir function executed by an LLM through a
LangChain.Message.ToolCallandLangChain.Functiondefinition to return and store the raw Elixir data structure in the matchingLangChain.Message.ToolResult.An Elixir function can return a 3-item tuple like this:
Where the
elixir_data_to_keepis assigned to the%ToolResult{processed_content: raw_result}.LLMChain.execute_tool_callsupports Elixir functions returning a 3-item tuple with the raw result