macOS 2.1.170 binary hangs before startup (_dyld_start), install.sh stuck at 'Setting up Claude Code'

Summary

Claude Code 2.1.170 for macOS (darwin-arm64, and also darwin-x64 under Rosetta) installs/downloads successfully but never starts. Even --version hangs with no stdout/stderr. The Linux build of 2.1.170 works for me on a separate Linux machine, so this appears specific to the macOS binary.

Environment

• macOS: 26.3.2 (Build 25D2140)
• Kernel: Darwin 25.3.0
• Machine: Apple M4 Pro, arm64
• Shell: zsh/bash
• Node/npm used for npm install: Node v25.9.0, npm 11.12.1
• Package manager path: /opt/homebrew

Affected version

• 2.1.170
• Official release manifest reports:
• latest endpoint: 2.1.170
• commit: 1cda84def004ef3a8f569f8e8284a153a6b98c3a
• build date: 2026-06-09T15:22:30Z
• darwin-arm64 sha256: e903646d8b7a31882a80ecd27569a27d8ac57b3708745f349709632c84117fdf
• darwin-x64 sha256: 914f23a70bbed5d9ae567e3e04b86206ed9971b371bc9baca3f79c8885bfddb4

Reproduction

1. npm install path

npm uninstall -g @anthropic-ai/claude-code
rm -rf /opt/homebrew/lib/node_modules/@anthropic-ai/claude-code
rm -f /opt/homebrew/bin/claude
npm cache clean --force
npm install -g --registry=https://registry.npmjs.org @anthropic-ai/claude-code@2.1.170
claude --version

Expected: prints 2.1.170 (Claude Code) quickly.

Actual: no output; command hangs until killed/timed out.

The installed binary checksum matches the official manifest:

shasum -a 256 /opt/homebrew/lib/node_modules/@anthropic-ai/claude-code/bin/claude.exe
# e903646d8b7a31882a80ecd27569a27d8ac57b3708745f349709632c84117fdf

2. official install.sh path

curl -fsSL https://claude.ai/install.sh | bash

Expected: completes installation.

Actual: hangs at:

Setting up Claude Code...

The child process is the downloaded binary running install:

~/.claude/downloads/claude-2.1.170-darwin-arm64 install

3. direct downloaded binary path

curl -fsSL -o /tmp/claude-2.1.170-darwin-arm64 \
  https://downloads.claude.ai/claude-code-releases/2.1.170/darwin-arm64/claude
chmod +x /tmp/claude-2.1.170-darwin-arm64
/tmp/claude-2.1.170-darwin-arm64 --version
/tmp/claude-2.1.170-darwin-arm64 install

Both commands hang with no stdout/stderr.

4. darwin-x64 under Rosetta

I also tried the darwin-x64 binary directly and via arch -x86_64; it also hangs on --version with no stdout/stderr.

Diagnostics

• file reports valid Mach-O binaries:

Mach-O 64-bit executable arm64
Mach-O 64-bit executable x86_64

• codesign --verify --deep --strict --verbose=4 reports the darwin-arm64 binary as valid on disk and satisfying its designated requirement.
• codesign -dv --verbose=4 shows:

Identifier=com.anthropic.claude-code
Authority=Developer ID Application: Anthropic PBC (Q6L2SF6YDW)
TeamIdentifier=Q6L2SF6YDW
Runtime Version=14.5.0
Timestamp=Jun 9, 2026 at 23:28:50

• Sampling a stuck claude --version process showed it sitting at _dyld_start, before reaching Claude Code application logic. No stdout/stderr is emitted.

Workaround

A previously installed 2.1.168 Claude Code binary still starts successfully on the same machine:

claude --version
# 2.1.168 (Claude Code)

So this looks like a regression in the macOS 2.1.170 binary or how macOS 26 validates/loads it, rather than a settings/auth/API issue.

Request

Could you please check whether the macOS 2.1.170 binaries have a loader/signing/packaging regression, especially on macOS 26 / Apple Silicon? A fixed 2.1.171+ build would be very helpful.