[BUG] Claude code 2.1.32 chat typing is not working every run, locking the chat

[TNYCL]

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?

On Windows, Claude Code CLI version 2.1.32, it is impossible to type any text in the chat input. The cursor appears but no characters are registered when pressing keys. This makes the tool completely unusable on Windows.

What Should Happen?

Users should be able to type text normally in the chat input field and submit prompts to Claude.

Error Messages/Logs

No error messages are shown. The input field simply does not accept any keyboard input. No logs are generated since the issue occurs at the input level.

Steps to Reproduce

Install Claude Code 2.1.32 on Windows
Launch claude in any terminal
Try to type any text in the chat input
Observe that no characters appear

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

2.1.19

Claude Code Version

2.1.32

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Warp

Additional Information

No response

[github-actions]

Found 3 possible duplicate issues:

1. [Bug] Interactive input frozen on startup on Windows 11 PowerShell (v2.1.30–2.1.32) #23460
2. [BUG] Windows Terminal input completely frozen starting from v2.1.30 (regression from v2.1.29) #23211
3. Keyboard input not working in v2.1.30 (Windows) #22906

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[SeanBackstrom]

same issue here. new, after updating to 2.1.32 -- cant type anything into claude at all.

[dysangelist-1]

I have this happening only when trying to launch Claude with claude --resume {session-id} - just starting claude always works fine for me (knock wood), but every time I try to resume a session (with the launch argument and value that Claude recommends using when it was last exited from), it hangs indefinitely, won't take input, CTRL-C won't kill it; I have to kill the shell (Git Bash running in Windows Terminal 1.23.13503.0) and start over in a new one, without using --resume.

Can't say how long it's been an issue - I only tried using the --resume argument for the first time today, but all three times I've tried it, it consistently starts up blocking all input. Happened on 2.1.31, and continued to happen on 2.1.32 after upgrading to it. So instead I just start it without args and ask it to read the previous plan and memory files it stored, and continue where we left off.

[github-actions]

Closing for now — inactive for too long. Please open a new issue if this is still relevant.

[github-actions]

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.