{"version":"2.1.287","anchor":"sandbox-filesystem-off-availability-now-linux-specific","canonical_anchor":"sandbox-filesystem-off-availability-now-linux-specific","heading":"Sandbox reports its file restrictions unavailable in different cases, now Linux-specific","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/sandbox-filesystem-off-availability-now-linux-specific","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Sandbox reports its file restrictions unavailable in different cases, now Linux-specific\n\nOn Linux, the sandbox's file protection is reported unavailable when a platform check passes, and in locked mode when it is disabled\n\n**Unclear.** It is not clear what the Linux platform check tests.\n\n**What**\n\nThe sandbox is a protective boundary that limits what commands run by Claude Code can touch, including which files. Claude Code checks whether the file part of that protection is available, and it now reports it as unavailable in these cases:\n\n- on Linux, when a platform check passes\n\n- in locked mode, when the sandbox's filesystem setting is disabled\n\nBefore, it reported the file protection unavailable in any mode other than the personal one whenever the filesystem setting was disabled.\n\n**Why**\n\nThis changes when the sandbox's file restrictions are offered, especially on Linux, so the options you see there may differ from before.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}