[BUG] Claude Code Versions 2.1.83 and 2.1.84 are not correctly taking keyboard input. CLAUDE CODE IS BRICKED!!!

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?

Bug Report: Keyboard Input Regressions in VS Code Terminal (v2.1.83-2.1.84)

Environment

• OS: Windows 10

• WSL: WSL2

• Terminal: VS Code integrated terminal (latest)

• Claude Code: 2.1.83, 2.1.84

Problem Summary

Multiple keyboard input issues specific to VS Code integrated terminal in Claude Code versions 2.1.83 and 2.1.84.

Issue 1: Critical Input Failure — PARTIALLY RESOLVED

Basic keys (Space, Backspace, Enter, Control) were non-functional. Fixed by updating VS Code to latest version.

Issue 2: Shift+Tab Mode Cycling — BROKEN

Expected: Shift+Tab cycles through Normal → Auto-Accept → Plan Mode

Actual: No response, mode indicator does not appear, input completely ignored

Issue 3: Escape Key — BROKEN

Expected: Escape stops running agent or clears current input

Actual: No response, agent continues running, input not cleared

Verification

• /plan slash command: works

• Ctrl+C to stop agent: works

• Standard Ubuntu terminal (WSL): Shift+Tab and Escape work correctly

• VS Code integrated terminal: Shift+Tab and Escape broken

Steps to Reproduce

1. Install Claude Code 2.1.84 in WSL2 on Windows 10

1. Open VS Code integrated terminal (latest version)

1. Run claude

1. Press Shift+Tab to cycle modes — no response

1. Start an agent task, press Escape to stop — no response

1. Type in input box, press Escape to clear — no response

Regression Confirmation

• 2.1.82 and earlier: all keyboard functions work in VS Code terminal

• 2.1.83-84: Shift+Tab and Escape broken in VS Code terminal only

Workarounds

• Use /plan slash command to enter plan mode

• Use Ctrl+C to stop running agent

• No workaround for clearing input box

System Info

uname -a: Linux DESKTOP-EQ55Q8H 6.6.87.1-microsoft-standard-WSL2 #1 SMP PREEMPT_DYNAMIC Mon Apr 21 17:08:54 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux

Claude Code: 2.1.84

What Should Happen?

Expected Behavior

All keyboard input functions normally as in previous versions.

Actual Behavior

• Letter keys: ✅ work

• Space bar: ❌ no spacing

• Backspace: ❌ no deletion

• Enter: ❌ cannot submit prompt

• Control combinations: ❌ not recognized

Regression Confirmation

• ✅ 2.1.82 and earlier: works correctly

• ❌ 2.1.83: broken

• ❌ 2.1.84: broken

Currently forced to downgrade to continue using Claude Code.

Error Messages/Logs

Steps to Reproduce

• Install Claude Code 2.1.84 in WSL2 on Windows 10

• Open VS Code integrated terminal (latest version)

• Run claude

• Press Shift+Tab to cycle modes — no response

• Start an agent task, press Escape to stop — no response

• Type in input box, press Escape to clear — no response

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.84, 2.1.83

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

VS Code integrated terminal

Additional Information

This has disrupted my workflow and taken hours of my time away, paired with Claude's recent extreme degradation in performance and honestly I want my money back for this month of March! I have never wanted to leave Anthropic subscription before in a serious way until this month! The performance of Opus and sonnet has went down EXTREMELY this month specifically Opus with the 1m context window is a worse model than Sonnet 3.5 on almost all daily tasks, and this is with clean and clear context window, there is something wrong with this model! I cannot describe every situation in which it has been failing but its surprisingly stupid stuff that no joke sonnet 3.5 would have done correctly in 1/4 the time.

So this needs to be fixed and soon! I am dead serious, I want my money back for this month if you want to keep me as a customer! GPT 5.4 is too good to be allowing problems like this over at Anthropic! You're going to start losing people, the gap isn't that large anymore!