claude-code - 💡(How to fix) Fix Cowork session fails with 'Failed to create bridge sockets after 5 attempts' after April 16 app update [1 comments, 1 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#49714Fetched 2026-04-17 08:33:29
View on GitHub
Comments
1
Participants
1
Timeline
9
Reactions
0
Author
Participants
Timeline (top)
labeled ×5closed ×1commented ×1mentioned ×1

Every attempt to start a cowork session fails immediately with exit code 1. The Claude Code process inside the VM exits ~800ms after spawning.

Error Message

From ~/Library/Logs/Claude/cowork_vm_node.log:

[warn] [vm-stderr] Error: Failed to create bridge sockets after 5 attempts
[info] [Process] Exited, code=1, signal=null, duration=~800ms, oom=false

Root Cause

Every attempt to start a cowork session fails immediately with exit code 1. The Claude Code process inside the VM exits ~800ms after spawning.

Code Example

[warn] [vm-stderr] Error: Failed to create bridge sockets after 5 attempts
[info] [Process] Exited, code=1, signal=null, duration=~800ms, oom=false
RAW_BUFFERClick to expand / collapse

Description

Every attempt to start a cowork session fails immediately with exit code 1. The Claude Code process inside the VM exits ~800ms after spawning.

Error

From ~/Library/Logs/Claude/cowork_vm_node.log:

[warn] [vm-stderr] Error: Failed to create bridge sockets after 5 attempts
[info] [Process] Exited, code=1, signal=null, duration=~800ms, oom=false

Version History

The app updated three times on April 16, 2026. Cowork worked fine on April 15 and broke after the April 16 updates:

DateApp VersionStatus
Apr 15 and prior1.1.8629✅ Working
Apr 16 08:151.2581.0❌ Broken
Apr 16 08:481.2773.0❌ Broken
Apr 16 14:161.3036.0❌ Broken

The VM bundle (rootfs.img.zst) was also updated on April 16 at ~08:39, coinciding with the first broken update.

Environment

  • OS: macOS Darwin 25.4.0 (arm64)
  • Current app version: 1.3036.0
  • Claude CLI version: 2.1.112
  • SDK installed into VM: 2.1.111
  • VM bundle hash: 5680b11bcdab215cccf07e0c0bd1bd9213b0c25d
  • coworkNetworkMode: gvisor

Steps to Reproduce

  1. Open Claude Mac app (version 1.3036.0)
  2. Start any new cowork session
  3. Session immediately fails with "Claude Code process exited with code 1"

What I've Tried

  • Signed out and back in — no change
  • Deleted rootfs.img and sessiondata.img to force VM rebuild from rootfs.img.zst — no change
  • The error is 100% reproducible on every attempt

Additional Context

The VM itself boots and connects successfully. The failure happens specifically when the Claude Code process inside the VM tries to establish bridge sockets back to the host. All infrastructure steps (vm_boot, guest_vsock_connect, sdk_install) complete successfully before the crash.

extent analysis

TL;DR

The most likely fix is to investigate and address the issue with creating bridge sockets in the VM, potentially related to the updated VM bundle or app versions.

Guidance

  • Review the changes made in the April 16 updates, especially the VM bundle update at ~08:39, to identify potential causes for the bridge socket creation failure.
  • Verify that the gvisor network mode is correctly configured and compatible with the updated VM bundle and app versions.
  • Check for any known issues or incompatibilities with the coworkNetworkMode set to gvisor and the updated components.
  • Consider reverting to a previous version of the app or VM bundle to isolate the issue and determine if it's related to a specific update.

Example

No specific code snippet is provided as the issue seems to be related to the interaction between the VM, app, and network configuration.

Notes

The issue seems to be specific to the updated components and the gvisor network mode. Further investigation is needed to determine the root cause and develop a permanent fix.

Recommendation

Apply a workaround by reverting to a previous version of the app or VM bundle, as the issue is likely related to one of the updates made on April 16. This will help isolate the issue and determine the best course of action for a permanent fix.

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