Open
Conversation
Adds OutputFilter dataclass with three presets: - full (default): show everything - compact: hide tool results (useful for hiding sensitive output) - conversation: show only user/assistant text (no tools, thinking) The backend uses individual boolean flags (hide_tool_calls, hide_tool_results, hide_thinking) with a should_hide() method, making it easy to add granular CLI flags later. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
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.
Really like this tool!
I wanted to be able to share transcripts without leaking the tool call results (which contained proprietary data/code). This adds an
--output-modeflag (documented in the README) to allow different modalities.You can see how it works by viewing these three logs of the conversation I used to have Claude write the code:
@simonw would love your input on this. This also addresses (at least partially) #61