claude-code - 💡(How to fix) Fix [BUG] claude agents TUI fully unresponsive on Windows Terminal — broken rendering + dead input loop (2.1.143)

Preflight Checklist

• I have searched existing issues and this hasn't been reported yet
• This is a single bug report (please file separate reports for different bugs)
• I am using the latest version of Claude Code

What's Wrong?

Running claude agents (added in 2.1.139) on Windows Terminal results in two compounding failures that make the agent view completely unrecoverable without killing the terminal:

1. TUI elements render in wrong vertical positions.

On initial launch, the header (Claude Code v2.1.143 / Opus 4.7 (1M context) · C:\Pipeline / 0 awaiting input · 1 working · 0 completed) and session row render, but the composer input region is missing entirely — only the shortcut footer (enter to open · space to reply · ctrl+x to delete · ? for shortcuts) is present, sitting where the input should be. The "Type a task below to dispatch a session" hint text is shown, but there is no input to type into.

After a session state change (the /projects session transitioned from working to Needs input for a Bash approval), the layout shifted further: the footer moved to the top of the visible area, the header info appeared below it, and the session row landed sandwiched between misplaced header text — see attached screenshots.

2. Keyboard input is completely dead.

None of the following had any effect once the TUI was in its corrupted state:

• Enter, Space, ? (documented shortcuts in the footer)
• Arrow keys (→, ←, ↑, ↓)
• Ctrl+C
• Ctrl+Break
• Mouse clicks on session rows

The only way to exit was closing the Windows Terminal tab/window entirely. The background /projects session was correctly recovered afterward via claude --resume.

What Should Happen?

• All TUI regions (header, session list, body hint, composer input, footer) render in their correct vertical positions on initial launch and persist across state changes.
• Documented keyboard shortcuts (Enter, Space, →, Ctrl+C) reach the input handler.
• At minimum, Ctrl+C always exits cleanly without requiring a terminal kill so users are never forced to kill the terminal window.

Error Messages/Logs

Steps to Reproduce

1. Open Windows Terminal (default profile: Windows PowerShell 5.1)
2. Have at least one existing claude session running in another worktree/directory (so agent view has a session to list)
3. Run claude agents
4. Observe: composer input region is missing on initial render — only header, session row, and footer present
5. Wait for any session to change state (e.g. request a permission approval)
6. Observe: TUI elements re-render in wrong vertical positions (footer moves to top, header moves to middle)
7. Attempt to press any documented key (Enter, Space, arrow keys, ?) — observe nothing happens
8. Attempt Ctrl+C / Ctrl+Break — observe nothing happens
9. Resort to closing the Windows Terminal window via the X button; the background session can then be recovered via claude --resume

Claude Model

Opus

Is this a regression?

No, this never worked

Last Working Version

No response

Claude Code Version

2.1.143 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

Environment details

• OS: Microsoft Windows 11 Pro 25H2 (build 26200.8457)
• Terminal: Windows Terminal 1.24.11321.0
• Shell: PowerShell 5.1.26100.8457 (Windows PowerShell, not PowerShell 7)
• Node: v26.1.0 / npm 11.8.0

Workarounds tried

• Resizing the Windows Terminal window — did not restore the input region. Made layout worse on second attempt (elements moved to new wrong positions instead of correct ones).
• Ctrl+L — no effect (no keyboard input reaches the process at all).
• Waiting for re-render after session state change — produced a different broken layout, did not restore functionality.
• Could not test /tui fullscreen renderer since input was dead and /tui is a slash command inside an attached session, not an agent view command.

Notes on shell

This was reproduced under Windows PowerShell 5.1 (the bundled, legacy shell), not PowerShell 7. The closely-related #58579 was filed against PowerShell 7.6.1 with similar rendering symptoms but did not report a wedged input loop, so the 5.1 vs 7.x distinction may be relevant for triage. Have not yet retested under pwsh (PowerShell 7) to determine whether the input-loop death is shell-specific or terminal-specific.

Severity rationale

This is a research preview feature, but the failure mode (unrecoverable wedge requiring terminal kill) is more severe than typical rendering issues — there is no in-app escape path. On Windows Terminal + Windows PowerShell (a common default Claude Code config on Windows), claude agents is currently unusable.

Related issues

• #58579 — /agents view lines stack/overlap on Windows Terminal (2.1.140) — same area (area:agent-view, platform:windows) but different failure mode. #58579 reports row overlap on the same line; this report is about elements being placed at wrong vertical positions AND complete input event loop death.
• #52410 — permission prompt render-loop on WT
• #19637 — long-standing Windows TUI overlap/garble since 2.1.3
• #16578 — status lines stacking instead of updating in place

Suggested labels

area:agent-view · area:tui · platform:windows · bug · has repro