›_ Claude Code Issues
Claude Code Issues / #59899

[BUG] Agents view becomes unresponsive after navigating back with left arrow key on Windows 11 PowerShell

Resolved 💬 16 comments Opened May 17, 2026 by MaybeJustLikeThis Closed May 19, 2026
💡 Likely answer: A maintainer (claude[bot], contributor) responded on this thread — see the highlighted reply below.

What's Wrong?

When using the Claude agents view in Claude Code v2.1.143 on Windows 11 PowerShell:

  1. After entering the agents view directly via Claude agents and dispatching a task
  2. Once inside a specific agent's detailed interface
  3. Pressing the left arrow key to navigate back to the main agents overview
  4. After returning to the main view, the entire TUI becomes completely unresponsive — no keyboard input is accepted, arrow keys do nothing, and no interactions work
  5. The only way out is to force-close the terminal window

Additionally:

  • Ctrl+C also cannot exit the agents view when inside it — pressing Ctrl+C brings back the main page but the UI is frozen and unresponsive, same as the left arrow key scenario
  • No error messages or stack traces are shown — the TUI simply stops responding to all input

What Should Happen?

  • Pressing the left arrow key should smoothly navigate back from a specific agent view to the main agents overview without freezing
  • Ctrl+C should reliably exit the agents view and return to the main chat interface
  • The TUI should remain responsive after navigation between views

Steps to Reproduce

  1. Launch Claude Code on Windows 11 PowerShell:

``
claude agents
``

  1. Enter the agents view directly via the Claude agents feature
  2. Dispatch a task to one of the agents
  3. Enter into a specific agent's detailed view
  4. Press the left arrow key to navigate back to the main agents overview
  5. Observe: the TUI becomes completely unresponsive

Alternatively:

  • From step 4, press Ctrl+C to exit the agents view — observe the same freeze on the main page

Environment

  • Claude Code Version: 2.1.143
  • OS: Windows 11 Home China (10.0.26200)
  • Terminal/Shell: PowerShell
  • Platform: Anthropic API
  • Model: Sonnet (default)
  • Regression: Not sure

Additional Information

The freeze happens consistently — 100% reproducible. When the freeze occurs, no error messages appear in the terminal. The cursor stops blinking, and the TUI appears visually correct but accepts no input whatsoever. The process must be terminated by closing the terminal window or killing the process via Task Manager.

View original on GitHub ↗

16 Comments

tomerpeled · 2 months ago

I'm encountering the same issue

davidpu770 · 2 months ago

same here

ilyam1234 · 2 months ago

same here

JinWooR · 2 months ago

same here

saarsg · 1 month ago

same

djarcadian · 1 month ago

Experiencing this issue too. Claude, Powershell, Windows 11 Pro all current and up to date.

Bash(claude --version)
⎿  2.1.143 (Claude Code)

● You're on Claude Code 2.1.143. Include that in the GitHub issue.

result: Installed version is Claude Code 2.1.143.

42logos · 1 month ago

Confirming repro on the same environment (Win 11 22631, PowerShell 5.1, Windows Terminal 1.24.11321.0, Claude Code 2.1.143). Same exact symptom: ← back from session detail → list view repaints fine but all input dead, including Ctrl+C in some sessions.

One additional data point that may help triage — the supervisor daemon log (~/.claude/daemon.log) shows a race where two daemons spawn within ~1s under this condition:

[2026-05-18T02:32:49.016Z] [supervisor] ─── daemon start ─── version=2.1.143 pid=12544 origin=transient
[2026-05-18T02:32:50.143Z] [bg] bg spawned aaf21448 (spare)
[2026-05-18T02:32:50.150Z] [supervisor] ─── daemon start ─── version=2.1.143 pid=23028 origin=transient
[2026-05-18T02:32:51.091Z] [supervisor] another daemon is already running (pid=12544, version=2.1.143, origin=transient; an on-demand daemon never displaces a running one). Stop it with `taskkill /PID 12544`, then retry.

Not certain this race is the root cause of the wedged input loop, but the timing correlates with TUI relaunches after the freeze. Also worth noting: there is no CLI escape hatch (claude agents is TUI-only, no --list/--stop subcommands), so when input dies the only recovery is killing the supervisor PID from daemon.status.json.

changminJ · 1 month ago

I’m seeing the same issue on Windows.

Environment:

  • Claude Code version: 2.1.143
  • OS: Windows 11 Education 26200
  • Terminal: Warp and Windows Terminal
  • Shell: PowerShell

Repro:

  1. Open agents view.
  2. Enter a background session.
  3. Press the left arrow key to return to the agents list.
  4. The TUI becomes unresponsive and all keyboard input is ignored.

The only reliable recovery is closing the terminal window.

Please fix this as soon as possible. This issue is blocking my normal workflow.

lizhouai · 1 month ago

I'm encountering the same issue in my Windows Git Bash.

cc0cc0cc · 1 month ago

same issue in my windows powershell7

TofiBot · 1 month ago

Same issue here, once I navigate into an agent and back out, the terminal becomes unresponsive.

Subodai-EVE · 1 month ago

Same issue when trying claude agents for the first time today. Also my mouse no longer scrolls the window it scrolls through previous input prompts..

Lesani · 1 month ago

same in vs code terminal on windows... does noone at Anthropic test features on systems other than linux?

claude[bot] contributor · 1 month ago

This is a duplicate of #59814, which was fixed as of version 2.1.144.

saarsg · 1 month ago

the "claude agents" view and the feature when allowed in config also messes with the powershell settings for what i noticed, when allowing agents view it messed up with scrolling using the mousewheel, instead it scrolled prompts on the message box. when toggled off for both config options and restarted the shell returned to normal functionality.

github-actions[bot] · 8 days ago

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.