Repository navigation
Render write() tool content as readable file text - #1024
Merged
Merged
Conversation
(cherry picked from commit 8476b85b6579054a61a7da97592deb0eb7646dd0)
…ents Show the file text only for a write whose input is just path/file_path and content, so another argument (a mode, a title) stays visible. Streamed input, which is still incomplete JSON, and an empty file keep the generic view too. Drop the duplicate tool-call-expansion import the merge with main left in the test file, which stopped MessageView.test.mjs from loading. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This was referenced Oct 4, 2026
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
2 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.
Instead of the raw json arguments with literal "\n", render write() results similar to edit()