[Feature Request] Inline suggested changes in VS Code editor with line-by-line review

Status Closed — not planned
Maintainer reply None cached
Activity 5 comments · opened Jan 28, 2026 · closed Mar 1, 2026

Bug Description
Feature request: Inline suggested changes in VS Code editor

When Claude Code edits files, I'd like to see changes as inline "suggested changes" directly in the VS Code editor (similar to GitHub suggestion blocks or VS Code inline completions).

This would allow:

  • Reviewing proposed changes in context within the actual file after all changes by Claude were already made
  • Accepting or declining individual hunks/lines rather than entire edits
  • More natural review workflow in the editor

Currently, accepting/rejecting entire edits means re-prompting when only part of a change is desired. Line-by-line control would be incredibly useful.

View original on GitHub ↗

5 Comments

github-actions[bot] · 8 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/16045
  2. https://github.com/anthropics/claude-code/issues/4322
  3. https://github.com/anthropics/claude-code/issues/7760

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

FBartos · 8 months ago

These requests are related but not the same. I'm asking for a native diff view functionality for VS Code that exists when using GitHub Coding Agent in VS Code or when using Antigravity. In facts, this is probably a major limitation for using Claude Code extension with VS Code.

github-actions[bot] · 7 months ago

Closing for now — inactive for too long. Please open a new issue if this is still relevant.

arijit-chowdhury-genea · 7 months ago

Hi @FBartos. Did you ever find a solution for this (inline suggestions via Claude Code VS Code extension)?

github-actions[bot] · 7 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.