claude agents: ESC key non-functional in agents view — stuck state survives terminal restart, requires taskkill
Environment
- Claude Code version: 2.1.142 (latest)
- OS: Windows 11
- Terminal: VS Code integrated terminal (Command Prompt)
Steps to reproduce
- Run
claude agents - Select "Create new agent" to enter the creation wizard
- Press ESC to cancel — the UI displays "Esc to close" as a hint
Expected behavior
ESC closes the agents view / wizard and returns to the normal CLI prompt.
Actual behavior
ESC does nothing. The UI shows "Esc to close" but the hint is non-functional. The stuck state survives terminal restarts — reopening claude agents in a new terminal session resumes in the same frozen state (screenshot shows "Running" tab focused, "Esc to close" hint visible, no input accepted). The only recovery is taskkill /F /IM claude.exe to kill the underlying background process.
Screenshot
ESC key non-functional — Running tab stuck, Esc to close hint shown but ignored
<img width="379" height="89" alt="Image" src="https://github.com/user-attachments/assets/f018570c-c5d5-4b5d-ac8c-4b57c1176082" />
(screenshot shows "Running" tab highlighted, "No subagents are currently running", "Esc to close" hint visible — ESC has no effect)
Notes
- Reproduces without completing agent creation — entering the wizard is sufficient to trigger the stuck state
- The "Running" tab shows "No subagents are currently running" in the persistent stuck state, suggesting the wizard left a background process running
- The fact that
claude agentsresumes into the same stuck state after terminal restart confirms a background process is left alive and holding state - Related to #7208 but distinct: that issue requires completing agent creation first and does not mention state persistence across terminal restarts
taskkill /F /IM claude.exeis the only known recovery
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗