[FEATURE] VS Code Extension: Diff review UI similar to GitHub Copilot Edits Review
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
When Claude Code modifies files in the VS Code extension, there is no built-in UI to review, accept, or reject those changes. I have to leave the Claude Code panel and manually check the Source Control panel or run git diff to see what changed — this breaks the flow completely.
GitHub Copilot solves this with "Edits Review": a dedicated inline diff UI that lets you accept/reject changes per-file or per-change without leaving the chat context. Claude Desktop's Code tab already has a similar diff stats indicator (+12 -1) with a clickable diff viewer, but this is missing from the VS Code extension.
The current workflow requires me to manually switch to Source Control, review diffs there, and then come back — all outside the Claude Code interface.
Proposed Solution
After Claude Code modifies files, the VS Code extension should show:
- A list of all modified files with a pending indicator in the chat panel and Explorer view
- An inline diff in the editor when a modified file is opened
- Editor overlay controls to navigate between changes and accept/reject them individually (per-change and per-file)
- "Accept All" / "Reject All" buttons in the chat panel
This is exactly how GitHub Copilot Edits Review works: https://code.visualstudio.com/docs/copilot/chat/review-code-edits
Claude Desktop already has a diff viewer (diff stats indicator +12 -1 that opens a diff viewer with inline commenting). Bringing this to the VS Code extension would close the gap.
Related: Desktop diff viewer bug #26548
Alternative Solutions
Currently I switch to VS Code's Source Control panel and review diffs there manually after each Claude Code session. I also use git diff in the terminal.
Other tools solve this natively: GitHub Copilot has Edits Review built into the chat panel, and Claude Desktop already has a diff stats indicator with a clickable diff viewer — so the capability exists within Anthropic's own ecosystem, just not in the VS Code extension.
Priority
High - Significant impact on productivity
Feature Category
Interactive mode (TUI)
Use Case Example
- I ask Claude Code in VS Code: "Refactor the authentication module and update all related tests"
- Claude modifies 8 files across the project
- Currently: I have to open Source Control panel, click each file one by one, review the diff, then decide — completely outside the Claude Code interface
- With this feature: A pending edits list appears in the chat panel, I click each file to see the inline diff, and accept/reject changes without ever leaving Claude Code
- This would save significant time and reduce the risk of accidentally accepting unwanted changes across large refactors
Additional Context
Similar features in other tools:
- GitHub Copilot Edits Review (VS Code): https://code.visualstudio.com/docs/copilot/chat/review-code-edits
- Claude Desktop Code tab already has a diff stats indicator (+12 -1) with a clickable diff viewer and inline commenting — this feature exists within Anthropic's own ecosystem but is missing from the VS Code extension
- Related bug where Desktop diff viewer is broken: #26548
The VS Code extension's checkpoints feature (rewind) partially addresses this, but it's a revert mechanism — not a review/accept/reject workflow. Users need granular control over which changes to keep before committing.
Showing cached comments. Read the full discussion on GitHub ↗
30 Comments
I created a VS Code plugin that allows me to review markdown files and then generates a response prompt with comments on the lines or selections made.
Actually crazy that this doesn't exist. It is a standard for IDE extensions at this point - would love to see it implemented!
This is our repo is in alpha mode.
I recently switched from github copilot to claude code, and this feature is the one i miss the most. Hopefully it gets implemented soon. The UX with Copilot chat is easy to understand and visually clean
you can use claude code in vscode, and you have full of plan
@mikeleg yes I'm using that, i have the claude extension for vscode. Before, I was using GitHub Copilot (student package) with the claude agent sdk https://code.visualstudio.com/docs/copilot/agents/third-party-agents#_claude-agent-preview . I'm not sure if i can use claude via github copilot agents but with my claude subscription
We created a new plugin for vscode for a review plan.
I ran into the same issue, so that's why this library exists.
https://github.com/molon/hunkwise
Happy to hear feedback!
<img width="2338" height="2054" alt="Image" src="https://github.com/user-attachments/assets/a3d3852f-a8b0-490f-bc0b-a9e471cb37b3" />
@molon The extension works perfectly! Thank you for creating this!
I'm waiting for that feature. Would be very nice.
Adding another data point to this — the issue is even more fundamental than just "no review UI".
When Claude Code: (VS Code: native UI panel) edits files, the changes are written directly to disk without going through VS Code:'s
TextEditorEditAPI. As a result:The only way to see what changed is to manually open Source Control panel or run
git diff. This makes the current workflow not just "inconvenient" but actually error-prone for large refactors where you need to verify every line.Would love to see this prioritized, especially since Claude Desktop already has the diff stats indicator (
+12 -1) and clickable diff viewer — the capability clearly exists within Anthropic's ecosystem.This is very critical feature that must be prioritized (I hate engineering with Claude code because of this). It seems it's designed for vibe coders where they blindly accept anything.
I have been looking around for sometime why no one complains about this because it's so important for technical people. The experience to review, accept, reject small edits or even review the whole session edits is so critical. Will try @molon extension and hope it closes this gap.
Claude code is basically just a vibecoding app for non-engineers until this exists.
@ashwin-ant You guys cannot possibly think that we will edit production code without having clear diff gates on the files.
This feature should have been included in the very first MVP of Claude Code.
Having to do all the work using
git diffcompletely disrupts the workflow. Any time Claude might save us is wasted on checking which lines it has modified and how. It makes no sense. What’s more, it’s very easy to clutter up the Git history with this way of working.This is needed very badly. Kind of ridiculous this is not even a feature yet. I'm a GHCP refugee (after they completely annihilated their payment model and user base this month) and not having inline approval just completely shuts down my workflow.
I need this feature very badly. If you don't change this fundamental principal approach, soon there will be a huge tech debt in this extension.
Please, please, please implement this. Some of us do actually want visibility and control over each edit. It helps so much when it comes to seeing how an LLM approached the problem and solution. This is absolutely critical for specialized code, where every single LLM chokes and needs more specific direction and back-and-forth with the developer.
The fact that this isn't a standard option across all editors/tools, is deeply confusing and frustrating to me. It genuinely makes me consider using lesser tools and LLMs, just for this functionality.
This is a must have feature. Please implement this
As a former GitHub Copilot user, the lack of an inline "Edits Review" UI is the single biggest point of friction in adopting Claude Code right now.
This breaks the developer flow completely. Relying on
git diffas a workaround is inconvenient and error-prone when dealing with large refactors.Really hope this gets prioritized!
I'll add my voice to the list on this one. Having used GitHub Copilot in a few places, the Claude Code extension is pretty solid...right up until it starts making edits.
This change would bring it right to the top of choices to use!
Honestly at some point I will start paying copilot again. Shame it is not as nice
How was this not already implemented in the first release of the extension?? Codex extension, Cursor, Copilot already has this and it works fine. Without it Claude looks like a vibe coding toy and not a proper work tool.
Claude Code and Codex both dont have this
Mandatory feature, should be an easy one for claude code :-)
You may use the VS Code Source Control tab to manually review, stage, and stash changes, but Cursor lets you approve or reject AI-generated edits before they're applied, making the workflow much smoother. I feel like I have more control over my changes.
I wonder how developers are happy using Claude Code
Wow. Dealbreaker switching from GitHub Copilot.
That sums it up perfectly
bumping
I just bumping it for more views.
This is the only reason I dont want to switch from Copilot to Claude Code
Edit: They would make to much money just from this small change