[BUG] VS Code extension stuck on Bash polling command after the shell exited; Stop button does nothing

Summary

In the VS Code extension, a session got permanently stuck showing a Bash polling command as "running". The orange Stop button had no effect. When I looked at the processes, the shell running the command was already gone, and the claude CLI process was idle. The UI was waiting for a tool result that never arrived.

This happens often when Claude runs long "wait for CI" style commands. Once it happens, the session is unusable until I reload the window or kill the process.

Environment

• Claude Code VS Code extension anthropic.claude-code-2.1.287-darwin-arm64
• macOS (Darwin 27.0.0), Apple Silicon

Command that was "running"

until ! gh pr checks 538 2>/dev/null | grep -qE '\bpending\b'; do sleep 30; done; gh pr checks 538 2>&1 | awk -F'\t' '{print $2"\t"$1}' | sort | uniq

What I observed

• The panel showed the command as still running, with no output and no end in sight.
• Clicking Stop did nothing.
• ps showed no until/sleep 30/gh pr checks shell anywhere on the machine.
• The extension's CLI process (.../native-binary/claude --output-format stream-json --verbose --input-format stream-json) was alive, idle (state S, 0% CPU), and its only children were MCP servers. It had no bash child.

So the command had already ended (or was never attached), but the tool result or completion never reached the UI, and the cancel path couldn't recover the turn.

Expected

• When the Bash tool's process exits, its result should be delivered and the turn should continue.
• Stop should always cancel the current turn and return control, even if a tool result is lost or the tool never finishes.

Workarounds

• Developer: Reload Window, or kill the extension's claude process and /resume.

Possibly related

• #98708: Stop didn't work in VS Code; only closing the window helped (different trigger: a runaway agent)
• #17333: VS Code extension hangs in the WebSocket/bidirectional communication (closed; possible regression)
• #80440: VS Code stuck "cooking" (closed)