[BUG] Cowork remote-devices bridge disconnects intermittently mid-session (Windows 11)

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

Summary
The Cowork remote-devices bridge between a cloud session and Claude Desktop disconnects
intermittently during a session, then reconnects on its own later. Error surfaced to the
session: "The device this session is bound to is not connected to the bridge."

Environment

• OS: Windows 11, win32/x64
• Claude Desktop appVersion: 1.40609.0
• electronVersion: 42.10.0
• nodeVersion: 24.18.1
• Device is a laptop, plugged in, not sleeping (screen/system sleep both set to 1 hour;

disconnects happen much sooner than that)

Symptom pattern

• Only Claude/Cowork loses connection — all other apps and windows on the machine stay

open and unaffected the entire time.

• Started suddenly at the end of a previous session; did not happen in sessions before that.
• Has now recurred across two separate sessions, both times during active use (browser

automation via the remote-devices computer-use tools), not while idle.

• One report from a device tester: the machine was untouched for about 5 minutes before

the drop.

• No data loss / no corrupted state observed when it happens — a retry a short time later

reconnects cleanly.

What I've ruled out

• Not a Windows Update issue — other apps and the network stay fully functional throughout.
• Not a sleep/power-plan issue — sleep timeouts are set to 1 hour; drops happen much faster,

and other apps keep running through the drop.

• "Keep awake" toggle in Claude Desktop: [was ON / OFF — fill in after you check

Settings in the app].

Possibly related open issues

• #77385 — remote-devices file bridge disconnects repeatedly, including mid-operation (macOS)
• #76054 — Desktop Bridge Failure after app update (Windows)
• #54378 — Cowork Dispatch persistently shows "Desktop appears offline" (Windows)
• #75416 — Dispatch stuck on "Asleep" despite desktop awake and app open (Windows 11)

Ask
Is this a known regression? What client-side logs would help pin down the cause?

What Should Happen?

The Cowork remote-devices bridge should stay connected for the duration of an active
session, or — if a brief network/OS hiccup does interrupt it — should detect the drop
and automatically reconnect within a few seconds without the in-progress task erroring
out or requiring a manual retry. It should not disconnect while the desktop app is open,
the computer is awake, and every other application on the machine remains connected and
responsive throughout.

Error Messages/Logs

Steps to Reproduce

1. Start a Cowork/Claude Desktop session on Windows with a folder connected via the

remote-devices bridge (device_bash / computer-use tools available).

1. Use the session actively for an extended period — in this case, driving browser

automation through the remote-devices computer-use tools (clicking, screenshots)
for several minutes.

1. At some point during active use (not while idle), a device tool call fails with:

"The device this session is bound to is not connected to the bridge."

1. Meanwhile, every other application and window on the machine (browser tabs, other

programs) remains open, connected, and responsive the entire time — only the
Claude session's bridge drops.

1. Retrying the tool call a short time later succeeds again without any user action

on the machine (no relaunch, no re-login) — the bridge reconnects on its own.

1. This is intermittent and not reliably reproducible on demand, but has now happened

in two separate sessions, both during active use rather than while idle.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

Claude Desktop appVersion 1.40609.0 (Cowork — not using the separate Claude Code CLI)

Platform

Other

Operating System

Windows

Terminal/Shell

Other

Additional Information

Platform: Using Cowork through a Claude.ai subscription (consumer product), not the
developer Anthropic API, AWS Bedrock, or Google Vertex AI directly.

Terminal/Shell: N/A — this bug is in the Cowork remote-devices bridge inside Claude
Desktop, not a CLI/terminal session. No terminal is involved in reproducing it.