Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.300entry #52

Claude Code v2.1.300 ·

Changes to how organisation-managed hooks combine with other hooks

Hook selection for organisation-managed setups now includes policy hooks delivered by plugins, and hooks that continue on failure can be marked contested

You'll notice Improvements
JSON All of v2.1.300
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
HooksArea: what it touches
ImprovementsKind: in v2.1.300,
ImprovementsSection of the release

Unclear What being marked contested changes about whether a hook that continues on failure actually lets the action go ahead is not shown.

What

Hooks 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:

  • 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.
  • When Claude Code picks only managed hooks, or excludes them, it now also counts policy hooks delivered through plugins.
  • A plugin's hooks can be treated as managed when the plugin passes a check.
  • Hook failure results outside cloud sessions now also depend on a further check.
Why

This affects how hooks set by an organisation combine with hooks you or your plugins add.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhat being marked contested changes about whether a hook that continues on failure actually lets the action go ahead is not shown.

See this entry in the whole of v2.1.300 →

Feedback