{"version":"2.1.280","anchor":"disableallhooks-setting-description-clarified-to-scope-hooks","canonical_anchor":"disableallhooks-setting-description-clarified-to-scope-hooks","heading":"disableAllHooks setting description clarified to scope hooks only","tier":"use","area":"Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/disableallhooks-setting-description-clarified-to-scope-hooks","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### disableAllHooks setting description clarified to scope hooks only\n\ndisableAllHooks setting now explains it only turns off custom hooks and statusLine, not Claude Code's built-in features\n\n**What**\n\nThe description for the `disableAllHooks` policy setting has been expanded to spell out exactly what it covers: hooks defined in settings files, hooks added by installed plugins, and `statusLine` execution. It now explicitly states that features built into Claude Code are not hooks in this sense and keep working, since each of those has its own separate switch.\n\n**Why**\n\nThis clears up potential confusion about the scope of `disableAllHooks`, making clear it's a switch for custom\/plugin hooks and the status line specifically, not a master switch for every Claude Code feature.\n\n- Area: Settings\n- Names: `disableAllHooks`\n- Tier: Use it now\n- Useful: 2\/5\n- Signal: 1\/5"}