[BUG] /mcp menu freezes and becomes unresponsive when using --resume in WSL2
Status Fixed / completed
Reported on v2.1.119
Maintainer reply ✓ Yes — mhegazy
Workaround ✓ Mentioned in description ↑
Activity 6 comments · opened Apr 24, 2026 · closed Apr 28, 2026
💡 Likely answer: A maintainer (mhegazy, contributor)
responded on this thread — see the highlighted reply below.
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 launching Claude Code with --resume flag, the /mcp menu opens but becomes completely unresponsive to keyboard input (arrow keys, Enter, Esc). The UI renders correctly but no input is processed.
What Should Happen?
/mcp menu should be navigable with arrow keys and respond to Enter/Esc normally.
Error Messages/Logs
nothing
Steps to Reproduce
- Start Claude Code normally:
claude - Exit the session
- Resume with:
claude --resume - Type
/mcp - Menu opens but does not respond to any key presses
Claude Model
Sonnet (default)
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.1.119 (Claude Code)
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
WSL (Windows Subsystem for Linux)
Additional Information
Actual Behavior
Menu renders but is completely frozen. No keyboard input is processed. The issue does not occur when starting a fresh session with claude (without --resume).
Workaround
Launching with TERM=xterm-256color claude --resume does not help.
Fresh claude sessions work fine — /mcp is responsive.
Additional Context
- MCP servers configured: claude.ai Gmail, Google Calendar, Google Drive (all disabled)
- Issue persists regardless of which project is resumed
- Tested with multiple projects — all exhibit the same behavior
6 Comments
Found 2 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Can confirm this on native Win 10 as well, not running on WSL2.
/mcpand/resumeare hard locked after messing with a few mcp settings but _even after reverting them_. Creating a brand new conversation suddenly it's okay again. This is a very frustrating one.Also: Disabled additional MCP servers with
ENABLE_CLAUDEAI_MCP_SERVERS=falsein env settings, then set up a small toy mcp server and verified working in a new session. Upon resuming the old session with those same verified working settings then in place,/rewindand/mcpboth still hard lock. It's some kind of session and/or settings poison.Process gets stuck/frozen but at 0% CPU usage, ctrl+c won't kill it, have to taskkill.
Confirming /rewind and /mcp locking on WSL2 Windows 11. This is a regression.
I'm seeing this too on Debian:
Debian 6.12.74-2 (2026-03-08) aarch64 GNU/Linuxwith Claude Code 2.1.119. Regular usage of Claude Code seems to work fine but the/mcpcommand freezes the TUI in an unrecoverable way.Pretty minimal config on this VM, here's the MCP section, lemme know if more of the file would be useful:
Fix should be in v2.1.120.
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.