claude agents: pressing back arrow while response is generating freezes CLI completely
Status Fixed / completed
Reported on v2.1.141
Maintainer reply ✓ Yes — claude[bot]
Activity 9 comments · opened May 14, 2026 · closed May 16, 2026
💡 Likely answer: A maintainer (claude[bot], contributor)
responded on this thread — see the highlighted reply below.
Environment
- Claude Code version: 2.1.141 (latest)
- OS: Windows 11
- Terminal: VS Code integrated terminal (Command Prompt)
Steps to reproduce
- Run
claude agents - Enter any existing conversation
- Send a message and wait for the agent to start generating a response
- While the response is still streaming/generating, press the back arrow to return to the agents list
Expected behavior
Navigation back to the agents list works cleanly, or is blocked with a prompt until generation completes.
Actual behavior
The CLI becomes completely unresponsive — no keyboard input is accepted, no navigation works. The only recovery is to kill the terminal session.
Notes
- Specific to the
claude agentscommand — does not reproduce in normal Claude Code chat - The freeze is triggered specifically by navigating away mid-generation via the back arrow
- Distinct from general CLI unresponsiveness issues (#24478, #25286) which lack this specific trigger
- No screenshot provided as the frozen state shows no visible indicator — the terminal simply stops responding to all input
9 Comments
This issue was fixed as of version 2.1.143.
No, it wasn't.
I still see that agents view getting stuck in a hellish manner
still not working in windows..
still having the same problem,
Confirming this still reproduces on v2.1.143 despite the "fixed" comment.
Environment
2.1.143Repro (broader than the original report)
The freeze is not limited to mid-generation. It reproduces even when the chat is fully idle:
claude agents→ attach to any session←(left arrow) to detach → terminal becomes completely unresponsiveDocumented workaround also broken
The
Ctrl+Zdetach shortcut mentioned in the Agent View docs produces the same freeze — neither input path recovers. Only killing the terminal works.Requesting reopen — the v2.1.143 fix doesn't cover this path on Windows.
No it was not, this is broken
It is a very very annoying issue... I have stopped using agents view completely...
it is a big distraction.
It is even more disappointing to see that they keep closing it without realizing the bad user experience they are offering
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.