[BUG] Claude Code in VSCode CLI does not respond to ESC and Ctrl+C events

/ Also unable to input

same here, version 2.1.84. in my case also Tab key does not work

I have the same (win11 arm64)
Going back to 2.1.81 resolves the problem temporarily.

This is the Kitty keyboard protocol regression introduced in v2.1.83. Claude Code now pushes enhanced keyboard mode (progressive enhancement level 1+) but doesn't properly handle the protocol in certain terminal emulators, particularly VSCode's xterm.js.
Root cause: The Kitty keyboard protocol sends modifier keys and special keys as CSI sequences (e.g., CSI 57358 u for Caps Lock). When the terminal or the app doesn't fully decode these sequences, raw escape codes leak into input and key events like ESC/Ctrl-C get swallowed or misinterpreted.
Workaround — force xterm.js back to standard keyboard protocol:
Add this to your VS Code settings.json:

{
  "terminal.integrated.keyboard.protocol": "standard"
}

This tells xterm.js to not advertise Kitty protocol support, so Claude Code won't push enhanced mode.
Alternative — pin to 2.1.81:

npm install -g @anthropic-ai/claude-code@2.1.81

Why downgrading works: v2.1.81 didn't push Kitty keyboard protocol, so ESC, Ctrl-C, and Ctrl-D were handled through standard ANSI sequences.
The fix should come from Claude Code properly popping the Kitty protocol on exit and correctly decoding all key events while in enhanced mode. This is tracked across several related issues (#38761, #38647, #38840).

This VS Code setting works for me with 2.1.84
"terminal.integrated.enableKittyKeyboardProtocol": false

@ashokvc this works , thanks for sharing

I was also stuck in that situation, but pressing CTRL + C multiple times worked for me.

This issue is really killing my Claude Code (CC) productivity. Sometimes I have accept edits on, and watch CC take 10 mins updating many files with the wrong design. Only when it ends do I get the chance to instruct it on the proper design for the fix. If my git is not up to date I have to rely on CC correctly reverting the code changes. The help text in the terminal says "Hit esc to interrupt", so it's frustrating when the software is not compliant with its own instructions. If you comment, don't deflect: my prompting is wrong, I should have updated git before code changes, my using CC wrong, etc. Programs have been interrupting processing for decades; why can't CC? I don't get why this is hard?

Version 2.1.81 (Claude Code)
Windows 11
Windows Terminal running PS 7.6.0

This was fixed in v2.1.85 — Restored terminal allowlist for Kitty keyboard protocol so VS Code integrated terminal (xterm.js) and SSH sessions no longer get pushed into enhanced keyboard mode, fixing ESC/Ctrl+C/Shift+Tab/Ctrl+W being swallowed on Windows. If you're still seeing this in the latest version, please comment with your version and repro and we'll reopen.

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.