You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
File AccessArea: what it touches
ImprovementsKind: in v2.1.281,
ImprovementsSection of the release
What
Claude Code screens paths before reading or registering them. Screening has a new outcome, screened_unvettable_chain: a path whose chain of parent folders and symbolic links (shortcuts that point to another location) cannot all be resolved is rejected before the file system is touched, and reported as bad.
read_file refuses such paths.
register_repo_root, which adds a working folder to a session, refuses them with the reason unvettable_chain. Its error now reads "target is a network path, an obfuscated spelling, or a path whose directories and symbolic links could not all be examined, which cannot be registered". Before, it named only network paths and obfuscated spellings.
Why
This is a safety hardening step. Some unusual paths, for example chains through symbolic links or network (UNC) paths, that used to be read or registered will now be refused, so programs using the SDK to register folders may get an error on paths that worked before.
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 does not say which paths are screened or what happens after one is reported.
