[PROTOTYPE] tool_use formatter implementation#916
Draft
LasmarKhalifa wants to merge 4 commits into
Draft
Conversation
LasmarKhalifa
force-pushed
the
06-02/tool-use-implementation
branch
from
0c2ca4b to
a8c4da8
Compare
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
1 participant
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.
Playground for tool use implementations. Most files are just for testing, the relevant one to look at is
tool_use.rbtool_use_foramtter_test.rbwas created to see the tool uses in action.Proposed design:
Single line tool use messages with truncation for long pieces of data.
Things that were considered:
Dual-line tool use: This was a good idea but it made the output harder to understand.
Single-line without truncation:
Long tool_use messages would mess up the visual coherence of the terminal output.