claude-code - 💡(How to fix) Fix Cowork on macOS 26.4.1: "Failed to create bridge sockets after 5 attempts" — every new session exits code 1 after desktop 1.3036.0 update [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#49489Fetched 2026-04-17 08:39:43
View on GitHub
Comments
2
Participants
3
Timeline
10
Reactions
0
Timeline (top)
labeled ×6commented ×2closed ×1cross-referenced ×1

Error Message

Error from cowork_vm_node.log

Error Messages/Logs

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?

What's Wrong?

After auto-updating Claude desktop to 1.3036.0 on April 16, 2026, every new Cowork session spawns successfully then crashes within ~900ms with exit code 1. Chat mode in desktop works fine. Claude Code CLI works fine. Only Cowork is affected. 100% reproducible.

Environment

  • Claude desktop: 1.3036.0 (auto-updated today, started the bug)
  • Claude Code: 2.1.111 (native install)
  • macOS: 26.4.1, build 25E253 (Tahoe)
  • Hardware: Mac Studio, Apple Silicon

Error from cowork_vm_node.log

What Should Happen?

Reproduction

100% reliable on any new Cowork session. VM boots cleanly, guest connects, network reaches REACHABLE, SDK 2.1.111 installs, OAuth passes MITM proxy, then bridge sockets fail.

Troubleshooting already completed (none resolved)

  • claude doctor — all clean
  • Renamed ~/.claude/
  • Deleted sessiondata.img
  • Deleted entire ~/Library/Application Support/Claude/vm_bundles/ (full VM rebuild)
  • Deleted ~/Library/Application Support/Claude/claude-code-vm/
  • Cleared ~/Library/Caches/Claude/
  • Raised maxfiles ulimit from 256 to 524288 via LaunchDaemon, verified post-reboot
  • Multiple reboots between steps
  • Confirmed no VPN, proxy, Little Snitch, or network filtering
  • Confirmed no zombie processes

Expected vs Actual

Expected: Cowork session launches and accepts prompts.
Actual: Instant crash with exit code 1.

Possibly related

#36419 (macOS Tahoe Cowork VM boot issue)

Willing to provide full logs on request.

Error Messages/Logs

Steps to Reproduce

Reproduction

100% reliable on any new Cowork session. VM boots cleanly, guest connects, network reaches REACHABLE, SDK 2.1.111 installs, OAuth passes MITM proxy, then bridge sockets fail.

Troubleshooting already completed (none resolved)

  • claude doctor — all clean
  • Renamed ~/.claude/
  • Deleted sessiondata.img
  • Deleted entire ~/Library/Application Support/Claude/vm_bundles/ (full VM rebuild)
  • Deleted ~/Library/Application Support/Claude/claude-code-vm/
  • Cleared ~/Library/Caches/Claude/
  • Raised maxfiles ulimit from 256 to 524288 via LaunchDaemon, verified post-reboot
  • Multiple reboots between steps
  • Confirmed no VPN, proxy, Little Snitch, or network filtering
  • Confirmed no zombie processes

Expected vs Actual

Expected: Cowork session launches and accepts prompts.
Actual: Instant crash with exit code 1.

Possibly related

#36419 (macOS Tahoe Cowork VM boot issue)

Willing to provide full logs on request.

Claude Model

Opus

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 related to a regression in the latest Claude desktop version 1.3036.0, causing Cowork sessions to crash with exit code 1 after updating.

Guidance

  • Review the error logs from cowork_vm_node.log to identify the specific point of failure, which may provide clues about the cause of the crash.
  • Consider reverting to a previous version of Claude desktop to see if the issue persists, as the problem started after the update to 1.3036.0.
  • Investigate the possibly related issue #36419 (macOS Tahoe Cowork VM boot issue) to see if there are any common factors or solutions that could apply to this case.
  • Provide the full logs as offered, which may help in diagnosing the issue more accurately.

Notes

The exact cause of the crash is not specified in the provided information, and without the full logs or more details about the error messages, it's challenging to provide a definitive solution. The steps taken so far, such as running claude doctor and deleting various files and folders, have not resolved the issue.

Recommendation

Apply a workaround by potentially downgrading the Claude desktop version to a previous one where Cowork sessions were working, if possible, until a fix for the current version is available. This is because the issue started after updating to version 1.3036.0, suggesting a regression.

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 Cowork on macOS 26.4.1: "Failed to create bridge sockets after 5 attempts" — every new session exits code 1 after desktop 1.3036.0 update [2 comments, 3 participants]