CLI stops streaming output, requires Enter key to check if alive

Description

The Claude Code CLI intermittently stops streaming output (the spinner stops spinning) with no indication of whether it is still working or has hung. The only way to determine if the process is alive is to press Enter, which then either resumes output or confirms it's dead.

This happens mid-conversation during normal operation — not during any specific command or heavy workload. There's no error message or visual indicator that anything has gone wrong.

Steps to Reproduce

1. Start a Claude Code session
2. Work normally (reading files, making edits, running commands)
3. At some point the spinner/output simply freezes
4. Press Enter — output either resumes or the session is confirmed dead

Expected Behavior

• The CLI should continuously show a spinner or progress indicator while working
• If the connection drops or the process hangs, there should be a visible timeout/error message
• The user should never have to press Enter just to check if the CLI is still alive

Environment

• OS: Windows 11 Home 10.0.26200
• Shell: bash (Git Bash)
• Model: claude-opus-4-6

Impact

This is disruptive during long work sessions. You can't tell if Claude is thinking (and you should wait) or if something broke (and you need to restart). It creates uncertainty about whether work is being lost.