fix: bound diff_edit result context - #798
Merged
will-lamerton merged 1 commit intoAug 9, 2026
Merged
Conversation
RealBhupesh
requested review from
Avtrkrb,
akramcodez and
will-lamerton
as code owners
August 5, 2026 12:44
3 tasks
This was referenced Aug 9, 2026
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
diff_edit's full-file response with three lines of context around each changed regionWhy
diff_editreturned the entire modified file after a successful edit. On large files this duplicated content already present in the conversation, consumed unnecessary context, and increased latency. The tool now returns only the information needed to verify the edit and directs the model toread_filewith a narrow range when more context is needed.Closes #795
Validation
pnpm exec ava source/tools/file-ops/diff-edit.spec.tsx(19 tests passed)pnpm run test:all(6,258 tests passed, 1 skipped)pnpm exec changeset statusgit diff --checkNote: Semgrep was not installed locally, so the repository's optional Semgrep step was skipped by its test script.