claude-code - 💡(How to fix) Fix [BUG] Cowork: "Failed to create bridge sockets after 5 attempts" after auto-update to Claude.app 1.3036.0 [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#49434Fetched 2026-04-17 08:41:17
View on GitHub
Comments
1
Participants
2
Timeline
11
Reactions
0
Author
Timeline (top)
cross-referenced ×4labeled ×4closed ×1commented ×1

Error Message

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

2026-04-16 12:08:18 [info] [Spawn:vm] id=00728e55 Spawn succeeded in 130ms 2026-04-16 12:08:20 [warn] [vm-stderr 00728e55] Error: Failed to create bridge sockets after 5 attempts 2026-04-16 12:08:20 [info] [Process:00728e55] Exited, code=1, signal=null, duration=1958ms, oom=false

Same pattern on every spawn — 11+ occurrences since the auto-update. Claude Code SDK in VM: 2.1.111 VM bundle: 5680b11bcdab215cccf07e0c0bd1bd9213b0c25d

Code Example

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

2026-04-16 12:08:18 [info] [Spawn:vm] id=00728e55 Spawn succeeded in 130ms
2026-04-16 12:08:20 [warn] [vm-stderr 00728e55] Error: Failed to create bridge sockets after 5 attempts
2026-04-16 12:08:20 [info] [Process:00728e55] Exited, code=1, signal=null, duration=1958ms, oom=false

Same pattern on every spawn — 11+ occurrences since the auto-update.
Claude Code SDK in VM: 2.1.111
VM bundle: 5680b11bcdab215cccf07e0c0bd1bd9213b0c25d
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?

Cowork (Claude.app desktop) fails on every spawn with "Failed to create bridge sockets after 5 attempts" immediately after auto-update to Claude.app 1.3036.0. Every Claude Code process inside the Cowork VM exits code=1 within ~2 seconds of spawn. Happens across all projects and all new chats. Claude.ai web (non-Cowork) is unaffected.

What Should Happen?

Claude Code should spawn successfully inside the Cowork VM, create its bridge sockets, and accept input like it did before the 1.3036.0 update.

Error Messages/Logs

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

2026-04-16 12:08:18 [info] [Spawn:vm] id=00728e55 Spawn succeeded in 130ms
2026-04-16 12:08:20 [warn] [vm-stderr 00728e55] Error: Failed to create bridge sockets after 5 attempts
2026-04-16 12:08:20 [info] [Process:00728e55] Exited, code=1, signal=null, duration=1958ms, oom=false

Same pattern on every spawn — 11+ occurrences since the auto-update.
Claude Code SDK in VM: 2.1.111
VM bundle: 5680b11bcdab215cccf07e0c0bd1bd9213b0c25d

Steps to Reproduce

  1. Open Claude.app 1.3036.0 on macOS.
  2. Open any Cowork chat (existing or new project).
  3. Send any message.
  4. Observe "Claude Code process exited with code 1" immediately.
  5. Check ~/Library/Logs/Claude/cowork_vm_node.log — every spawn shows "Failed to create bridge sockets after 5 attempts".

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

1.3035.x (exact unknown — last working session was ~2 hours before auto-update today 2026-04-16)

Claude Code Version

2.1.111 (bundled SDK inside Cowork VM)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Other

Additional Information

This is not a Claude Code CLI terminal bug — it's the Cowork VM inside Claude.app desktop. The form doesn't have a perfect category for it.

Context that narrows it to the 1.3036.0 build:

  • App bundle at /Applications/Claude.app mtime: 2026-04-16 (today, auto-updated).
  • /Applications parent mtime: 11:21 — exact moment of the quit that triggered the auto-update.
  • First "Failed to create bridge sockets" error in the log: 11:24, 3 minutes after the update.
  • Fresh DMG downloaded from claude.com/download reports the same 1.3036.0 — no downgrade path available.

Things already tried (none fixed it):

  • Full app quit + relaunch.
  • Wiped SDK 2.1.111 and .sdk-version marker — SDK reinstalls, bug persists.
  • Deleted entire VM bundle (/vm_bundles/claudevm.bundle) and claude-code-vm dir — VM rebuilds from scratch (~3.5 min download), bug persists.
  • Reinstall from fresh DMG — same version, no change.
  • Tested across multiple projects / new chats — same failure.

The spawn itself always succeeds ("Spawn succeeded in ~100ms"); the failure is inside the claude binary when it attempts to create its bridge sockets. Strongly points to a regression in the 1.3036.0 build rather than local state corruption.

extent analysis

TL;DR

The most likely fix is to wait for a patch or downgrade to a previous version of Claude.app, as the issue seems to be a regression introduced in version 1.3036.0.

Guidance

  • The error "Failed to create bridge sockets after 5 attempts" suggests a problem with the communication between the Cowork VM and the Claude Code process.
  • Given that the issue started immediately after the auto-update to 1.3036.0 and the fact that downgrading is not possible with the current setup, waiting for a patch or a new version that addresses this regression might be the most viable solution.
  • Since the problem persists across different projects, new chats, and even after reinstalling the app and the VM bundle, it's likely a problem with the 1.3036.0 build itself rather than local state corruption.
  • Monitoring the GitHub issues and the official Claude.app channels for updates on this specific issue could provide a timeline for when a fix might be available.

Notes

The issue seems to be specific to the Cowork VM inside Claude.app desktop and does not affect the Claude.ai web version, suggesting that the problem might be related to how the VM interacts with the Claude Code process in the desktop application.

Recommendation

Apply workaround: Wait for a patch or an update that addresses the regression in version 1.3036.0, as downgrading to a previous version is not currently an option due to the auto-update mechanism and the lack of a downgrade path.

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 [BUG] Cowork: "Failed to create bridge sockets after 5 attempts" after auto-update to Claude.app 1.3036.0 [1 comments, 2 participants]