Claude Code Cowork process exited with code 127 on macOS Intel

What this error means

Claude Code process exited with code 127 is a Claude Code failure pattern reported for developers trying to fix claude code cowork tasks failing immediately with exit code 127. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

Official GitHub issue on anthropics/claude-code repo (May 2026). Every Cowork task in Claude Desktop fails immediately with ‘Claude Code process exited with code 127’ on macOS Intel with App Store sandboxed Claude Desktop and native CLI 2.1.139. Affects Pro plan subscribers.

Common causes

• Claude Max and Pro subscribers experience immediate Cowork task failures on macOS Intel with App Store Claude Desktop, blocking all AI-assisted coding workflows. The exit code 127 indicates a command-not-found error in the Claude Code binary launch path, making it impossible to use a paid service.
• Official GitHub issue on anthropics/claude-code repo (May 2026). Every Cowork task in Claude Desktop fails immediately with ‘Claude Code process exited with code 127’ on macOS Intel with App Store sandboxed Claude Desktop and native CLI 2.1.139. Affects Pro plan subscribers.

Quick fixes

1. Confirm the exact error signature matches Claude Code process exited with code 127.
2. Check the Claude Code account, local tool state, and provider configuration involved in the failing workflow.
3. Compare the failing environment with a known working setup, then change one configuration value at a time.

Platform/tool-specific checks

• Verify the command, editor, extension, or API client that produced the error.
• Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
• Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

1. Capture the exact error message and the command, editor action, or request that triggered it.
2. Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
3. Review the source evidence below and compare it with your environment.
4. Apply one change at a time and rerun the smallest failing action.
5. Keep the working fix documented for the team or deployment environment.

How to prevent it

• Keep provider/tool configuration documented.
• Record non-secret diagnostics such as tool version, provider name, model name, and command path.
• Add a lightweight check before CI or production workflows depend on the tool.

Sources checked

• https://github.com/anthropics/claude-code/issues/58495

Evidence note: Official GitHub issue on anthropics/claude-code repo (May 2026). Every Cowork task in Claude Desktop fails immediately with ‘Claude Code process exited with code 127’ on macOS Intel with App Store sandboxed Claude Desktop and native CLI 2.1.139. Affects Pro plan subscribers.

Related errors

• Claude Code Desktop app fails to launch on macOS
• Claude Code App Store sandbox permission denied
• Claude Code native CLI path not found

FAQ

What should I check first?

Start with the exact Claude Code process exited with code 127 text and the smallest action that reproduces it.

Can I ignore this error?

No. Treat it as a failed Claude Code workflow until the root cause is understood.

Is this guaranteed to have one fix?

No. The imported evidence supports the troubleshooting path above, but tool behavior can vary by account, plan, version, provider, and local configuration.

How do I know the fix worked?

Rerun the same command, editor action, or request. The fix is working when that action completes without Claude Code process exited with code 127.