{"version":"2.1.300","anchor":"hook-onfailure-continue-contested-marking-and-managed-hook","canonical_anchor":"hook-onfailure-continue-contested-marking-and-managed-hook","heading":"Changes to how organisation-managed hooks combine with other hooks","tier":"notice","area":"Hooks","scope":"both","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/hook-onfailure-continue-contested-marking-and-managed-hook","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Changes to how organisation-managed hooks combine with other hooks\n\nHook selection for organisation-managed setups now includes policy hooks delivered by plugins, and hooks that continue on failure can be marked contested\n\n**Unclear.** What being marked contested changes about whether a hook that continues on failure actually lets the action go ahead is not shown.\n\n**What**\n\nHooks are actions that run automatically at set points while Claude Code works. Some are managed, meaning an organisation's administrator sets them. This release changes how hooks from different sources are combined:\n\n- A hook set to carry on after a failure (an `onFailure` value of `continue`) can now be marked as contested when a hook from another source is also in play.\n\n- When Claude Code picks only managed hooks, or excludes them, it now also counts policy hooks delivered through plugins.\n\n- A plugin's hooks can be treated as managed when the plugin passes a check.\n\n- Hook failure results outside cloud sessions now also depend on a further check.\n\n**Why**\n\nThis affects how hooks set by an organisation combine with hooks you or your plugins add.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: both\n- Heads-up: yes"}