claude-code - 💡(How to fix) Fix [DOCS] VS Code diff review docs omit that Claude sees manual diff edits before approval [1 comments, 2 participants]

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/vs-code

Section/Topic

"Review changes" in the VS Code extension guide

Current Documentation

The VS Code guide currently says:

When Claude wants to edit a file, it shows a side-by-side comparison of the original and proposed changes, then asks for permission. You can accept, reject, or tell Claude what to do instead.

The overview page currently summarizes the feature this way:

The VS Code extension provides inline diffs, @-mentions, plan review, and conversation history directly in your editor.

Neither page explains that you can edit the proposed content directly in the IDE diff and that Claude is informed about those edits before you accept the change.

What's Wrong or Missing?

Claude Code changelog v2.1.110 adds a user-visible IDE diff behavior: when you edit the proposed content in the IDE diff before accepting, the Write tool now informs the model about your edited version.

The current VS Code documentation only describes three outcomes for a proposed edit: accept it, reject it, or tell Claude what to do instead. That misses an important fourth workflow: directly modifying the proposed patch in the IDE review UI and having Claude continue from the version you edited.

Without this explanation, users have no reason to know that manual edits in the diff viewer are part of the Claude feedback loop rather than a local adjustment Claude never sees.

Suggested Improvement

Update the VS Code "Review changes" section to document the editable diff workflow explicitly.

Suggested addition:

You can also edit the proposed content directly in the IDE diff before accepting it. Claude sees those edits and uses the modified version as the basis for the final file change, which makes it easier to make small adjustments without rejecting the edit and writing a separate follow-up prompt.

Also update the VS Code feature summary (and any IDE integration overview text that mentions inline diffs or diff viewing) so users can discover this behavior before they hit a permission prompt.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

Total scope: 3 pages affected

Source: Changelog v2.1.110

Release entry under review: "Write tool now informs the model when you edit the proposed content in the IDE diff before accepting"