{"version":"2.1.300","anchor":"hooks-held-until-organization-managed-settings-answer","canonical_anchor":"hooks-held-until-organization-managed-settings-answer","heading":"Hooks wait for your organisation's managed settings before running","tier":"notice","area":"Hooks","scope":"both","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/hooks-held-until-organization-managed-settings-answer","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Hooks wait for your organisation's managed settings before running\n\nStartup hooks and plugin hooks now wait for organisation managed settings, and are skipped with a warning if those never arrive\n\n**Unclear.** Whether this waiting applies to every setup or only to some is not stated.\n\n**What**\n\nHooks are your own commands that Claude Code runs at set moments, such as when a session starts. Managed settings are settings your organisation's administrator sets for everyone. Claude Code now holds back these until the organisation's managed settings have answered:\n\n- hooks that run at startup\n\n- command sources\n\n- hooks that come from plugins\n\nIf the managed settings never answer, Claude Code shows a warning and does not run the hooks. A failure because the organisation did not answer is treated the same as a policy block.\n\n**Why**\n\nIf your organisation manages Claude Code, hooks may start a little later, or not run at all, when its settings cannot be reached at startup. This stops hooks from running before the organisation's rules are known.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: both\n- Heads-up: yes"}