Update command warns about PATH even when binary is accessible
Resolved 💬 3 comments Opened Jan 29, 2026 by the-michael-toy Closed Feb 1, 2026
Description
The claude update command warns about ~/.local/bin not being in PATH, even when the binary is clearly accessible and functioning (since the update command itself is running).
Current Behavior
$ claude update
Current version: 2.1.23
Checking for updates to latest version...
Warning: Native installation exists but ~/.local/bin is not in your PATH
Fix: Run: echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.zshrc then open a new terminal or run: source ~/.zshrc
Claude Code is up to date (2.1.23)
This warning appears on every claude update invocation.
Expected Behavior
The update command should not warn about PATH configuration when the binary is successfully being executed. Users may have valid alternative setups:
- Symlink from a directory already in PATH (e.g.,
~/bin/claude -> ~/.local/bin/claude) - Shell alias
- Direct invocation via full path
- Desktop shortcut or launcher
Suggested Fix
The check should verify "can I find and update myself" rather than "is ~/.local/bin specifically in PATH." If the binary is running, the user's setup is working.
Alternatively, provide a configuration option to suppress this warning for users who have intentionally chosen an alternative approach.
Environment
- macOS (Darwin)
- Native installation via installer
- Using symlink approach instead of modifying PATH
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗