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

Claude Code v2.1.300 ·

Claude Code now handles hooks that plugins hold back separately

Hook checks can now look only at hooks that plugins hold back, and plugin hook matching now handles those held hooks explicitly

Under the hood Internal Changes
JSON All of v2.1.300
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
HooksArea: what it touches
Internal ChangesKind: in v2.1.300,
Internal ChangesSection of the release

Unclear It is not clear what makes a plugin hook held, or whether held hooks now fire differently for users.

What

Hooks are commands Claude Code runs automatically at set moments, for example before a tool is used. Plugins can supply hooks, and some of those hooks can be held back.

Claude Code's check for whether any hooks exist can now be asked to consider held hooks only. In that mode it no longer stops early when nothing is being held. The way plugin hooks are matched was also reworked, so hooks a plugin holds back are now dealt with explicitly.

Why

This can change which hooks fire when a plugin holds some of them back.

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 doubtIt is not clear what makes a plugin hook held, or whether held hooks now fire differently for users.

See this entry in the whole of v2.1.300 →

Feedback