{"version":"2.1.287","anchor":"sandboxed-project-hook-wrap-is-verified-more-strictly","canonical_anchor":"sandboxed-project-hook-wrap-is-verified-more-strictly","heading":"Sandboxed project hooks are checked more strictly before they run","tier":"notice","area":"Hooks","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/sandboxed-project-hook-wrap-is-verified-more-strictly","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Sandboxed project hooks are checked more strictly before they run\n\nA sandboxed project hook now runs only if Claude Code confirms it is a deny-by-default sandbox launch; otherwise it is skipped and an error is logged\n\n**What**\n\nA hook is a command that Claude Code runs automatically at set points, for example before or after it uses a tool. A project hook is one defined in a project's own settings. When Claude Code wraps a project hook in a sandbox (a restricted environment that limits what the command can reach), it now checks that the result really is a deny-by-default sandbox launch. Deny-by-default means everything is blocked unless it is explicitly allowed.\n\nIf the check fails, the hook is not run, and the failure is logged at error level. The earlier check looked only at whether the wrapped command began with a fixed profile prefix. That check has been replaced by the new one.\n\n**Why**\n\nThis is a security hardening step. A project hook that is meant to run inside a strict sandbox will not run at all unless that sandbox is confirmed to be in place.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5"}