You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
File SystemArea: what it touches
Bug FixesKind: in v2.1.265,
Bug FixesSection of the release
Unclear The finding marks this fallback path itself as 'unverified', so how reliable it is in practice is unclear.
What
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.
Why
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.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe finding marks this fallback path itself as 'unverified', so how reliable it is in practice is unclear.
