{"version":"2.1.251","anchor":"sandbox-checks-the-task-output-directory-path-before-denying","canonical_anchor":"sandbox-checks-the-task-output-directory-path-before-denying","heading":"Sandbox checks the task output directory path before denying writes to it","tier":"notice","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/sandbox-checks-the-task-output-directory-path-before-denying","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Sandbox checks the task output directory path before denying writes to it\n\nThe sandbox verifies the task output path is real directories before locking it down.\n\n**What**\n\nBefore making the sandboxed task output directory read-only, Claude Code now verifies that every directory from your home directory down to it is a plain directory rather than a symlink or other special entry. If the chain does not check out, the read-only rule is skipped and a warning is logged instead of applying a rule to a path that may not be the one intended.\n\n**Details**\n\n- Always on; there is no flag.\n- The warning names the offending path: `[sandbox] task output dir chain is not plain directories; read-only deny skipped: ${Q}`.\n\n**Evidence**\n\n`[sandbox] task output dir chain is not plain directories; read-only deny skipped: ${Q}`\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}