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.301 ·

Matched hooks now go through an extra check tied to managedHooksOnly

After Claude Code picks which hooks apply, it now runs one more check that is told whether managedHooksOnly is set

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

Unclear What the new check does with the matched hooks, and whether it can change which hooks run, is not shown.

What

Hooks are commands Claude Code runs automatically at set points, such as before or after it uses a tool. After Claude Code works out which hooks match the current moment, it now passes those hooks to an additional check, along with whether the managedHooksOnly option is set. Before, the matched hooks were used directly with no further step.

Why

If you use managedHooksOnly, there is now one more step between matching a hook and running it.

Read from
Names in the bundlemanagedHooksOnly
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 the new check does with the matched hooks, and whether it can change which hooks run, is not shown.

See this entry in the whole of v2.1.301 →

Feedback