[BUG] Cowork: "Claude Code process exited with code 127" on macOS Intel, App Store Claude Desktop, native CLI 2.1.139

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?

What's Wrong?

Every Cowork task in Claude Desktop fails immediately with "Something went wrong - Claude Code process exited with code 127" before any output is generated. Issue persists after extensive troubleshooting including full VM state reset.

Environment

• OS: macOS (Intel, darwin-x64)
• Claude Desktop: App Store version (sandboxed)
• Claude Code CLI: 2.1.139 (native install)
• Install path: `/Users/nathanielshanklin

<img width="1453" height="638" alt="Image" src="https://github.com/user-attachments/assets/6bb0b9a2-a105-40f2-b9dc-09148b230c83" />

/.local/share/claude/versions/2.1.139`

• Plan: Pro
• Feature affected: Cowork (Code tab unaffected because not tested; regular Claude chat works fine)

Steps to Reproduce

1. Open Claude Desktop
2. Click the Cowork tab
3. Send any prompt (e.g., "Hi Cowork, let's see where we are this week")
4. Task fails within ~1 second with exit code 127

Expected Behavior

Cowork task accepts the prompt, spawns the Claude Code binary inside the VM, and returns a response.

Actual Behavior

Something went wrong
Try sending your message again. If it keeps happening, share feedback so we can investigate.
Details
Claude Code process exited with code 127
You can restart the conversation from an earlier message.

Every task. Reproducible 100% of the time.

Troubleshooting Already Performed

1. Ran claude doctor. Initial output flagged two installations (npm-global at /usr/local/bin/claude showing a suspicious claude.exe binary path on macOS, and a native install at ~/.local/bin/claude), plus an "Insufficient permissions for auto-updates" warning.

1. Removed the conflicting npm install: sudo npm uninstall -g @anthropic-ai/claude-code. Confirmed 2 packages removed.

1. Reinstalled fresh via native installer: claude install. Verified v2.1.139 installed at ~/.local/share/claude/versions/2.1.139.

1. Fixed PATH: Added ~/.local/bin to ~/.bash_profile, sourced it.

1. Created symlink for GUI app resolution: sudo ln -s ~/.local/bin/claude /usr/local/bin/claude.

1. Verified clean terminal state: claude --version returns 2.1.139, claude doctor shows native install as active runner, auto-updates enabled, no permissions warnings.

1. Cleared Cowork VM state: Deleted ~/Library/Application Support/Claude/vm_bundles, emptied Trash, rebooted Mac, relaunched Claude Desktop. VM rebuilt on next launch.

1. Fully quit and relaunched Claude Desktop (Cmd+Q) multiple times across each step above.

Result: Cowork still exits with code 127 on every task. Terminal-side Claude Code is fully functional throughout.

Hypothesis

The sandboxed App Store version of Claude Desktop may not be resolving the claude binary inside its Cowork VM environment, regardless of host filesystem state. This is consistent with the pattern in #54274 and the entitlement-related root cause documented in #40283 and #46661 (though those report exit code 126 on Apple Silicon; this is exit code 127 on Intel).

Related Issues

• #54274 (exit code 127, macOS Apple Silicon)
• #46661 (exit code 126, missing com.apple.vm.networking entitlement, Apple Silicon)
• #40283 (Cowork Dispatch not responding, same root cause as #46661)
• #49485 (exit code 1, Apple M3)

Happy to provide additional logs, run any diagnostic commands, or share Console.app output if helpful.

What Should Happen?

I want Cowork to be able to work properly again

Error Messages/Logs

Steps to Reproduce

Just enter anything into cowork and I'm getting the code 127 error

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.139

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_