Cowork: All sessions fail with "Failed to create bridge sockets after 5 attempts" after SDK auto-update to 2.1.111

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] 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