fix: add support for ACP writeTextFile clientCapability #6902
+23
−2
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
Contributor
|
The following comment was made by an LLM, it may be inaccurate: Duplicate Search ResultsNo additional duplicate PRs found. All searches returned only PR #6902 with the same title "fix: add support for ACP writeTextFile clientCapability", which appears to be the PR being reviewed. Summary:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This is an attempt to fix the issue called out in issue 4240. By mirroring the write back to the client it causes the local review flows to trigger. It feels a bit inefficient, but it seems to match with the expectations of the spec. I looked at hijacking the tool call to just do the writes and reads through the client, but I couldn't find a good pattern to make that fit.