Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [Bug] Cowork mode bridge socket creation fails in SDK 2.1.111 [2 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#49460•Fetched 2026-04-17 08:40:35
View on GitHub
Comments
2
Participants
3
Timeline
7
Reactions
0
Author
ZhingelZhingel
Participants
claude[bot]claude[bot]github-actions[bot]github-actions[bot]ZhingelZhingel
Timeline (top)
labeled ×3commented ×2closed ×1cross-referenced ×1

Error Message

Error in ~/Library/Logs/Claude/cowork_vm_node.log: [warn] [vm-stderr <id>] Error: Failed to create bridge sockets after 5 attempts

Code Example

[]
RAW_BUFFERClick to expand / collapse

Bug Description Title: Cowork mode globally broken since 2.1.111 — "Failed to create bridge sockets after 5 attempts"

Description:

Every new cowork session fails on macOS, globally (all chats, new or resumed), since guest SDK was updated to 2.1.111 today at 19:22 local time.

Environment:

macOS 26.3 (Tahoe), arm64 (Apple Silicon) Claude Desktop: 1.3036.0 Host CLI claude: 2.1.111 (native, ~/.local/bin/claude) Guest VM SDK: 2.1.111 (at ~/Library/Application Support/Claude/claude-code-vm/2.1.111/claude) No npm/Homebrew installs, only native. Error in ~/Library/Logs/Claude/cowork_vm_node.log:

[warn] [vm-stderr <id>] Error: Failed to create bridge sockets after 5 attempts [info] [Process:<id>] Exited, code=1, signal=null, duration=~1000-1600ms, oom=false Exits ~1s after Spawn succeeded, on every session.

Timeline:

First occurrence: 2026-04-16 19:23:05 (right after sdk_install completed pushed 2.1.111 to claude-code-vm/ at 19:22:46) Worked earlier same day (last successful sessions 12:52) 12+ consecutive failures across 1.5 hours. What I tried (none helped):

Full Claude.app quit + restart rm -rf ~/Library/Application Support/Claude/claude-code-vm — re-downloaded same 2.1.111 binary, same failure Updated host CLI from 2.1.92 → 2.1.111 via claude install latest to match guest — same failure Verified only one claude install exists Fault isolation (host-side looks clean):

cowork_vm_swift.log: VM boot → guest connected → CA certs installed → SDK installed → OAuth approved → Process spawned — all OK coworkd.log: user recovery (88 users), static IP assigned, RPC connected, ready event sent — all OK cowork_vm_node.log: Spawn succeeded in ~100-300ms then vm-stderr ... Failed to create bridge sockets within 1s The failure is 100% inside the guest-side claude binary at /usr/local/bin/claude inside the VM (= claude-code-vm/2.1.111/claude). Host infrastructure is fine. Looks like a regression in bridge socket creation logic in guest SDK 2.1.111.

Host-side stdio MCP servers (~/Library/Logs/Claude/mcp-server-*.log) are all healthy — ruled out.

Environment Info

  • Platform: darwin
  • Terminal: Apple_Terminal
  • Version: 2.1.111
  • Feedback ID: 4459baaa-776d-43ae-8cd5-e50187849cf5

Errors

[]

extent analysis

TL;DR

The most likely fix is to revert or patch the guest SDK version to resolve the regression in bridge socket creation logic introduced in version 2.1.111.

Guidance

  • Verify that the issue persists across different cowork sessions and macOS environments to rule out any transient or environment-specific causes.
  • Attempt to downgrade the guest SDK to a previous version (e.g., 2.1.92) to see if the issue is resolved, which would confirm the regression hypothesis.
  • Inspect the cowork_vm_node.log for any additional error details or patterns that could provide more insight into the bridge socket creation failure.
  • Consider reaching out to the development team or support for version 2.1.111 to report the issue and inquire about potential patches or fixes.

Example

No specific code snippet can be provided without more context on the bridge socket creation logic, but debugging the claude binary inside the VM for socket creation issues could be a starting point.

Notes

The issue seems to be isolated to the guest SDK version 2.1.111, and the host infrastructure appears to be functioning correctly. However, without access to the source code or more detailed logs, providing a definitive fix is challenging.

Recommendation

Apply a workaround by downgrading the guest SDK to a previous version until a fixed version of the SDK is released, as this approach has a high likelihood of resolving the issue based on the provided information.

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…
#prompt issue#agent setup#task chaining#parallel task#integration issue

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 mode bridge socket creation fails in SDK 2.1.111 [2 comments, 3 participants]