fix: preserve grep and ls tool results#211
Draft
lawyer112 wants to merge 1 commit into
Draft
Conversation
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.
What changed
grepmatches, file lists, counts, and truncation metadata in replayed tool results.lsdirectory tree instead of reducing it to path and file-count metadata.Why
Successful
grepandlstool calls were previously summarized as metadata-only strings. On the next model pass, the assistant could see that a tool succeeded but not the files, matches, or directory entries it needed to continue.Impact
The model receives the useful contents of successful search and listing calls, while payload limits still prevent oversized replay messages.
Validation
go test ./...18080/18090runtime.