claude-code - 💡(How to fix) Fix [BUG] ( Cowork )[BUG] Cowork - Claude Code process exited with code 132 on Apple Silicon macOS [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#46687Fetched 2026-04-12 13:35:41
View on GitHub
Comments
1
Participants
2
Timeline
8
Reactions
0
Timeline (top)
labeled ×6commented ×1cross-referenced ×1

Error Message

Cowork crashes immediately on every attempt with the following error: 4. Error appears immediately, no response is generated

  • After cleanup, error code changed from 1 to 132,

Error Messages/Logs

  1. Error appears immediately, no response is generated

Root Cause

This appears related to issues #39270 and #46161 reported by other users on Apple Silicon. The exit code 132 (SIGILL) is more specific than the generic code 1 and may help narrow down the root cause.

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

Cowork crashes immediately on every attempt with the following error:

"Something went wrong. Claude Code process exited with code 132. You can restart the conversation from a previous message."

Exit code 132 = SIGILL (Illegal Instruction), which suggests a binary compatibility issue between the Claude Code process and Apple Silicon when spawned internally by the Desktop app.

Steps to reproduce

  1. Open Claude Desktop on Apple Silicon Mac
  2. Navigate to Cowork
  3. Start or attempt any conversation
  4. Error appears immediately, no response is generated

What I tried

  • Deleted the local-agent-mode-sessions folder from ~/Library/Application Support/Claude/
  • Deleted the Session Storage folder from the same directory
  • Restarted the app
  • After cleanup, error code changed from 1 to 132, confirming the session folders were corrupted/conflicting

What Should Happen?

Cowork should load and respond normally.

Error Messages/Logs

Steps to Reproduce

  1. Open Claude Desktop on Apple Silicon Mac
  2. Navigate to Cowork
  3. Start or attempt any conversation
  4. Error appears immediately, no response is generated

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

Claude 1.1617.0 (8d6345) 2026-04-09T16:10:15.000Z

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

This appears related to issues #39270 and #46161 reported by other users on Apple Silicon. The exit code 132 (SIGILL) is more specific than the generic code 1 and may help narrow down the root cause.

extent analysis

TL;DR

  • The issue may be resolved by updating or modifying the Claude Code process to ensure binary compatibility with Apple Silicon.

Guidance

  • Investigate the compatibility of the Claude Code process with Apple Silicon, as the SIGILL error suggests a binary compatibility issue.
  • Review the previous issues #39270 and #46161 to see if there are any common patterns or potential fixes that can be applied to this case.
  • Consider testing the Cowork feature on a different platform or architecture to isolate if the issue is specific to Apple Silicon.
  • Check if there are any available updates or patches for the Claude Code version 1.1617.0 that may address the compatibility issue.

Notes

  • The fact that the error code changed from 1 to 132 after cleaning up the session folders suggests that the issue may be related to a combination of factors, including binary compatibility and session data.
  • The issue being a regression and having worked in a previous version implies that a fix may involve reverting to a previous version or updating to a newer version that addresses the compatibility issue.

Recommendation

  • Apply workaround: Given the potential binary compatibility issue, a workaround may involve using a different version of the Claude Code process or modifying the existing process to ensure compatibility with Apple Silicon.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING