{"version":"2.1.300","anchor":"hooks-report-a-different-reason-when-managed-settings-have-n","canonical_anchor":"hooks-report-a-different-reason-when-managed-settings-have-n","heading":"Hooks now give a separate reason when managed settings haven't loaded yet","tier":"notice","area":"Hooks","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/hooks-report-a-different-reason-when-managed-settings-have-n","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Hooks now give a separate reason when managed settings haven't loaded yet\n\nIf your organization's managed settings haven't been read yet, Claude Code now says it can't yet tell whether hooks are allowed\n\n**What**\n\nHooks are commands Claude Code runs automatically at set moments. When hooks are off, Claude Code explains why. It now has a separate explanation for when your organization's managed settings have not been read yet. Managed settings are settings your organization controls. Until they are read, Claude Code cannot know whether they allow hooks, and it says so.\n\nThis case is checked before `disableAllHooks`. Before, Claude Code went from the safe mode check straight to the `disableAllHooks` check.\n\n**Why**\n\nEarly in startup, before managed settings are read, the message shows the real reason hooks are not running instead of a wrong one.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: both\n- Heads-up: no"}