feat(protected): exclude read/bash from recent-zone - #35
Merged
Conversation
read (file/image contents) and bash (build/test/log output) are the largest common sources of tool-result context bloat. When such results land in the preserveRecentMessages last-N window they become un-compressible — the model cannot reclaim that context, and they never appear in compressible-ranges recommendations. Add read/bash to NEVER_PRESERVE_RECENT_TOOLS (alongside decompress and search_context). They remain fully visible and compressible like any ordinary message — this only removes them from the soft-protected recent zone, so the protected window covers actual conversation turns (user intent, assistant reasoning, tool dispatch decisions) instead of being filled by spent file/command output.
Merged
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.
Why
read(file/image contents) andbash(build/test/log output) are the largest common sources of tool-result context bloat. When such results land in thepreserveRecentMessageslast-N window they become un-compressible — the model cannot reclaim that context, and they never appear in compressible-ranges recommendations.Change
Add
readandbashtoNEVER_PRESERVE_RECENT_TOOLS(alongsidedecompressandsearch_context).They remain fully visible and compressible like any ordinary message — this only removes them from the soft-protected recent zone, so the protected window covers actual conversation turns (user intent, assistant reasoning, tool dispatch decisions) instead of being filled by spent file/command output.
Verification
compress/protectedTools(always-protected) — only the soft recent-zone is affected.