@lpc123 @Al1nuX Its fixed. The new Claude Desktop (1.1.7714) changed its vm-client behavior.

Thanks for your report.

Claude Desktop's VM client correlates responses by id: const a = s.id ?? 0; const o = Ng.get(a);

Without id in the response, every reply was treated as orphaned (id=0 not in pending map), Promises never resolved, and startVM was never called — leaving Cowork stuck polling isGuestConnected indefinitely.

Fix: add ID field to Response struct and pass req.ID through WriteResponse() and WriteError() at all call sites.

@lpc123 thanks, i will immediately check and fix it.

The most recent upgrade: claude-code (2.1.72 → 2.1.80) claude-cowork-service (1.0.10 → 1.0.11) ← This is the key one claude-desktop-bin (1.1.5749 → 1.1.7714)

The claude-cowork-service package is what provides the VM/workspace functionality. The update seems to have broken compatibility with the new claude-desktop-bin version.

Looking at the logs:

No vm-bundle directory exists (it's empty) The app is trying to connect to https://a-api.anthropic.com/v1/m but it's being blocked by CSP The workspace never initializes because the VM bundle isn't being downloaded/created