[BUG] Installer/updater recreates ~/.local/bin/claude as an absolute symlink, breaking on NFS-mounted homes

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?

On every install/update, Claude Code (re)creates ~/.local/bin/claude as an absolute symlink pointing at the resolved binary path, e.g.:

/exports/homes/alexis/.local/bin/claude -> /exports/homes/alexis/.local/share/claude/versions/2.1.216

When $HOME (or ~/.local) is NFS-mounted (e.g. <nfs-server>:/exports/homes/alexis mounted on nn NFS client as /home/alexis - a common setup), an absolute symlink baked to one client's view of the path breaks on NFS clients.

Note that this is not the same issue as 74738.

What Should Happen?

A relative symlink (e.g. /exports/homes/alexis/.local/bin/claude -> ../share/claude/versions/2.1.216) would resolve correctly regardless of where the NFS export is mounted.

Error Messages/Logs

Steps to Reproduce

following auto-upgrade run claude.

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.216 (Claude Code)

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

Xterm

Additional Information

_No response_