Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Cowork: All sessions fail with "Failed to create bridge sockets after 5 attempts" after SDK auto-update to 2.1.111 [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#49364•Fetched 2026-04-17 08:43:14
View on GitHub
Comments
0
Participants
1
Timeline
5
Reactions
0
Author
JoeEvans-atJoeEvans-at
Participants
JoeEvans-atJoeEvans-at
Timeline (top)
labeled ×4closed ×1

Error Message

Environment

  • Claude desktop version: 1.3036.0
  • Claude Code VM SDK version: 2.1.111 (auto-updated from 2.1.92)
  • macOS: 26.4.1 (Build 25E253)

Exact 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=~1000ms, oom=false

Root cause (from logs)

TimeEvent
12:50–12:51Sessions working fine, SDK version = 2.1.92
12:52:32App quit/restarted
12:52:54SDK updated to 2.1.111
13:04:20First spawn → bridge socket failure
13:04+Every subsequent spawn fails identically

Root Cause

Root cause (from logs)

Code Example

## Environment
                
- **Claude desktop version:** 1.3036.0
- **Claude Code VM SDK version:** 2.1.111 (auto-updated from 2.1.92)
- **macOS:** 26.4.1 (Build 25E253)                                  
                                                                                
## Exact 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=~1000ms, oom=false
                                                                                
## Root cause (from logs)
                                                                                
| Time | Event |                                                              
|------|-------|
| 12:50–12:51 | Sessions working fine, SDK version = **2.1.92** |             
| 12:52:32 | App quit/restarted |
| 12:52:54 | SDK updated to **2.1.111** |                                     
| 13:04:20 | First spawn → bridge socket failure |
| 13:04+ | Every subsequent spawn fails identically |
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?

After the Cowork VM SDK auto-updated from 2.1.92 → 2.1.111, every Claude Code process spawned inside the VM exits with code 1 within ~1 second. Restarting the Claude desktop app does not fix it — the updated SDK persists across restarts.

What Should Happen?

Sessions should spawn and run normally after an SDK auto-update. The bridge socket IPC between the claude binary (inside the VM) and the host node layer should remain functional across SDK version bumps, or the update should be gated/rolled back if the new version is incompatible with the current desktop app version.

Error Messages/Logs

## Environment
                
- **Claude desktop version:** 1.3036.0
- **Claude Code VM SDK version:** 2.1.111 (auto-updated from 2.1.92)
- **macOS:** 26.4.1 (Build 25E253)                                  
                                                                                
## Exact 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=~1000ms, oom=false
                                                                                
## Root cause (from logs)
                                                                                
| Time | Event |                                                              
|------|-------|
| 12:50–12:51 | Sessions working fine, SDK version = **2.1.92** |             
| 12:52:32 | App quit/restarted |
| 12:52:54 | SDK updated to **2.1.111** |                                     
| 13:04:20 | First spawn → bridge socket failure |
| 13:04+ | Every subsequent spawn fails identically |

Steps to Reproduce

  1. Open any Cowork session (new or resumed)
  2. Process spawns, OAuth approves successfully
  3. Within ~1 second: bridge socket error, exit code 1
  4. Happens on every session including trivial new ones
  5. Restarting Claude desktop does not resolve it

Claude Model

Not sure / Multiple models

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

1.3036.0

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Other

Additional Information

  • oom=false — not a memory issue
  • 269 GB disk free
  • VM boots and connects successfully — bridge socket failure happens inside the VM after spawn
  • Consistent across all session types and plugin configurations

extent analysis

TL;DR

The issue is likely due to an incompatibility between the updated Cowork VM SDK version 2.1.111 and the current Claude desktop app version 1.3036.0, causing the bridge socket to fail.

Guidance

  • Verify that the issue is indeed caused by the SDK update by checking the logs for any other potential errors or warnings that may indicate a different root cause.
  • Attempt to roll back the SDK update to version 2.1.92 to see if the issue is resolved, which would confirm the incompatibility.
  • Check if there are any known issues or release notes for the updated SDK version 2.1.111 that may provide more information on the compatibility with the current Claude desktop app version.
  • Consider reaching out to the developers or support team for further assistance, as this issue may require a fix or update to the Claude desktop app to ensure compatibility with the updated SDK.

Example

No code snippet is provided as the issue seems to be related to a compatibility problem between the SDK and the desktop app, rather than a code-specific issue.

Notes

The fact that the issue persists across restarts and is consistent across all session types and plugin configurations suggests that the problem is likely related to the SDK update. However, without more information on the specific changes made in the updated SDK version, it is difficult to provide a more detailed solution.

Recommendation

Apply workaround: Roll back the SDK update to version 2.1.92, as this version was previously working and the issue started after the update. This will allow users to continue working while a more permanent fix is developed.

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#model compatibility#GPU setup#container setup#orchestration 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 Cowork: All sessions fail with "Failed to create bridge sockets after 5 attempts" after SDK auto-update to 2.1.111 [1 participants]