{"version":"2.1.300","anchor":"managed-settings-startup-message-distinguishes-unloaded-hook","canonical_anchor":"managed-settings-startup-message-distinguishes-unloaded-hook","heading":"Startup warning now says when invalid managed settings drop security hooks","tier":"notice","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/managed-settings-startup-message-distinguishes-unloaded-hook","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Startup warning now says when invalid managed settings drop security hooks\n\nIf invalid managed settings include PreToolUse or PermissionRequest hooks, the startup message now says those hooks are not loaded\n\n**What**\n\nManaged settings are settings an organization's administrator pushes to its devices. When they contain invalid entries, Claude Code shows a message at startup. Before, that message only said there were invalid entries and that the remaining valid policies were still enforced.\n\nNow, when the invalid entries include `PreToolUse` or `PermissionRequest` hooks, the message says those hooks are NOT loaded and asks for each entry to be fixed or removed. Hooks are commands that run automatically at set points; a `PreToolUse` hook runs before a tool call and can block it. This is a separate case from managed settings failing to load at all.\n\n**Why**\n\nAdministrators can now see that hooks meant to guard tool use are not running, instead of assuming they are still enforced.\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}