Suppress dynamic tool progress in stderr - #625
Open
LZong-tw wants to merge 1 commit into
Open
Conversation
LZong-tw
marked this pull request as ready for review
August 10, 2026 10:02
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
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.
Summary
Suppress high-frequency
dynamicToolCallprogress updates from foreground stderr while retaining them in each job's log file.Why
The Claude Code host can retain stderr progress as transcript tool output. A task with many dynamic
Read/Bashcalls can therefore create a very large, repetitive JSONL assistant record and make session resume slow or unusable.Change
hideFromStderrto normalized progress events;Validation
npm test