chore: create specific tools for LLM vs. SDK #9
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
Signed-off-by: Grant Linville <grant@acorn.io>
g-linville
requested review from
StrongMonkey,
drpebcak,
iwilltry42,
njhale,
thedadams and
tylerslaton
thedadams
approved these changes
Nov 1, 2024
njhale
approved these changes
Nov 1, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Since we now support arbitrary data instead of just strings, the data we interact with here in the dataset tools is typically base64. It's bad to hand this to the LLM, so this PR introduces specific tools for the LLM which decode the base64, and tools for the SDK which don't. Once we have some kind of "filter" that "undoes" datasets for the LLM, this distinction will no longer be necessary.