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

[DevendraTomar]

Preflight Checklist

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

What's Wrong?

When running Claude Code via the VSCode integrated terminal (CLI), keyboard interrupt signals such as ESC and Ctrl+C are not being handled correctly. The process does not respond to these events as expected.

What Should Happen?

Description

When running Claude Code via the VSCode integrated terminal (CLI), keyboard interrupt signals such as ESC and Ctrl+C are not being handled correctly. The process does not respond to these events as expected.

Expected Behavior

• Ctrl+C should interrupt the current operation or cancel the running process.
• ESC should cancel/abort the current input or ongoing task.

Actual Behavior

• Neither ESC nor Ctrl+C produce any effect.
• The process continues running without acknowledging the keyboard signals.

Error Messages/Logs

NA

Steps to Reproduce

1. Open the VSCode integrated terminal.
2. Run claude to start Claude Code.
3. During an active session or while a response is being generated, press ESC or Ctrl+C.

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.83

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

• Editor: Visual Studio Code
• Terminal: VSCode integrated terminal (CLI)
• OS: Windows 10

[xieincz]

/ Also unable to input

[lupoinvesting]

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

[myniqx]

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

[yurukusa]

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).

[ashokvc]

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

[DevendraTomar]

@ashokvc this works , thanks for sharing