{"version":"2.1.317","anchor":"symlink-guard-messages-now-cover-windows-junctions","canonical_anchor":"symlink-guard-messages-now-cover-windows-junctions","heading":"Protection against linked paths now covers Windows junctions","tier":"notice","area":"Windows","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/symlink-guard-messages-now-cover-windows-junctions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Protection against linked paths now covers Windows junctions\n\nClaude Code's guard on protected paths now catches Windows junctions as well as symlinks, and its messages say so\n\n**What**\n\nA symlink is a file that points to another location. A Windows junction does the same for folders on Windows. Claude Code already guards protected paths against symlinks. The check now tests whether the file itself is a link of either kind, and its messages are:\n\n- \"This path is a link (a symlink or a Windows junction).\"\n\n- \"The enclosing .claude directory is a link (a symlink or a Windows junction).\"\n\nBefore, the message said only that the path was a symlink.\n\n**Why**\n\nA junction now triggers the same protection a symlink did, so it cannot be used to reach a protected path.\n\n- Area: Windows\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}