Claude Code on Windows hit 18-minute device handshake failures, surviving reboot and app update
obrienatimothy-sketch · ghdev · 2026-09-25
A user filed a detailed bug report on anthropics/claude-code: the Windows desktop app's device bridge handshake went unanswered for 18 minutes. The WebSocket to wss://bridge.claudeusercontent.com opened and connect frames were sent, but no authenticated reply ever arrived — every attempt ended in handshake timeout. A full reboot plus an auto-updated app version changed nothing, and cloud sessions bound to the device failed entirely: the first shell command ran and exited 0 in the Cowork VM but its result was never delivered, timing out after 190 seconds. status.claude.com showed all systems operational throughout. The issue self-recovered with no client-side change.
The author reconstructed a timeline from %LOCALAPPDATA%\Claude\Logs\main.log: routine reconnect at 00:04, a new cloud session binding at 00:06, pong timeout resetting the link, then repeated 15-second handshake timeouts with backoff up to 30 seconds. They note this differs from prior issues #77385/#91111 (mid-session drops) and #84463 (reconnect storm): here the handshake itself is never acknowledged, sustained across a reboot and two app versions.
More from coding & agent
- Perplexity CEO shows agent building browser-playable 3D zombie shooter in hours with zero 3D assets — AravSrinivas · 2026-11-11
- The complete harness engineering roadmap: how OpenAI shipped ~1M lines with zero hand-written code — blaizedsouza · 2026-11-11
- Micius-Flash: 27B Multimodal Model for Hardware and Semiconductor Agents — zhiman-ai · 2026-11-11
- Viral 'the harness is the machine' thread touts unverified Claude Fable/Mythos 5.2 9-equation architecture — blaizedsouza · 2026-11-11
- Compaction creates a new failure mode for coding agents: critical bug details can vanish mid-fix — blaizedsouza · 2026-11-11
- What 40+ coding-agent harnesses do between your prompt and the model, dissected — blaizedsouza · 2026-11-11