claude-code icon indicating copy to clipboard operation
claude-code copied to clipboard

[BUG] UI hangs in 'accept edits' mode after streaming abort - WSL2

Open pentafive opened this issue 1 month ago • 1 comments

Preflight Checklist

  • [x] I have searched existing issues and this specific symptom hasn't been reported
  • [x] This is a single bug report
  • [x] I am using the latest version of Claude Code

What's Wrong?

After a streaming request was aborted (user interrupt), Claude Code entered an unrecoverable state where:

  1. UI shows "⏵⏵ accept edits on (shift+tab to cycle)" at bottom
  2. Keyboard input is completely ignored (Esc, y, n, Enter, Ctrl+C - nothing works)
  3. Session appears frozen but timer continues (showed 26s+)
  4. Only way to exit was closing terminal

What Should Happen?

After streaming abort, Claude should gracefully recover and return to accepting user input.

Error Messages/Logs

From debug log (~/.claude/debug/7f35a362-ab83-4b38-afb6-7a3915fcd666.txt):

2025-12-12T06:44:54.483Z [DEBUG] Streaming aborted by user: Request was aborted.
2025-12-12T06:44:54.483Z [ERROR] Error in non-streaming fallback: Request was aborted.
2025-12-12T06:44:54.484Z [ERROR] Error: Error: Request was aborted.
2025-12-12T06:44:54.485Z [ERROR] Error: Error: No assistant message found

Additional observations:

  • Multiple [SLOW OPERATION DETECTED] for PowerShell calls (~130-160ms)
  • Session continued processing after error but UI was frozen

Steps to Reproduce

  1. Start Claude Code session with active todo list
  2. During Bash tool execution awaiting permission, press Escape to interrupt
  3. Observe UI enters "accept edits" mode
  4. Attempt any keyboard input - nothing responds

Claude Model

Sonnet (default)

Is this a regression?

Unknown

Claude Code Version

2.0.67 (Claude Code)

Platform

Anthropic API

Operating System

WSL2 (Ubuntu) on Windows 11

Terminal/Shell

Windows Terminal / zsh

Additional Information

Session ID: 7f35a362-ab83-4b38-afb6-7a3915fcd666 Project: PentaTemplateGemini-cli

Related but distinct from #10484 - same error but different trigger (user abort vs @ folder) and symptom (UI hang vs crash).

pentafive avatar Dec 12 '25 07:12 pentafive