[BUG] Input freezes on certain usage patterns in Windows

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?

Claude code freezes when using --resume and pressing 2x Esc immediately, or when using /powerup and picking one of the subitems.

WORKAROUND:

• Use traditional Command Prompt window instead of Windows Terminal. This is not 100% workaround, it can freeze in that as well, but it seems that the traditional command prompt window is much more likely to work.

What Should Happen?

Claude Code should never freeze this way and instead just continue working.

Error Messages/Logs

No error messages or logs as it freezes.

Steps to Reproduce

Steps to reproduce consistently, verified on two different computers:

1. Freshly install Claude Code and login (first-time ux)
2. Start up Claude Code in Windows Terminal. Use /powerup, select one of the sub-items. After that, Claude Code freezes, not accepting Esc, 2xEsc, Enter, Ctrl+C or any input.
3. Kill the frozen claude.exe
4. Try to open Claude Code to start a new session. /exit immediately.
5. Use claude --resume, select one of the previous sessions (doesn't matter which). Press 2x Esc immediately. Claude goes back to session resume selection. It again freezes in similar way as in step b.

Claude Model

Not sure / Multiple models

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.119

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

Environment:

• Windows 11 Pro.
• Claude Code version 2.1.119
• Windows Terminal 1.24.10921.0
• bash version: GNU bash, version 5.2.37(1)-release (x86_64-pc-msys), with env. var. CLAUDE_CODE_GIT_BASH_PATH=C:\...fullpath...\PortableGit\bin\bash.exe
• DISABLE_TELEMETRY=1 env. var. in use

Note:

• There seems to be many similar issues, but not exactly the same as this one, so I posted a new issue.