GitHub Issuesdemand signalby yakupadaklibuilt with AIheuristic score

anthropics/claude-code: [FEATURE] VS Code Extension: Diff review UI similar to GitHub Copilot Edits Review

Opportunity

AI-buildable

Traction

Creativity

The take

effort: ~1-2 weeks

Heuristic estimate (AI scoring not configured). anthropics/claude-code: [FEATURE] VS Code Extension: Diff review UI similar to GitHub Copilot Edits Review shows 74 engagement on ghissues. Buildability is inferred from the description; add an AI gateway key for a tailored read.

Deliver it

A starter prompt for Claude Code, what you'll need, and how to reach them.

Build a minimal version of "anthropics/claude-code: [FEATURE] VS Code Extension: Diff review UI similar to GitHub Copilot Edits Review". Read the original at https://github.com/anthropics/claude-code/issues/33932 for the exact requirements, then scaffold a Next.js + Tailwind app, implement the smallest valuable slice first, and ship it. (Enable AI scoring for a tailored, detailed prompt.)

Prerequisites — cost & what to learn

Node.js + a Vercel accountFree · Free (hobby tier)✓ in your stack
Part of the operator's house stack.
Any APIs/data the find depends onFree tier · Varies — enable AI scoring for a real cost read.📚 needs study
Depends on the find — enable AI scoring for specifics.
Learn it: Search getting-started ↗

Setup steps

How you'd build it

1Open the project and list its 3-5 core user-facing features.
2Scaffold a Next.js + AI Gateway app and rebuild the smallest valuable slice first.
3Wire any external data/APIs it depends on; stub what you can't access.
4Ship a thin public version and measure whether the demand signal reproduces.

Risks & moats

Traction may be launch-day spike rather than durable demand.
Heuristic scoring can't judge true novelty or competition — verify manually.

Original context

### Preflight Checklist - [x] I have searched [existing requests](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20label%3Aenhancement) 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: 1. A list of all modified files with a pending indicator in the chat pan