Summary
On 2.1.143, detaching from an attached session inside claude agents via ← leaves the entire terminal completely unresponsive on Windows. No keystroke (arrow keys, Enter, Space, Esc, Ctrl+C, Ctrl+Z, Ctrl+Break) is accepted. The only recovery is closing the Windows Terminal tab.
This is distinct from #59750 (broken render + dead input from cold claude agents launch) in that the agent view opens, renders, and accepts input normally until the attach → detach cycle is performed. After that, the terminal is dead.
Likely related to the 2.1.143 fix:
Fixed: on Windows, pressing ← in claude agents while a response was streaming could leave the agents list unresponsive to all input
The streaming-specific fix appears not to cover the more general detach path — the bug now reproduces deterministically regardless of whether a response is in flight.
Repro
claude agents opens cleanly with at least one running background session in the list.- Select a session and press
Enter (or →) to attach. The session takes over the terminal normally.
- On an empty prompt, press
← to detach back to the table.
- Agent view repaints, but the input loop is dead. No key produces any response.
- Terminal tab must be killed.
Also tried Ctrl+Z (documented as the immediate-detach fallback in the docs) — same hang.
Environment
- Claude Code: 2.1.143 (native installer,
~/.local/bin/claude.exe, FileVersion 2.1.143.0, ~219 MB Bun binary)
- OS: Windows 11 Pro, build 26200
- Terminal: Windows Terminal 1.24.11321.0
- Shell: PowerShell 7.6.1 (pwsh)
- Hardware: AMD Ryzen 9 7950X3D, 128 GB RAM, Radeon RX 7900 XTX (drivers current)
- Daemon: healthy (
claude daemon status reports control.sock reachable, 1 bg worker, no errors)
Same setup on Linux (SSH)
I tested the same workflow on a Linux box (Arx, my home server) over SSH — no freeze. Confirms this is Windows / Windows Terminal-specific, not an issue with my account or background sessions themselves.
Workaround
Downgrading clears it:
2.1.142 works reliably for me — agent view attach/detach is fluid, no hang. Stays clean through repeated cycles.
Related
Happy to provide logs (~/.claude/daemon.log, a recording, anything else useful) — just let me know what's needed.
Summary
On 2.1.143, detaching from an attached session inside
claude agentsvia←leaves the entire terminal completely unresponsive on Windows. No keystroke (arrow keys,Enter,Space,Esc,Ctrl+C,Ctrl+Z,Ctrl+Break) is accepted. The only recovery is closing the Windows Terminal tab.This is distinct from #59750 (broken render + dead input from cold
claude agentslaunch) in that the agent view opens, renders, and accepts input normally until the attach → detach cycle is performed. After that, the terminal is dead.Likely related to the 2.1.143 fix:
The streaming-specific fix appears not to cover the more general detach path — the bug now reproduces deterministically regardless of whether a response is in flight.
Repro
claude agentsopens cleanly with at least one running background session in the list.Enter(or→) to attach. The session takes over the terminal normally.←to detach back to the table.Also tried
Ctrl+Z(documented as the immediate-detach fallback in the docs) — same hang.Environment
~/.local/bin/claude.exe, FileVersion 2.1.143.0, ~219 MB Bun binary)claude daemon statusreports control.sock reachable, 1 bg worker, no errors)Same setup on Linux (SSH)
I tested the same workflow on a Linux box (Arx, my home server) over SSH — no freeze. Confirms this is Windows / Windows Terminal-specific, not an issue with my account or background sessions themselves.
Workaround
Downgrading clears it:
2.1.142 works reliably for me — agent view attach/detach is fluid, no hang. Stays clean through repeated cycles.
Related
claude agentslaunch (PS 5.1 + 7 both affected per my comment there)Happy to provide logs (
~/.claude/daemon.log, a recording, anything else useful) — just let me know what's needed.