Claude Code VS Code Extension Adds Per-Change Accept and Reject in Diffs
Claude CodeThe Claude Code VS Code extension added accept and reject buttons under each change in its proposed-change diff tab, so an edit can be reviewed change by change instead of approved or rejected as a whole. Developers can now keep the parts of an edit they trust and reject only the parts they don't, within a single review pass. It shipped in Claude Code 2.1.275, released September 17, 2026.
Key Takeaways
- VS Code's proposed-change diff tab now shows accept and reject buttons under each change, not a single decision for the whole file.
- An edit can be reviewed change by change, keeping trusted hunks while rejecting the rest.
- It shipped inside version 2.1.275 on September 17, 2026, alongside dozens of other VS Code extension fixes.
- The change is scoped to the VS Code extension's proposed-change diff tab.
- Per-hunk review means a single questionable change no longer forces a whole turn to be discarded.
- It brings the extension's review UX closer to the inline diff review developers expect from other editor integrations.
From Whole-File to Per-Change Review
Before this release, reviewing a Claude Code edit inside VS Code meant accepting or rejecting the proposed change as one unit, even when only part of it looked risky. Version 2.1.275 added accept and reject buttons under each change in the proposed-change diff tab, so an edit can be reviewed change by change.
Why It Matters
Reviewing hunk by hunk lets a developer accept the safe parts of an edit while holding back the riskier ones from the same turn, instead of rejecting everything and re-prompting. For large multi-file edits, that difference compounds: a single questionable hunk no longer forces a whole turn to be discarded and redone.