v2.1.152 native installer build hangs indefinitely on ARM aarch64 Linux

Environment

• Version: 2.1.152 (broken). 2.1.149 and 2.1.150 work fine.
• Install method: native installer (~/.local/share/claude/versions/<v>)
• OS: Ubuntu 22.04 Desktop
• Arch: ARM aarch64 (Apple Silicon Mac running Ubuntu under Parallels)
• Binary: ELF 64-bit LSB executable, ARM aarch64, dynamically linked, for GNU/Linux 3.7.0, ~239 MB

Symptom

claude hangs forever with no output. No prompt, no error, no debug output — even with flags that shouldn't touch auth/network/MCP/config:

\\\`
\$ timeout 5 claude --version; echo "exit=\$?"
exit=124

\$ timeout 10 claude --debug 2>&1 | tee claude-startup.log
Terminated
(claude-startup.log is empty)
\\\`

\~/.claude/\ does not exist, so no user config, MCP servers, or auth state is involved. The hang is in the binary itself before any output is produced.

Reproduction

\\\`bash
timeout 5 ~/.local/share/claude/versions/2.1.152 --version

hangs, killed by timeout (exit 124)

timeout 5 ~/.local/share/claude/versions/2.1.150 --version

prints "2.1.150 (Claude Code)" instantly

timeout 5 ~/.local/share/claude/versions/2.1.149 --version

prints "2.1.149 (Claude Code)" instantly

\\\`

All four versions (148/149/150/152) exist side-by-side in \~/.local/share/claude/versions/\, downloaded by the native auto-updater. Only 2.1.152 is broken.

Workaround

Re-point the symlink to a working version and disable the auto-updater:

\\\bash
ln -sf ~/.local/share/claude/versions/2.1.150 ~/.local/bin/claude
export DISABLE_AUTOUPDATER=1
\\\

Impact

Anyone on ARM aarch64 Linux who auto-updates to 2.1.152 ends up with a CLI that silently hangs on every invocation, including \--version\ and \--help\. Hard to diagnose because no error output is emitted.