claude-code - 💡(How to fix) Fix [BUG] npm install now ships Bun binary (v2.1.126) — npm workaround for non-AVX VPS is dead, no upgrade path [2 comments, 2 participants]

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?

As of version 2.1.x, npm install -g @anthropic-ai/claude-code ships a Bun ELF binary (claude.exe) instead of a Node.js-based entry point. This means the npm installation path — the documented workaround for non-AVX environments — no longer works.

I am a paying subscriber using Claude Code professionally for server administration and development across multiple dedicated servers and VPS instances (OpenStack, Proxmox KVM). I was forced to downgrade to version 2.0.62, which is the last version that actually runs on Node.js. I am now frozen on an outdated version with no upgrade path.

This affects all common virtualized environments: OpenStack, Proxmox KVM, Docker, LXC — any platform where AVX is not exposed to guests, which is the default for the vast majority of VPS providers and hypervisors worldwide.

Previous issues (#19904, #19967, #19981, #20611) all recommended npm install as the workaround. That workaround is now dead.

Bun itself publishes baseline builds without AVX dependency. The fix is straightforward.

What Should Happen?

One of the following:

1. npm install -g @anthropic-ai/claude-code should install a version that runs on Node.js (as it did up to v2.0.62), OR
2. The shipped Bun binary should be a baseline build without AVX dependency (Bun officially provides these), OR
3. Runtime CPU detection should select the appropriate binary automatically

Users on virtualized infrastructure should not be locked out of updates. "Upgrade your CPU" is not actionable for VPS customers.

Error Messages/Logs

============================================================
Bun v1.3.14 (0a466a11) Linux x64 (baseline)
Linux Kernel v6.1.0 | glibc v2.36

Args: "claude" "--resume"
Features: jsc no_avx2 no_avx standalone_executable claude_code
Builtins: "bun:main"

Elapsed: 7956ms | User: 6200ms | Sys: 1758ms
RSS: 4.56GB | Peak: 4.03GB | Commit: 4.56GB

CPU lacks AVX support. Please consider upgrading to a newer CPU.
panic(main thread): Segmentation fault at address 0x3063D000000
oh no: Bun has crashed. This indicates a bug in Bun, not your code.

Steps to Reproduce

1. Use any Linux VPS or VM where AVX is not available (OpenStack, Proxmox with default kvm64 CPU type, Docker, LXC — this is the default for most virtualized environments)
2. Install Node.js 18+ via nvm
3. Run: npm install -g @anthropic-ai/claude-code (installs v2.1.126)
4. Verify the binary: file $(which claude) → shows ELF binary (Bun), not a Node.js script
5. Run: claude --version → Segmentation fault / SIGILL

Workaround: npm install -g @anthropic-ai/[email protected] — last version using Node.js runtime. But this locks the user out of all updates.

Claude Model

Opus

Is this a regression?

No, this never worked

Last Working Version

2.0.62

Claude Code Version

2.1.126 (crashes) / 2.0.62 (works)

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

Other

Additional Information

Impact: I use Claude Code daily across multiple production servers for Laravel development, server administration, email infrastructure, and database operations. Being locked to v2.0.62 means I am paying for a product I cannot fully use.

Key facts:

• This is not exotic hardware. The majority of VPS instances worldwide do not expose AVX.
• OpenStack, Proxmox (default kvm64), Docker, LXC — all affected by default.
• Bun publishes official baseline builds without AVX: https://github.com/oven-sh/bun/releases
• Tested on Debian 12, Debian 13, Ubuntu 22.04, Ubuntu 24.04 — same result everywhere.
• The npm package at v2.1.126 contains bin/claude.exe which is a Bun ELF binary, not a Node.js entry point.
• DISABLE_AUTOUPDATER=1 is required to prevent auto-update back to the broken version.

Related issues: #19904, #19967, #19981, #20611, #18423