{"version":"2.1.281","anchor":"symlink-resolution-now-refuses-network-target-loops-instead","canonical_anchor":"symlink-resolution-now-refuses-network-target-loops-instead","heading":"Symlink resolution now refuses network-target loops instead of returning raw paths","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/symlink-resolution-now-refuses-network-target-loops-instead","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Symlink resolution now refuses network-target loops instead of returning raw paths\n\nResolving shortcut-style file links now stops on long loops or network targets instead of passing the raw path through\n\n**Unclear.** The finding does not say which cases return the original path and which return nothing.\n\n**What**\n\nA symlink is a file that points to another file or folder. Claude Code follows these links to find the real location. The code that does this now handles two cases differently:\n\n- A chain of links that goes past 64 hops, which usually means a loop.\n\n- A link whose target sits on a network location.\n\nIn these cases it now returns the original path or nothing, rather than passing the raw result through. When the resolver has been asked to surface targets that go up a folder with `..`, it now raises an error instead.\n\n**Why**\n\nLinks that loop forever or point off to network locations no longer slip through as if they were ordinary resolved paths."}