claude-code - 💡(How to fix) Fix Cowork broken on latest 1.3036.0 — "Failed to create bridge sockets" on all sessions [3 comments, 3 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#49376Fetched 2026-04-17 08:42:52
View on GitHub
Comments
3
Participants
3
Timeline
13
Reactions
1
Timeline (top)
labeled ×5cross-referenced ×4commented ×3closed ×1

Error Message

What Should Happen?

Cowork sessions should start successfully and allow Claude Code to run inside the Cowork VM. Opening any Cowork project (new or resumed) should produce a working chat session. Error Messages/Logs

Claude Desktop: 1.3036.0 Claude Code CLI (inside VM): 2.1.111 macOS: [check Apple Menu → About This Mac] Every Cowork session fails immediately with exit code 1, ~900ms after spawn. From ~/Library/Logs/Claude/cowork_vm_node.log: 2026-04-16 14:54:42 [info] [Spawn:config] Creating spawn function for process=sweet-wonderful-faraday, isResume=false, allowedDomains=23 2026-04-16 14:54:43 [warn] [vm-stderr a251f4d1] Error: Failed to create bridge sockets after 5 attempts 2026-04-16 14:54:43 [info] [Process:a251f4d1-495d-48c4-b3e7-c06240ad25a0] Exited, code=1, signal=null, duration=813ms, oom=false From main.log: [error] Session local_xxx query error: Claude Code process exited with code 1 unhealthy_reason: 'system_error', error_message: 'Claude Code process exited with code 1', error_category: 'process_crashed', Reproduces on:

  • New sessions (isResume=false) AND resumed sessions
  • All Cowork projects
  • After full Claude Desktop reinstall
  • After full Mac reboot
  • After clearing ~/Library/Application Support/Claude/claude-code-vm/ cache (redownloaded same 2.1.111) Ruled out:
  • No VPN, no firewall active
  • TMPDIR exists and is writable (/var/folders/...)
  • No suspicious network extensions
  • Regular Claude chat works fine
  • Claude Code in terminal works fine
  • Only Cowork VM-spawned Claude Code fails Related issues: #19503, #23746, #11079

Code Example

What Should Happen?

Cowork sessions should start successfully and allow Claude Code to run inside the Cowork VM. Opening any Cowork project (new or resumed) should produce a working chat session.
Error Messages/Logs

Claude Desktop: 1.3036.0
Claude Code CLI (inside VM): 2.1.111
macOS: [check Apple MenuAbout This Mac]
Every Cowork session fails immediately with exit code 1, ~900ms after spawn.
From ~/Library/Logs/Claude/cowork_vm_node.log:
2026-04-16 14:54:42 [info] [Spawn:config] Creating spawn function for process=sweet-wonderful-faraday, isResume=false, allowedDomains=23
2026-04-16 14:54:43 [warn] [vm-stderr a251f4d1] Error: Failed to create bridge sockets after 5 attempts
2026-04-16 14:54:43 [info] [Process:a251f4d1-495d-48c4-b3e7-c06240ad25a0] Exited, code=1, signal=null, duration=813ms, oom=false
From main.log:
[error] Session local_xxx query error: Claude Code process exited with code 1
  unhealthy_reason: 'system_error',
  error_message: 'Claude Code process exited with code 1',
  error_category: 'process_crashed',
Reproduces on:
- New sessions (isResume=false) AND resumed sessions
- All Cowork projects
- After full Claude Desktop reinstall
- After full Mac reboot
- After clearing ~/Library/Application Support/Claude/claude-code-vm/ cache (redownloaded same 2.1.111)
Ruled out:
- No VPN, no firewall active
- TMPDIR exists and is writable (/var/folders/...)
- No suspicious network extensions
- Regular Claude chat works fine
- Claude Code in terminal works fine
- Only Cowork VM-spawned Claude Code fails
Related issues: #19503, #23746, #11079
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?

Claude Desktop: 1.3036.0 (latest) Claude Code CLI in VM: 2.1.111 macOS: [your version — check Apple Menu → About This Mac] All Cowork sessions fail ~900ms with exit code 1. VM log error: "Error: Failed to create bridge sockets after 5 attempts" Tried (all failed):

  • Full Claude Desktop reinstall
  • Full Mac reboot
  • New sessions (isResume=false) and resume sessions
  • Clearing claude-code-vm cache (redownloaded same 2.1.111)
  • No VPN, no firewall, TMPDIR writable Related: #19503, #23746, #11079 Claude Code in terminal works fine. Only Cowork VM-spawned Claude Code fails.

What Should Happen?

Cowork sessions should start successfully and allow Claude Code to run inside the Cowork VM. Opening any Cowork project (new or resumed) should produce a working chat session.

Error Messages/Logs

What Should Happen?

Cowork sessions should start successfully and allow Claude Code to run inside the Cowork VM. Opening any Cowork project (new or resumed) should produce a working chat session.
Error Messages/Logs

Claude Desktop: 1.3036.0
Claude Code CLI (inside VM): 2.1.111
macOS: [check Apple Menu → About This Mac]
Every Cowork session fails immediately with exit code 1, ~900ms after spawn.
From ~/Library/Logs/Claude/cowork_vm_node.log:
2026-04-16 14:54:42 [info] [Spawn:config] Creating spawn function for process=sweet-wonderful-faraday, isResume=false, allowedDomains=23
2026-04-16 14:54:43 [warn] [vm-stderr a251f4d1] Error: Failed to create bridge sockets after 5 attempts
2026-04-16 14:54:43 [info] [Process:a251f4d1-495d-48c4-b3e7-c06240ad25a0] Exited, code=1, signal=null, duration=813ms, oom=false
From main.log:
[error] Session local_xxx query error: Claude Code process exited with code 1
  unhealthy_reason: 'system_error',
  error_message: 'Claude Code process exited with code 1',
  error_category: 'process_crashed',
Reproduces on:
- New sessions (isResume=false) AND resumed sessions
- All Cowork projects
- After full Claude Desktop reinstall
- After full Mac reboot
- After clearing ~/Library/Application Support/Claude/claude-code-vm/ cache (redownloaded same 2.1.111)
Ruled out:
- No VPN, no firewall active
- TMPDIR exists and is writable (/var/folders/...)
- No suspicious network extensions
- Regular Claude chat works fine
- Claude Code in terminal works fine
- Only Cowork VM-spawned Claude Code fails
Related issues: #19503, #23746, #11079

Steps to Reproduce

Yes. Cowork was working normally prior to today (2026-04-16). Successful Cowork runs as recent as this morning in our logs (e.g., a Redfin MLS scraper run completed successfully in Cowork earlier today). Cowork started failing after that with no user configuration changes.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.89 (Claude Code) — local terminal install Note: The Claude Code version that crashes inside the Cowork VM is 2.1.111 (per logs: "Installing SDK: subpath=...claude-code-vm, version=2.1.111"). That's the version spawned by Cowork — the local terminal 2.1.89 works fine.

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

extent analysis

TL;DR

The most likely fix is to investigate and resolve the "Failed to create bridge sockets" error in the Cowork VM, potentially related to version compatibility between Claude Code 2.1.111 and the Cowork environment.

Guidance

  • Investigate the "Failed to create bridge sockets after 5 attempts" error in the cowork_vm_node.log to understand the root cause of the issue.
  • Compare the versions of Claude Code used in the terminal (2.1.89) and the Cowork VM (2.1.111) to determine if there's a version compatibility issue.
  • Check the related issues (#19503, #23746, #11079) to see if they provide any insights or solutions to the problem.
  • Consider downgrading the Claude Code version in the Cowork VM to 2.1.89 to see if it resolves the issue.

Example

No code snippet is provided as the issue seems to be related to version compatibility and environment configuration rather than a specific code error.

Notes

The issue seems to be specific to the Cowork VM environment and the version of Claude Code used within it. The fact that Claude Code works fine in the terminal suggests that the issue is not with the Claude Code itself, but rather with the interaction between Claude Code and the Cowork VM.

Recommendation

Apply a workaround by downgrading the Claude Code version in the Cowork VM to 2.1.89, as it is known to work in the terminal and may resolve the compatibility issue.

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…

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 Cowork broken on latest 1.3036.0 — "Failed to create bridge sockets" on all sessions [3 comments, 3 participants]