Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Slash-command submenus hard-freeze TUI on native Windows / PowerShell 7 (mirrors WSL2 bug #52882) [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#54095•Fetched 2026-04-28 06:39:23
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
GPLJRivettGPLJRivett
Participants
github-actions[bot]github-actions[bot]GPLJRivettGPLJRivett
Timeline (top)
labeled ×4commented ×1

Root Cause

Preflight Checklist

  • Searched existing issues. Closest: #52882 (same symptom on WSL2). Filing a separate issue because root environment is different (native Windows install, not WSL).
  • Single bug report.
  • Latest version of Claude Code.

Fix Action

Fix / Workaround

Adding --debug at startup makes the same submenus respond normally — same workaround as #52882.

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • Searched existing issues. Closest: #52882 (same symptom on WSL2). Filing a separate issue because root environment is different (native Windows install, not WSL).
  • Single bug report.
  • Latest version of Claude Code.

What's Wrong?

On Claude Code 2.1.119, native Windows install (C:\Users\<me>\.local\bin\claude.exe), running directly in PowerShell 7.5.5 Core inside Windows Terminal: any slash command that mounts an interactive selection submenu (/mcp, /agents, etc.) hard-freezes the TUI. The submenu paints, but Enter / Esc / arrow keys / Ctrl-C are all unresponsive. Only recovery is killing the process from another terminal (Get-Process claude | Stop-Process -Force).

Slash commands that just print text (e.g. /mcp when no servers are configured, /model confirming the current model) work fine — the freeze hits specifically when an interactive picker is rendered.

This is the same symptom and Heisenbug class described in #52882 — the OP there diagnosed it as a React/Ink render loop on WSL2, only reproducible without --debug. Confirming it also reproduces on native Windows outside WSL, which rules out a WSL/pty-specific cause and points more squarely at the TUI library or the Bun runtime's interaction with process.stdin raw mode on Windows ConsoleHost.

Environment

  • Claude Code 2.1.119 (latest)
  • Install method: native (Windows installer to ~/.local/bin/claude.exe)
  • Runtime: bundled (no separate node/bun in PATH)
  • Windows 11 Pro 10.0.26200
  • PowerShell 7.5.5 Core (pwsh), ConsoleHost
  • Windows Terminal (WT_SESSION set)

No WSL, no Cygwin, no MSYS, no Git Bash — pure Win32 PowerShell.

What Should Happen?

Interactive submenus should respond to Enter / Esc / arrow keys / Ctrl-C on native Windows the same way they do under --debug (which presumably works around the bug here too, same as on WSL2).

Steps to Reproduce

  1. Native Windows 11, install Claude Code 2.1.119 via the Windows installer.
  2. Open Windows Terminal → PowerShell 7 tab.
  3. claude (no --debug).
  4. Type /mcp (with at least one MCP server configured) or /agents or any slash command that opens a selection submenu.
  5. Submenu paints. All keyboard input is silently swallowed. Process must be killed from outside.

Adding --debug at startup makes the same submenus respond normally — same workaround as #52882.

Cross-reference

#52882 — same bug on WSL2. Likely same root cause; this report broadens platform coverage to native Windows.

extent analysis

TL;DR

Running Claude Code with the --debug flag may temporarily resolve the issue of interactive submenus freezing on native Windows.

Guidance

  • Verify that the issue is specific to interactive submenus by testing slash commands that only print text, such as /mcp with no servers configured or /model.
  • Try running Claude Code with the --debug flag to see if it works around the bug, as it did in the similar issue #52882.
  • Test the issue in different environments, such as different versions of Windows or PowerShell, to determine if the issue is specific to the current setup.
  • Consider investigating the TUI library or the Bun runtime's interaction with process.stdin raw mode on Windows ConsoleHost, as these may be contributing to the issue.

Notes

The issue may be related to a React/Ink render loop, as suggested in #52882, but further investigation is needed to confirm this.

Recommendation

Apply the workaround by running Claude Code with the --debug flag, as this has been shown to resolve the issue in similar cases.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#latency issue#model loading#dependency error#configuration error#environment variable

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] Slash-command submenus hard-freeze TUI on native Windows / PowerShell 7 (mirrors WSL2 bug #52882) [1 comments, 2 participants]