[BUG] Hitting ESC to exit /bashes also aborts active task

Environment

• Platform (select one):
• [x] Anthropic API
• [ ] AWS Bedrock
• [ ] Google Vertex AI
• [ ] Other: <!-- specify -->
• Claude CLI version: v24.6.0
• Operating System: Windows 11
• Terminal: Windows Terminal

Bug Description

If I run /bashes while claude code is "thinking" (e.g., ✻ Pouncing… (esc to interrupt)) and /bashes shows that there are No background shells currently running, it says I should hit ESC To exit /bashes but when I do, it also interrupts the ongoing task.

Expected Behavior

Hitting ESC once should exit the slash command without interrupting claude code.

Actual Behavior

ESC exits the slash command and interrupts claude code.