{"version":"2.1.281","anchor":"path-resolver-gives-up-on-a-new-sentinel","canonical_anchor":"path-resolver-gives-up-on-a-new-sentinel","heading":"Path resolver gives up on a new sentinel","tier":"internal","area":"File Access","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/path-resolver-gives-up-on-a-new-sentinel","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Path resolver gives up on a new sentinel\n\nThe file path resolver now returns a path unchanged when its lookup gives back a special marker value\n\n**Unclear.** The finding does not say what situation produces the marker value.\n\n**What**\n\nClaude Code has a resolver that works out where a file path really points, following symlinks (shortcuts to other files or folders). When its lookup now returns a particular marker value, the resolver stops and hands back the original path unchanged, treating it as neither a symlink nor its final form.\n\n**Why**\n\nIn that case the path is used exactly as given rather than being rewritten.\n\n- Area: File Access\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}