Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Cowork: Claude Code process exited with code 1 — Failed to create bridge sockets after 5 attempts (all tasks, after VM auto-update to 2.1.111) [4 comments, 4 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#49461•Fetched 2026-04-17 08:40:32
View on GitHub
Comments
4
Participants
4
Timeline
15
Reactions
2
Author
danfrancisdanfrancis
Participants
claude[bot]claude[bot]danfrancisdanfrancisgithub-actions[bot]github-actions[bot]usethedatausethedata
Timeline (top)
labeled ×5commented ×4cross-referenced ×3subscribed ×2

All Cowork tasks fail immediately after an automatic update of the Claude Code VM binary today (April 16, 2026). The Claude Code process inside the VM exits with code 1 on every task, including trivial ones like "Is Claude Cowork working?".

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

Root Cause

All Cowork tasks fail immediately after an automatic update of the Claude Code VM binary today (April 16, 2026). The Claude Code process inside the VM exits with code 1 on every task, including trivial ones like "Is Claude Cowork working?".

Code Example

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

Summary

All Cowork tasks fail immediately after an automatic update of the Claude Code VM binary today (April 16, 2026). The Claude Code process inside the VM exits with code 1 on every task, including trivial ones like "Is Claude Cowork working?".

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

Timeline

  • 11:52 AM — ~/Library/Application Support/Claude/claude-code-vm/2.1.111/claude was updated (file timestamp)
  • 12:24 PM — First task failure observed in Cowork
  • All tasks have failed since then

Environment

  • Claude Code version: 2.1.111
  • OS: macOS (Apple Silicon, Darwin 25.4.0)
  • Claude Desktop app: latest

Reproduction

  1. Open Claude Desktop / Cowork
  2. Start any new task (any prompt, any project or no project)
  3. Observe immediate failure: "Something went wrong — Claude Code process exited with code 1"

Troubleshooting Already Attempted

  • Quit and relaunched the Claude desktop app
  • Restarted the Mac
  • Verified no VPN or active firewall
  • Installed socat via Homebrew (brew install socat 1.8.1.1) — did not resolve
  • The cmd=/usr/local/bin/claude binary runs inside a Linux VM; Mac-side socat is not relevant

Additional Context

The spawn log shows the VM starts successfully (Spawn succeeded) and the OAuth token is approved, but the process exits within ~1 second with the bridge socket error. The issue appears to be in how the 2.1.111 VM hypervisor sets up internal VM networking.

This is a regression — Cowork was working normally before the auto-update this morning.

extent analysis

TL;DR

The most likely fix is to revert or update the Claude Code VM binary to a version that correctly sets up internal VM networking.

Guidance

  • Investigate the changes made in the 2.1.111 update to the Claude Code VM binary, specifically focusing on how it sets up internal VM networking.
  • Verify that the issue is indeed related to the bridge socket creation by checking the spawn log for any other errors or warnings.
  • Consider rolling back to the previous version of the Claude Code VM binary to see if it resolves the issue.
  • If possible, test the claude binary directly inside the Linux VM to isolate the issue from the Mac-side environment.

Example

No code snippet is provided as the issue seems to be related to the VM hypervisor setup rather than a specific code error.

Notes

The issue appears to be a regression introduced by the 2.1.111 update, and the exact cause is related to the internal VM networking setup. Without more information about the changes made in this update, it's difficult to provide a more specific fix.

Recommendation

Apply a workaround by rolling back to the previous version of the Claude Code VM binary, as this is likely to resolve the issue until a fixed version is released.

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

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING