[BUG] Cowork Linux sandbox fails to start — persistent for 24+ hours

Resolved 💬 2 comments Opened May 12, 2026 by kittipontheeramawan-jpg Closed Jun 12, 2026

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?

Environment: Claude Code (claude.ai/code), Cowork feature

Problem:
The Linux sandbox in Cowork fails to start and has been in this broken state for over 24 hours. Every attempt to run a skill (e.g., creating a Word document) returns the following error:

"Workspace ไม่พร้อมใช้งานตอนนี้ครับ (Linux sandbox ยังไม่ start ได้)"
(Translation: "Workspace is not ready for use right now — Linux sandbox couldn't start")

Steps to reproduce:

Open a Cowork session
Attempt to run any skill that requires the Linux sandbox (e.g., create a Word document)
Error appears immediately — sandbox never becomes ready
Expected behavior: Sandbox starts within a short wait time

Actual behavior: Sandbox never starts, even after 24+ hours and multiple new sessions

Workaround tried: Opening new sessions, retrying commands — none resolved the issue

What Should Happen?

The Linux sandbox should start successfully within a short time (usually under a minute), allowing Cowork skills — such as creating Word documents — to run normally.

Error Messages/Logs

Steps to Reproduce

1.Open a Cowork session on claude.ai/code
2.Ask Claude to run any skill that requires the Linux sandbox (e.g., "create a Word document")
3.Observe that the sandbox fails to start and returns an error stating the workspace is not ready

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

N/A

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗