[BUG] Terminal input stops working after re-entering Vim mode in Claude Code

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?

I updated Claude Code to the latest version and I’m using the integrated terminal with Vim mode enabled.

When Vim mode is enabled, after I enter the Claude interactive session (i.e., open Claude from the terminal), I can no longer type in the terminal. Keyboard input doesn’t register, and I’m unable to enter any prompts or commands, making the terminal unusable.

Installation method: Upgraded via winget

I reproduced this behavior on two different Windows machines and observed the same issue in both environments.

On a freshly installed Windows system, I initially did not enable Vim mode and was able to enter prompts normally in the Claude terminal. After enabling Vim mode and opening the Claude interactive session again, the same problem occurred — terminal input stopped working and I was no longer able to enter prompts.

This suggests the issue is consistently triggered when Vim mode is enabled rather than being specific to a single machine or configuration.

What Should Happen?

Terminal input should remain functional when Vim mode is enabled. I should be able to enter prompts and commands normally after opening the Claude interactive session.

Error Messages/Logs

Steps to Reproduce

.

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

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

_No response_