Path safety checks now fall back to a shared-ancestor path if the OS blocks realpath resolution
Claude Code resolves file paths using a system call that also checks whether a path is actually a symlink pointing somewhere unexpected. When that system call fails with a permissions error (EPERM or EACCES), Claude Code now tries a fallback: it computes the common ancestor directory between the current working directory and the 'launch' path (the directory Claude Code was started from), and re-runs its symlink-safety checks using that ancestor path instead of giving up immediately.
Previously a permissions error during this check would simply fail. The fallback lets Claude Code keep working in more restrictive environments instead of erroring out.
The finding marks this fallback path itself as 'unverified', so how reliable it is in practice is unclear.