remote session / stuck spinner / no secrets

Claude Code “still running” is a state split, not a reinstall ritual.

Claude Code v2.1.179 fixed several real stuck-session failure modes: mid-stream connection drops that left the spinner at running tool, WSL2 mouse-wheel regression, huge sandbox glob descriptions making Linux sessions unusable, and remote background tasks appearing stuck. This packet separates those paths before anyone deletes auth or pastes secrets.

Source signal

Verified against Anthropic's public GitHub release notes for v2.1.179: partial responses are preserved on connection drops, WSL2 scrolling was fixed, large denyRead/allowRead globs were fixed, and remote background tasks no longer appear stuck as “still running” between turns.

Build the packet Release receipt

Split the failure before touching auth.

01

Status and version.

Record Claude Status and claude --version. A just-updated CLI and a just-resolved service incident can both explain weird remote state.

02

Remote vs normal shell.

Run one harmless prompt in the remote/IDE surface and one normal terminal. If only the remote surface hangs, debug wrapper/session/plugin state first.

03

Sandbox scope.

Large denyRead/allowRead globs can poison the tool description path. Note the shape without dumping private paths.

04

Background task proof.

Capture whether a task is actually running, only displayed as running, or missing partial output after a connection drop. Those are different bugs.

Copyable remote-stuck triage

Build the no-secret stuck-session packet.

Environment Claude Code version / install Main symptom Where it happens Service/status check Sandbox / file-scope note Plugins / remote-session note Small reproduction Boundary / help needed

Email Mikael

Output preview

Safe to share publicly after you redact project names and private host/path details. Never include tokens, cookies, app passwords, API keys, or OAuth codes.