{"version":"2.1.280","anchor":"allowmanagedhooksonly-now-also-scopes-plugin-hooks","canonical_anchor":"allowmanagedhooksonly-now-also-scopes-plugin-hooks","heading":"allowManagedHooksOnly now also scopes plugin hooks","tier":"use","area":"Hooks","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/allowmanagedhooksonly-now-also-scopes-plugin-hooks","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### allowManagedHooksOnly now also scopes plugin hooks\n\nallowManagedHooksOnly setting now also restricts which plugin hooks can run\n\n**What**\n\nThe managed-settings option `allowManagedHooksOnly` (\"Run only the [hooks](\/docs\/en\/hooks) your organization deploys\") now covers plugin hooks too. When turned on, only hooks defined directly in managed settings, or hooks belonging to plugins that managed settings explicitly enable, are allowed to run. Hooks from plugins a user installed on their own are excluded, while Claude Code's own built-in features are exempt from this restriction.\n\n**Why**\n\nThis lets organizations lock down which hooks can execute more completely, closing a gap where a user-installed plugin's hooks could previously run even with `allowManagedHooksOnly` enabled.\n\n- Area: Hooks\n- Names: `allowManagedHooksOnly`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}