Isolated Linux workspace (device-bash) fails to start on linked Windows desktop

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?

The isolated Linux environment (device-bash / Cowork VM workspace) fails to start on my linked Windows desktop. Every attempt to run a command through it fails immediately with a "Workspace unavailable" error. File-bridge operations (listing, staging, and committing files) on the same linked device work fine — only command execution via the isolated Linux workspace is broken.

What Should Happen?

Commands run via the device-bash tool should execute in the isolated Linux environment on the linked device, the same as file-bridge operations already do.

Error Messages/Logs

Workspace unavailable. The isolated Linux environment on this device failed to start. Use device_stage_files / device_commit_files instead.

Steps to Reproduce

1. Link a Cowork session to a Windows desktop, with one or more folders connected.
2. Attempt any command through the device-bash tool, e.g. a simple curl or echo.
3. Expected: command executes in the isolated Linux environment on that device.
4. Actual: immediate "Workspace unavailable" error, on every attempt, across multiple sessions over multiple days.

Claude Model

Not sure / Multiple models

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

1.52386.0 (1003ca)

Platform

Other

Operating System

Windows

Terminal/Shell

Other

Additional Information

This matches existing reports: anthropics/claude-code#55649, anthropics/claude-code#56145, anthropics/claude-code#57968, anthropics/claude-code#56542, anthropics/claude-code#92008

One of those threads (#56145) traced a related root cause to the workspace's working-directory path format changing after an app update (cloud /sessions/.../mnt/ path vs. Windows local path), breaking cloud workspace provisioning.