2.1.97 binary gets SIGKILL'd on macOS 26.3 (Tahoe beta)
Resolved 💬 3 comments Opened Apr 9, 2026 by avilla-junior Closed Apr 13, 2026
Environment
- macOS: 26.3 (Tahoe beta, Build 25D125)
- Architecture: arm64
- Affected version: 2.1.97 (203,606,768 bytes, signed Mar 25 2026)
- Working version: 2.1.96
Description
The claude binary at version 2.1.97 is killed with SIGKILL (exit code 137) on macOS 26.3 Tahoe beta. Running claude --version immediately exits with 137. The same binary executed from /tmp also fails.
Version 2.1.96 runs fine on the same machine.
Steps to Reproduce
- Install Claude Code on macOS 26.3 (Tahoe beta)
- Run
claude --version - Observe exit code 137 (SIGKILL)
Workaround
Rolling back to 2.1.96 resolves the issue:
ln -sf ~/.local/share/claude/versions/2.1.96 ~/.local/bin/claude
Additional Context
- The 2.1.97 binary is code-signed by Anthropic (Team ID:
Q6L2SF6YDW) with Hardened Runtime spctl -areports:rejected (the code is valid but does not seem to be an app)— but this is expected for a CLI tool and is the same result for 2.1.96- The kill happens immediately on invocation, suggesting a kernel/security policy block rather than a runtime crash
- This also affects third-party apps (e.g. Conductor) that bundle their own copy of the
claudebinary - The 2.1.96 binary (199MB) and 2.1.97 binary (203MB) differ in size, suggesting a meaningful build difference between them
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗