[BUG] Claude Code process exited with code 127

Status Fixed / completed
Reported on v2.1.133
Maintainer reply None cached
Activity 4 comments · opened May 8, 2026 · closed May 13, 2026

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?

I'm setting up Claude desktop on a new MackBook Air (specs below) and have no issues with Chat, but Cowork and Code will not run, regardless of everything being installed correctly. I did troubleshooting in Chat extensively and it finally recommended a bug be filed.

Any command in Cowork shows "Claude Code process exited with code 127"
Code also incorrectly reports "binary doesn't match architecture" despite both being ARM64

macOS Tahoe 26.4, Apple Silicon
Node.js v24.15.0 via nvm, ARM64
Claude Code 2.1.133, ARM64 binary
PATH correctly set via launchctl

/Users/joewheeler/.nvm/versions/node/v24.15.0/bin:/Users/joewheeler/.nvm/versions/node/v24.15.0/bin:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin:/opt/pkg/env/active/bin:/opt/pmk/env/global/bin:/Library/Apple/usr/bin

What Should Happen?

Claude Cowork and Code should accept commands and they are not.

Error Messages/Logs

Claude Code process exited with code 127

The Claude Code binary doesn't match this computer's architecture. Reinstall Claude Desktop for your platform.

Claude Code process exited with code 127

Steps to Reproduce

Install Claude desktop app on a new MacBook Air (Silicon) and try to use Cowork and Code.

macOS Tahoe 26.4, Apple Silicon
Node.js v24.15.0 via nvm, ARM64
Claude Code 2.1.133, ARM64 binary

Claude Model

Not sure / Multiple models

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

Claude Code 2.1.133, ARM64 binary

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

<img width="1255" height="131" alt="Image" src="https://github.com/user-attachments/assets/0935956f-5ef5-48c0-9a42-a4c09e0bc6a0" />
<img width="564" height="214" alt="Image" src="https://github.com/user-attachments/assets/931a6bf8-e67c-4ff0-83eb-fa86ff6c983f" />

View original on GitHub ↗

4 Comments

github-actions[bot] · 5 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/57292
  2. https://github.com/anthropics/claude-code/issues/48827
  3. https://github.com/anthropics/claude-code/issues/46661

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

joewheeler · 5 months ago

The bug I reported is not a duplicate of any of the three already reported issues above. Please do not close.

joewheeler · 5 months ago

I resolved this after working with Chat for a while:

Root Cause:
Cowork cannot find the claude binary when Node.js is installed via nvm, because nvm installs to a user-level path (~/.nvm/...) that macOS desktop apps don't have access to, even if launchctl is used to set the PATH.

Solution:
Create symlinks from the nvm-managed binaries to /usr/local/bin, which is a standard system location accessible to all macOS desktop apps:
sudo mkdir -p /usr/local/bin
sudo ln -sf ~/.nvm/versions/node/$(node --version)/bin/claude /usr/local/bin/claude
sudo ln -sf ~/.nvm/versions/node/$(node --version)/bin/node /usr/local/bin/node
No restart required after running these commands.

Environment:
macOS Tahoe 26.4, Apple Silicon
Node.js v24.15.0 installed via nvm
Claude Code 2.1.138

github-actions[bot] · 3 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.