[BUG] Cannot edit file changes in VS Code integration anymore

Resolved 💬 16 comments Opened Aug 14, 2025 by JakobBruenker Closed Aug 19, 2025

Environment

  • Platform (select one):
  • [x] Anthropic API
  • [ ] AWS Bedrock
  • [ ] Google Vertex AI
  • [ ] Other: <!-- specify -->
  • Claude CLI version: 1.0.80 <!-- output of claude --version -->
  • Operating System: Windows 11, using WSL with Ubuntu 22.04<!-- e.g. macOS 14.3, Windows 11, Ubuntu 22.04 -->
  • terminal: VSCode <!-- e.g. iTerm2, Terminal App -->

Bug Description

It used to be the case that if Claude suggested an edit and you had VS Code connected, you could see the diff, and make changes to the diff. Pressing enter in the terminal would accept the edit while discarding your changes, however saving the open VS Code diff editor would save the changes you made.

Now however, those changes are discarded regardless.

This wastes a lot of time because each time you want to change something you either have to tell Claude exactly what you want to change or find the place where the edit was made and reorient yourself again.

Steps to Reproduce

  1. Open Claude Code, making sure it's connected to VS Code
  2. Have Claude Code edit a file
  3. Make manual changes to the opened diff editor
  4. Save the open diff editor

Expected Behavior

The manual changes should be part of the file, as well as part of what is shown as the edit that was performed in the terminal (both of these used to be the case)

Actual Behavior

The changes are discarded and now shown in the terminal

View original on GitHub ↗

16 Comments

github-actions[bot] · 11 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/4730
  2. https://github.com/anthropics/claude-code/issues/1317
  3. https://github.com/anthropics/claude-code/issues/1472

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

juli-jumptrading · 11 months ago

Not a duplicate. Downgrading claude code to 1.0.77 (2025-08-12) fixes the issue. Bug possibly introduced in 1.0.78.

callumhay · 11 months ago

This is a pretty serious bug that got introduced very recently. Please fix this, it significantly affects/breaks workflow.

nekitk · 11 months ago

Reproduces with JetBrains Rider too

Henry-E · 11 months ago
Not a duplicate. Downgrading claude code to 1.0.77 (2025-08-12) fixes the issue. Bug possibly introduced in 1.0.78.

Ok but how to stop claude code from auto updating after downgrading

JakobBruenker · 11 months ago

@Henry-E use /config in claude code

callumhay · 11 months ago
@Henry-E use /config in claude code

For anyone else being driven totally bonkers by this bug, don't forget to actually downgrade the terminal (npm) app as opposed to just the vscode extension i.e.,
npm install -g @anthropic-ai/claude-code@1.0.77 --save-exact

sasharosca · 11 months ago

Commenting for visibility. I'm also seeing this issue, running in native Ubuntu w/ VSCode.

sleepo581 · 11 months ago

Bumping this up. The bug appears in IntelliJ products as well.

944750720 · 11 months ago

Same issue in 1.0.83 (Claude Code), Cursor extension version 1.0.83 (server version: 1.0.72).

olegsubbly · 11 months ago

Same issue. Annoying to make edits in a file after.

Nacho2027 · 11 months ago

Yup same issue would love to get this fixed

sleepo581 · 11 months ago

@hackyon-anthropic @bcherny is it possible to not automatically close this issue? It's a valid bug that needs attention please. Sorry for direct tagging.

juli-jumptrading · 11 months ago

Fixed in 1.0.84 🎉 Thanks a lot!

JakobBruenker · 11 months ago

I can confirm that it works in 1.0.84. Thanks!

github-actions[bot] · 10 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.