[BUG] Claude Code in VSCode CLI does not respond to ESC and Ctrl+C events
Resolved 💬 10 comments Opened Mar 25, 2026 by DevendraTomar Closed Apr 19, 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 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+Cshould interrupt the current operation or cancel the running process.ESCshould cancel/abort the current input or ongoing task.
Actual Behavior
- Neither
ESCnorCtrl+Cproduce any effect. - The process continues running without acknowledging the keyboard signals.
Error Messages/Logs
NA
Steps to Reproduce
- Open the VSCode integrated terminal.
- Run
claudeto start Claude Code. - During an active session or while a response is being generated, press
ESCorCtrl+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
This issue has 10 comments on GitHub. Read the full discussion on GitHub ↗