Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [Bug] Linux sandbox (bash) permanently fails — cloud workspace not provisioning for Windows Cowork sessions (6+ sessions affected) [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#56145•Fetched 2026-05-05 05:57:01
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
chatkecerdasanchatkecerdasan
Participants
chatkecerdasanchatkecerdasangithub-actions[bot]github-actions[bot]
Timeline (top)
labeled ×4commented ×1

Error Message

Error Messages/Logs

Code Example

Workspace unavailable. The isolated Linux environment failed to start. You can still use file tools directly.
RAW_BUFFERClick to expand / collapse

Preflight Checklist

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

What's Wrong?

The isolated Linux sandbox fails to start in every Cowork session on Windows. Every bash call returns immediately: "Workspace unavailable. The isolated Linux environment failed to start." This has persisted across 6+ consecutive sessions over multiple weeks with no recovery.

What Should Happen?

The Linux sandbox should start successfully when a Cowork session begins, allowing Claude to execute bash commands, run Python scripts, and perform shell operations. Sessions should have cwd set to /sessions/<name>/mnt/ as was the case before the April 2026 app update.

Error Messages/Logs

Workspace unavailable. The isolated Linux environment failed to start. You can still use file tools directly.

Steps to Reproduce

  1. Open Claude Cowork desktop app on Windows (Microsoft Store version)
  2. Start any new conversation session
  3. Ask Claude to perform any task requiring bash/shell/Python execution
  4. Observe Claude calls mcp__workspace__bash
  5. Result: immediate failure — "Workspace unavailable. The isolated Linux environment failed to start."
  6. Failure is instant with no retry, no startup delay, sandbox never becomes available

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

Version before Claude_1.5354.0.0_x64 (last working sessions before 29 April 2026)

Claude Code Version

Claude Cowork 1.5354.0.0 (Microsoft Store, not Claude Code CLI)

Platform

Other

Operating System

Windows

Terminal/Shell

Other

Additional Information

IMPORTANT: This bug is in Claude Cowork (desktop app), not Claude Code CLI.

KEY FINDINGS:

  1. Session cwd format changed after app update:

    • BEFORE (working): /sessions/<name>/mnt/
    • AFTER (broken): C:\Users\NKB.PRBNS.2111.0025\AppData\Roaming\Claude\local-agent-mode-sessions...

  2. No local sandbox exists — installation inspection confirms: Path: C:\Program Files\WindowsApps\Claude_1.5354.0.0_x64__pzs8sxrjxfjjc Contents: app/ and assets/ folders only NO WSL, Docker, container runtime, or sandbox binary found %AppData%\Claude does not exist on this machine Windows Event Viewer shows ZERO Claude entries

    Conclusion: Linux workspace is a REMOTE/CLOUD service. The failure is server-side — nothing to fix locally.

  3. Affected sessions (6 confirmed): local_7922f495, local_b8a680cb, local_83d21f4b, local_b2a16a18, local_b98a6bbc, local_b5a3f165

  4. Working sessions (before update): local_749d8921, local_b55ec58e, local_9f5155d2, local_95848dc1

  5. Anthropic Support Conversation ID: 215474175581735

  6. App update date: 29 April 2026 — correlates exactly with regression start

extent analysis

TL;DR

The issue is likely due to a server-side problem with the remote Linux workspace service, and the user should contact Anthropic Support for further assistance.

Guidance

  • The error message "Workspace unavailable. The isolated Linux environment failed to start" suggests a problem with the Linux sandbox, but the investigation reveals that the issue is server-side, related to the remote Linux workspace service.
  • The change in session cwd format after the app update may be related to the issue, but it's not a local problem that can be fixed by the user.
  • The user has already confirmed that there is no local sandbox or container runtime installed, and the Windows Event Viewer shows no Claude entries, supporting the conclusion that the issue is server-side.
  • The user should refer to the Anthropic Support Conversation ID: 215474175581735 for further assistance and potential resolution.

Notes

The issue is specific to the Claude Cowork desktop app on Windows, and the user is already using the latest version. The problem started after the app update on April 29, 2026, and has persisted across multiple sessions.

Recommendation

Apply workaround: Contact Anthropic Support for further assistance, as the issue is likely related to their remote Linux workspace service.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#installation#container setup#orchestration issue#cache issue#memory leak

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [Bug] Linux sandbox (bash) permanently fails — cloud workspace not provisioning for Windows Cowork sessions (6+ sessions affected) [1 comments, 2 participants]