Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Cowork: "Failed to create bridge sockets after 5 attempts" — all sessions crash with exit code 1, persists after full reinstall (macOS M4 Pro) [3 comments, 4 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#49439•Fetched 2026-04-17 08:41:10
View on GitHub
Comments
3
Participants
4
Timeline
10
Reactions
0
Author
axiomopsaxiomops
Participants
axiomopsaxiomopsclaude[bot]claude[bot]github-actions[bot]github-actions[bot]torrejonvtorrejonv
Timeline (top)
commented ×3labeled ×3cross-referenced ×2closed ×1

Error Message

[Spawn:vm] Spawn succeeded in 48ms [vm-stderr] Error: Failed to create bridge sockets after 5 attempts [Process] Exited, code=1, signal=null, duration=972ms, oom=false

Code Example

[Spawn:vm] Spawn succeeded in 48ms
[vm-stderr] Error: Failed to create bridge sockets after 5 attempts
[Process] Exited, code=1, signal=null, duration=972ms, oom=false

---

[process:bdb01aea] wrote srt-settings (domains=23 parentProxy=false) to /etc/srt-settings/bdb01aea.json
[process:bdb01aea] started PID 4009
[process:bdb01aea] direct child exited: code=1 signal=<nil>
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • - [x] This is a single bug report
  • - [x] I am using the latest version of Claude Desktop

Environment

  • Claude Desktop version: 1.1.4328
    • Claude Code SDK: 2.1.111
      • macOS: Sequoia, Darwin 25.3.0
        • Hardware: Apple M4 Pro, 48GB RAM

What's Wrong?

Every Cowork session — new and resumed — crashes instantly with Claude Code process exited with code 1. The VM boots successfully, network connects, API is reachable, OAuth token is valid. The crash happens ~1 second after spawn, consistently.

Issue started: April 15, 2026, coinciding with the Anthropic platform outage. Has not recovered since service was restored.

Key error from cowork_vm_node.log

[Spawn:vm] Spawn succeeded in 48ms
[vm-stderr] Error: Failed to create bridge sockets after 5 attempts
[Process] Exited, code=1, signal=null, duration=972ms, oom=false

From coworkd.log:

[process:bdb01aea] wrote srt-settings (domains=23 parentProxy=false) to /etc/srt-settings/bdb01aea.json
[process:bdb01aea] started PID 4009
[process:bdb01aea] direct child exited: code=1 signal=<nil>

What Should Happen?

Cowork sessions should start and run successfully as they did prior to April 15, 2026.

Steps to Reproduce

  1. Open Claude Desktop
    1. Navigate to Cowork
    1. Start any new session (or attempt to resume existing)
    1. Session immediately fails with exit code 1

Steps Already Tried — None Resolved It

  • Force quit and full restart / reboot
    • Cleared IndexedDB and Session Storage
      • Cleared local-agent-mode-sessions and claude-code-sessions
        • Deleted vm_bundles/claudevm.bundle (forced full ~10GB re-download)
          • Deleted claude-code-vm directory
            • Started brand new sessions (confirmed is_resume: false in logs)
              • Full uninstall + reinstall from claude.ai/download All attempts produce identical error. VM infrastructure (boot, network, API reachability) is healthy — failure is specific to bridge socket creation inside the VM.

extent analysis

TL;DR

The issue is likely related to the failure of creating bridge sockets within the VM, which can be mitigated by investigating and resolving potential configuration or dependency issues.

Guidance

  • Investigate the cowork_vm_node.log and coworkd.log files for any patterns or clues that could indicate the root cause of the bridge socket creation failure.
  • Verify that the Anthropic platform outage, which coincided with the start of the issue, did not introduce any changes or bugs that could be affecting the bridge socket creation process.
  • Check the system's network configuration and dependencies to ensure that they are compatible with the Claude Code SDK version 2.1.111 and the macOS Sequoia environment.
  • Consider testing the bridge socket creation process in isolation to determine if it's a specific issue with the Cowork session or a broader problem with the VM infrastructure.

Example

No code snippet is provided as the issue seems to be related to a specific configuration or dependency problem rather than a code-level issue.

Notes

The issue seems to be specific to the Claude Desktop environment and the Cowork session, and the provided logs suggest that the VM infrastructure is healthy. However, without more information about the bridge socket creation process and the specific dependencies involved, it's difficult to provide a more detailed solution.

Recommendation

Apply workaround: Given the complexity of the issue and the lack of clear information about the root cause, it's recommended to try to isolate the problem and apply a workaround, such as testing the bridge socket creation process in isolation or trying to recreate the issue in a different environment.

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…
#api#cache issue#memory leak#API versioning#request timeout

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] Cowork: "Failed to create bridge sockets after 5 attempts" — all sessions crash with exit code 1, persists after full reinstall (macOS M4 Pro) [3 comments, 4 participants]