[BUG] Ctrl + S (Save operation) in VSCode auto-accepts proposed changes by Claude Code Cli

Resolved 💬 3 comments Opened Feb 20, 2026 by IT-Knight Closed Feb 24, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

When VS Code is connected as /IDE, when Code Changes are proposed, I want to:
1 make changes in the code in Vs Code
2 add explanation context to the AI at 1 Yes, [the extra context].

When I make changes — the file state changes, and requires to be Saved.
However, On Save — triggers "1. Yes," [without any context] in the Cli.
So: I can only make silent changes, or provide explanation to the Cli — which equally often is a stupid situation: to explain common things, or let AI continue doing same mistakes.

What Should Happen?

On file Save in Vs Code (as external connected IDE for code diff) — changes are saved, and I can provide extra context to Claude via "1 Yes, bla-bla-bla", to stop him repeat mistakes.

Error Messages/Logs

Steps to Reproduce

1 Open Claude Code Cli in Windows
2 Ensure Vs Code connected as /Ide to the cli
3 Make the model to create some code "hello world"
3.2 Cli should auto-open the Vs Code with git-Diff
4 Change the "hello world" to "hello claude"
5 Save the file with Ctrl + S or another way
6 This will trigger the Cli to auto-accept the code changes and continue it's work
(but shouldn't — file just has to be saved without acceptance)

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.49 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

WSL (Windows Subsystem for Linux)

Additional Information

Gemini Cli has it correct as extra example))

View original on GitHub ↗

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