{"version":"2.1.275","anchor":"hooks-can-be-disabled-per-agent-via-settingshooksoff","canonical_anchor":"hooks-can-be-disabled-per-agent-via-settingshooksoff","heading":"Hooks can be disabled per-agent via settingsHooksOff","tier":"use","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/hooks-can-be-disabled-per-agent-via-settingshooksoff","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Hooks can be disabled per-agent via settingsHooksOff\n\nA new settingsHooksOff option can disable all hook execution for a given agent or subagent run\n\n**Unclear.** The finding doesn't say what user-facing setting or scenario sets `settingsHooksOff`, so how a user would trigger this isn't clear.\n\n**What**\n\nSeveral internal functions responsible for assembling and running hooks (user-configured scripts that run at specific points, including agent-context hooks) now check for a new `settingsHooksOff` option. When it's set to `true`, they short-circuit and skip running any hooks entirely for that agent or subagent run.\n\n**Why**\n\nThis provides a way to fully disable hook execution for a specific run, which is useful for situations where hooks shouldn't fire, such as isolated or internal subagent invocations.\n\n- Area: Hooks\n- Names: `settingsHooksOff`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}