{"version":"2.1.317","anchor":"sandbox-refuses-when-a-denied-file-is-hard-linked-new-gate","canonical_anchor":"sandbox-refuses-when-a-denied-file-is-hard-linked-new-gate","heading":"Sandbox can refuse to run when a protected file has a second hard link","tier":"notice","area":"Sandbox","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/sandbox-refuses-when-a-denied-file-is-hard-linked-new-gate","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Sandbox can refuse to run when a protected file has a second hard link\n\nBehind a server switch, the sandbox refuses to start if a protected file has more than one hard link, blocking even dangerouslyDisableSandbox\n\n**Unclear.** What the check does when the server sends nothing is not settled, so it is unclear whether it runs for you by default.\n\n**What**\n\nThe sandbox, which limits what commands Claude runs can reach on your machine, has a new check. A hard link is a second name that points at the same file. If a file the sandbox is meant to keep off-limits has more than one hard link, the sandbox now fails to start with a message saying so. Until the extra link is removed, both of these are refused:\n\n- commands run inside the sandbox\n\n- running a command outside it with `dangerouslyDisableSandbox`\n\nThe check only runs when a server-controlled switch is on.\n\n**Why**\n\nA second name for a protected file could let a command reach it through the other path. If the check is on and you hit it, every shell command stays blocked until you remove the extra link.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}