Cowork: remote-devices file bridge disconnects repeatedly, including mid-operation

Summary

In the Claude desktop app (Cowork mode), the remote-devices file bridge (device_stage_files / device_bash / device_commit_files) disconnects intermittently — including mid-operation — and does not auto-recover within the session, even after the desktop app reports the device as reconnected.

Environment

• Product: Claude desktop app — Cowork mode, remote-devices file bridge
• Device: khairuls-mac-studio-local (macOS, arm64)
• OS: macOS 26.5.2 (build 25F84), Darwin kernel 25.5.0, arm64
• appVersion: 1.20186.1
• electronVersion: 42.5.1
• nodeVersion: 24.17.0
• Connected folder: .../Khairulverse/Calendar/B&C Command Center/Bimoli Project Management
• Date observed: 2026-07-14, timezone Asia/Jakarta

What happens

The remote-devices bridge drops intermittently and does not auto-recover within the session. In one working session it:

1. Staged files fine
2. Committed handoff files
3. Performed a rename

…then the MCP server disconnected. It reconnected once (get_device_info succeeded), then dropped again mid-operation during device_stage_files with:

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

Multiple reconnect attempts over ~several minutes failed. Notably, get_device_info intermittently succeeded while device_stage_files failed in the same window — suggesting a partial/inconsistent bridge state rather than a clean disconnect.

Impact

Blocked from reading two files staged from the connected folder. Had to fall back to manually pasting / dragging the files into chat.

Steps to reproduce

1. Connect a folder in Cowork.
2. Run a series of device_stage_files / device_bash / device_commit_files calls.
3. The bridge disconnects intermittently and stays down within the session even after the desktop app reports the device reconnected.

Expected behavior

The bridge should either stay connected for the duration of a session, or auto-recover cleanly so that all remote-device tools (not just get_device_info) work again after a reported reconnect.