Feature Request: Interactive Edit Refinement in Diff View

Resolved 💬 3 comments Opened Aug 28, 2025 by diraneyya Closed Sep 1, 2025

Feature Request: Interactive Edit Refinement in Diff View

Problem Description

Currently, Claude Code displays proposed changes in VS Code's diff view for review only. When developers attempt to refine these proposed edits directly in the diff interface, their modifications are lost when the changes are applied or rejected. This creates a friction point in the collaborative editing workflow.

Current Behavior

  1. Claude Code proposes changes and displays them in VS Code's diff view
  2. Developer reviews the proposed changes
  3. Developer can only accept or reject the entire proposal
  4. Any direct edits made to the proposed changes in the diff view are discarded

Proposed Enhancement

Enable interactive refinement of Claude's proposed changes with the following workflow:

  1. Direct Edit Support: Allow developers to modify proposed changes directly in the diff view
  2. Change Detection: Detect when the developer has modified the proposed changes
  3. Collaborative Dialog (ideal): When modifications are detected, prompt Claude to:
  • Acknowledge the changes made by the developer
  • Ask clarifying questions about the intent behind the modifications
  • Incorporate the developer's refinements into the final implementation, and ideally generalise the edits to other places where the intent also applies

Why This Matters

This feature would enable a more natural "show, don't tell" collaboration model where:

  • Developers can demonstrate their intent through concrete code changes rather than verbal descriptions
  • Complex requirements can be communicated through example modifications
  • The feedback loop between human and AI becomes tighter and more efficient
  • It reduces the need for multiple back-and-forth prompt iterations

Use Case Example

1. Claude proposes a function implementation
2. Developer sees it's 90% correct but needs a small adjustment to the error handling
3. Developer directly edits the proposed change in the diff view
4. Claude recognises the modification and asks: "I see you changed the error handling approach - would you like me to apply this pattern to similar functions in the codebase?"
5. Developer confirms, and Claude applies the refined approach consistently

Alternative Implementation

If real-time collaborative dialog is too complex initially, even basic support for preserving developer modifications to proposed changes would be a significant improvement over the current behaviour.

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗