🤖 feat: add filter_exclude to bash_output tool #1081
Merged
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.
Add a boolean
filter_excludeparameter to thebash_outputtool that inverts the filter behavior:true, lines matchingfilterare excluded instead of keptProblem
When polling
bash_outputfor long-running processes likewait_pr_checks.sh, agents generate excessive tool calls because:⏳ Checks in progress...every 5s)timeout_secsonly sets upper bound - returns early when ANY output arrivesSolution
With
filter_exclude:The agent can set a long timeout and only wake when meaningful output (✅ or ❌) arrives.
Tests Added
filter_excludewithoutfilterGenerated with
mux