[BUG] v2.1.123 crashes on startup with "Module not found ''" (Linux x86-64 baseline)
Status Fixed / completed
Reported on v2.1.123
Maintainer reply None cached
Workaround ✓ Mentioned in description ↑
Activity 3 comments · opened Apr 29, 2026 · closed Apr 30, 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?
After the automatic update to v2.1.123, Claude Code fails to start
with the following error:
error: Module not found ''
Bun v1.3.14 (Linux x64 baseline)
The module name in the error is blank (whitespace only), suggesting a
bundling/packaging issue in the released binary rather than a
missing user dependency.
Environment
- OS: Ubuntu 22.04, Linux 6.8.0-59-generic, x86-64
- Binary: standalone ELF (~/.local/share/claude/versions/2.1.123, 247
MB)
- Embedded Bun: v1.3.14 (Linux x64 baseline)
Workaround - not complete
Manually re-pointing the symlink to the previous version:
ln -sf ~/.local/share/claude/versions/2.1.122 ~/.local/bin/claude
auto updater keeps rewriting the link to the new (and broken) version.
What Should Happen?
Claude Code should start normally (as v2.1.122 does on the same machine).
Error Messages/Logs
error: Module not found ''
Bun v1.3.14 (Linux x64 baseline)
Steps to Reproduce
- Allow auto-update from v2.1.122 → v2.1.123
- Run claude (or the binary directly)
- See the error above immediately, before any output
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
2.1.122
Claude Code Version
2.1.123
Platform
Anthropic API
Operating System
Ubuntu/Debian Linux
Terminal/Shell
Other
Additional Information
_No response_
3 Comments
Found 2 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Not a duplicate - new issue, relevant only on the newest version (and very different error messages).
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.