Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Agent/CCD sessions crash with "Failed to create bridge sockets after 5 attempts" on 2.1.111 [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#49531•Fetched 2026-04-17 08:38:29
View on GitHub
Comments
1
Participants
2
Timeline
8
Reactions
0
Author
SpecialEd05SpecialEd05
Participants
claude[bot]claude[bot]SpecialEd05SpecialEd05
Timeline (top)
labeled ×5closed ×1commented ×1unlabeled ×1

Error Message

Error Messages/Logs

[vm-stderr <uuid>] Error: Failed to create bridge sockets after 5 attempts

Fix Action

Workaround

None found. Downgrading to 2.1.101 not possible (binary not cached).

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, Claude Code VM SDK 2.1.111 (macOS ARM > All local agent sessions crash ~1s after spawn with Failed to create bridge sockets after 5 attempts, exit code 1. Worked on 2.1.101 (April 14). Broke on 2.1.111 (April 16). Fresh re-download of the VM SDK reproduces. Happens across all agent folders, with ~11 plugins loaded and 20 virtio-fs mounts. Non-agent sessions on the same 2.1.111 build work fine — the bug is in the VM bridge path. Log: ~/Library/Logs/Claude/cowork_vm_node.log

What Should Happen?

The agents should work

Error Messages/Logs

Steps to Reproduce

Environment

  • macOS (Apple Silicon)
  • Claude desktop app: 1.3036.0
  • Claude Code SDK (VM): 2.1.111
  • Previously working: 2.1.101 (April 14, 2026)
  • Broken since: 2.1.111 auto-installed (April 16, 2026)

Steps to Reproduce

  1. Open the Claude desktop app.
  2. Start any local agent-mode session (folder-based agent / Cowork CCD session) — e.g., open a folder with a CLAUDE.md and begin a session scoped to it.
  3. Send any message (or just let the session initialize).

Expected

Agent session initializes and responds.

Actual

Within ~1 second of spawn, the VM-side claude process exits with code 1. The desktop app surfaces:

"Claude Code process exited with code 1. You can restart the conversation from an earlier message."

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

[Spawn:vm] id=<uuid> Spawn succeeded in ~70ms [vm-stderr <uuid>] Error: Failed to create bridge sockets after 5 attempts [Process:<uuid>] Exited, code=1, signal=null, duration=~1000ms, oom=false

Scope

  • Reproduces on every agent session attempt (6+ consecutive failures logged today).
  • Reproduces after fully deleting ~/Library/Application Support/Claude/claude-code-vm/2.1.111 and ~/Library/Application Support/Claude/claude-code/2.1.111 to force a fresh download — so it's not a corrupted binary.
  • Non-agent Claude Code sessions on the same 2.1.111 build work fine. The bug is specific to the VM/bridge path used by Cowork agent sessions.
  • 11 remote plugins loaded, 20 virtio-fs mounts on the spawn command.

Workaround

None found. Downgrading to 2.1.101 not possible (binary not cached).

Attached log

~/Library/Logs/Claude/cowork_vm_node.log (see excerpt above; full file available)

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.111

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

extent analysis

TL;DR

The issue is likely caused by a regression in the VM bridge path of the Claude Code SDK, introduced in version 2.1.111, and can be temporarily mitigated by investigating the bridge socket creation process.

Guidance

  • Investigate the Failed to create bridge sockets after 5 attempts error message in the ~/Library/Logs/Claude/cowork_vm_node.log log file to understand the root cause of the issue.
  • Verify that the issue is specific to the VM/bridge path used by Cowork agent sessions by testing non-agent Claude Code sessions on the same 2.1.111 build.
  • Consider testing with a reduced number of remote plugins and virtio-fs mounts to see if the issue is related to the complexity of the spawn command.
  • Review the changes made in the Claude Code SDK between versions 2.1.101 and 2.1.111 to identify potential causes of the regression.

Example

No code snippet is provided as the issue is related to a specific version of the Claude Code SDK and its interaction with the VM bridge path.

Notes

The issue is specific to the macOS (Apple Silicon) platform and the Claude Code SDK version 2.1.111. Downgrading to version 2.1.101 is not possible as the binary is not cached.

Recommendation

Apply a workaround by investigating the bridge socket creation process and testing with reduced complexity, as the issue is likely caused by a regression in the VM bridge path of the Claude Code SDK.

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#task chaining#parallel task#integration issue#index setup

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 Agent/CCD sessions crash with "Failed to create bridge sockets after 5 attempts" on 2.1.111 [1 comments, 2 participants]