claude-code - 💡(How to fix) Fix [BUG] Agents view becomes unresponsive after navigating back with left arrow key on Windows 11 PowerShell

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

2. Enter the agents view directly via the Claude agents feature
3. Dispatch a task to one of the agents
4. Enter into a specific agent's detailed view
5. Press the left arrow key to navigate back to the main agents overview
6. 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.