Improve Tool Input Display #1282
Merged
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
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.
Display tool args (inputs)
This doesn't change code display (like python or bash). Previously, we would only show inputs for a small set of tools we knew (and for these we would show a single input only). This change will show the tool call as it was made with args. This was done to better support computer use, but I think it's a good improvement across the board since hiding tool input params seems harmful rather than helpful.
Other Fixes
Fix tool input text highlighting which wasn't working since our migration to react.
Also a variety of react link (a nested hook that I ran across as well as fixes to warnings when running the developer version).
This PR contains: