{"version":"2.1.302","anchor":"settings-hook-block-message-now-names-repo-settings","canonical_anchor":"settings-hook-block-message-now-names-repo-settings","heading":"Blocked-hook message now mentions repository settings as well as organization ones","tier":"notice","area":"Hooks","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/settings-hook-block-message-now-names-repo-settings","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### Blocked-hook message now mentions repository settings as well as organization ones\n\nThe message shown when a settings hook is blocked now says it came from the organization's or the repo's settings\n\n**What**\n\nA hook is a command that Claude Code runs automatically at a set point, such as before a tool runs. The message shown when a hook defined in settings is blocked used to refer to \"their organization's managed settings\". It now says \"their organization's or their repo's settings\", so it also covers settings stored in the repository (the project folder).\n\n**Why**\n\nIf a hook is blocked by settings in your project rather than by your organization, the message now points to the right place.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: both\n- Heads-up: no"}