claude-code - 💡(How to fix) Fix Claude Desktop: 'Failed to create bridge sockets' on macOS 26 Tahoe [3 comments, 4 participants]

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

TL;DR

The issue is likely due to a compatibility problem between the Claude Desktop VM sandbox and macOS 26 Tahoe's Virtualization framework, causing the Claude Code process to exit with code 1 when trying to create bridge sockets.

Guidance

• Investigate the Virtualization framework changes in macOS 26 Tahoe and their impact on the Claude Desktop VM sandbox to understand the root cause of the compatibility issue.
• Try setting coworkFullVmSandbox to false in other configuration files or environment variables, if available, to see if it makes a difference.
• Since the CLI works perfectly, compare the environment and configuration settings between the CLI and the Desktop app to identify potential differences that could be contributing to the issue.
• Consider reaching out to the Claude Desktop support team to report the issue and ask about potential server-side fixes or workarounds, given that the sandbox setting appears to be server-side controlled.

Example

No code snippet is provided as the issue seems to be related to configuration and compatibility rather than a specific code problem.

Notes

The exact solution may depend on the specifics of the Claude Desktop and macOS 26 Tahoe configurations, which are not fully detailed in the issue. The provided steps are aimed at guiding the user towards identifying the root cause and potential workarounds.

Recommendation

Apply workaround: Given the potential complexity of resolving the compatibility issue directly, applying a workaround, such as adjusting configuration settings or using the CLI as an alternative for now, might be the most practical approach until a more permanent fix is available.