{"version":"2.1.304","anchor":"sandbox-linux-where-a-write-lands-through-symlinks-is-resol","canonical_anchor":"sandbox-linux-where-a-write-lands-through-symlinks-is-resol","heading":"Linux sandbox now works out where a write through a symlink really lands","tier":"notice","area":"Sandbox","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/sandbox-linux-where-a-write-lands-through-symlinks-is-resol","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Linux sandbox now works out where a write through a symlink really lands\n\nOn Linux, the sandbox now follows symlinks to see where a write would land, and blocks the link when it cannot tell\n\n**What**\n\nThe sandbox is the restricted area Claude Code can run commands in, so they cannot touch files outside the places they are allowed to. On Linux, when a write goes through a symlink (a file that points to another file or folder), the sandbox now follows the chain of links to see where the write would actually end up.\n\nIf it cannot work that out, it shows a warning saying where the write would land cannot be settled, and it blocks the link instead of allowing it.\n\nFiles opened inside the sandbox can now also be written to. A write with a negative or fractional offset, length or position is refused with an error.\n\n**Why**\n\nThis makes the Linux sandbox handle folder layouts that use symlinks, both when the sandbox starts up and when files are written.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}