[BUG] Continue support for older CPUs via npm
Resolved 💬 6 comments Opened Jan 22, 2026 by vn6295337 Closed Jan 22, 2026
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
Bug Description
My Chromebook's CPU is an Intel Celeron N3350 with no AVX support. So, ran into issue while installing, so re-installed it using npm.
Environment Info
- Platform: linux
- Terminal: xterm-256color
- Version: 2.1.15
- Feedback ID: a058ed73-08e0-4164-8358-5622ac4ed2ae
What Should Happen?
Please continue support npm for older CPUs
Error Messages/Logs
Bun v1.3.6 (d530ed99) Linux x64 (baseline) Linux Kernel v6.6.76 | glibc v2.36 CPU: sse42 popcnt Args: "claude" Features: Bun.stderr(2) Bun.stdin(2) Bun.stdout(2) fetch(13) jsc no_avx2 no_avx spawn(18) standalone_executable Builtins: "bun:main" "node:assert" "node:async_hooks" "node:buffer" "node:child_process" "node:constants" "node:crypto" "node:domain" "node:events" "node:fs" "node:fs/promises" "node:http" "node:https" "node:module" "node:net" "node:os" "node:path" "node:path/posix" "node:path/win32" "node:perf_hooks" "node:process" "node:querystring" "node:stream" "node:timers/promises" "node:tls" "node:tty" "node:url" "node:util" "node:zlib" "node:worker_threads" "undici" "ws" "node-fetch" "node:inspector" "node:http2" "node:diagnostics_channel" Elapsed: 9689ms | User: 5671ms | Sys: 2812ms RSS: 1.21GB | Peak: 0.41GB | Commit: 1.21GB | Faults: 42 | Machine: 2.89GB CPU lacks AVX support. Please consider upgrading to a newer CPU. panic(main thread): Illegal instruction at address 0x4001FB4 oh no: Bun has crashed. This indicates a bug in Bun, not your code.
Steps to Reproduce
claude install in Intel Celeron N3350 or earlier
Claude Model
Opus
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.1.15 (Claude Code)
Platform
Other
Operating System
Ubuntu/Debian Linux
Terminal/Shell
Xterm
Additional Information
_No response_
This issue has 6 comments on GitHub. Read the full discussion on GitHub ↗