{"version":"2.1.281","anchor":"path-resolution-gains-a-screen-mode-that-follows-every-sym","canonical_anchor":"path-resolution-gains-a-screen-mode-that-follows-every-sym","heading":"Path resolution gains a 'screen' mode that follows every symlink hop","tier":"internal","area":"File Access","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/path-resolution-gains-a-screen-mode-that-follows-every-sym","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Path resolution gains a 'screen' mode that follows every symlink hop\n\nPath checks gain a 'screen' mode that follows up to 8 symlink hops and reports failure if any cannot be followed\n\n**Unclear.** The finding does not say which feature uses the new 'screen' mode.\n\n**What**\n\nClaude Code has a function that works out the real location of a file path. It now runs in one of two modes:\n\n- `permission`, which keeps the old behaviour, including its fallback when the path is too long or access is denied\n\n- `screen`, a new mode that follows up to 8 intermediate symlinks (shortcuts that point to another file or folder) and reports the path as unresolved if any hop cannot be followed\n\n**Why**\n\nA chain of shortcuts cannot hide where a path really leads: if any step in the chain cannot be checked, the path is treated as unresolved instead of being accepted.\n\n- Area: File Access\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}