[BUG] Constant warning that "claude symlink points to invalid binary"
Status Fixed / completed
Maintainer reply ✓ Yes — ant-kurt
Activity 5 comments · opened Sep 19, 2025 · closed Sep 24, 2025
💡 Likely answer: A maintainer (ant-kurt, collaborator)
responded on this thread — see the highlighted reply below.
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?
Every time I start claude I get this warning:
● Claude symlink points to invalid binary: ../lib/node_modules/@anthropic-ai/claude-code/cli.js
I haven't been able to find anything online about what would cause this, or how to fix it.
I start claude with ~/.local/bin/claude which is a (relative) symlink to ~/.local/lib/node_modules/@anthropic-ai/claude-code/cli.js
What Should Happen?
I shouldn't get this warning on startup
Error Messages/Logs
● Claude symlink points to invalid binary: ../lib/node_modules/@anthropic-ai/claude-code/cli.jsSteps to Reproduce
- On linux configure npm prefix to be ~/.local:
npm config prefix ~/.local - Install claude with `npm install -g @anthropic-ai/claude-code
- start claude
- see warning
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
not sure
Claude Code Version
1.0.119 (Claude Code)
Platform
Anthropic API
Operating System
Ubuntu/Debian Linux
Terminal/Shell
Other
Additional Information
_No response_
5 Comments
Can you check your
~/.claude.jsonto see "installMethod"?@ant-kurt In my case
installMethodvalue isunknown.For context:
npmprefix to point to$HOME/.local(npm config set prefix $HOME/.local) as a way to avoid a dangling$HOME/node_modules.npm install -g @anthropic-ai/claude-codeto install claude (which installs it in$HOME/.local/lib/node_modules/@anthropic-ai/claude-codeExcept for the warning, Claude appears to be working just fine.
My installMethod is also
unknownThis should be fixed in the next release.
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.