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 ·

Hook errors caused by Claude Code itself no longer send you to /hooks

When an internal fault stops Claude Code from finding the hooks for a call, the message now says nothing in the session can fix it

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

Hooks are commands set up to run at set moments, such as before or after Claude uses a tool. Before an action, Claude Code works out which hooks apply to it. If that lookup fails because of a fault inside Claude Code, the action is blocked. The block message now says the fault is in Claude Code, that nothing in this session can fix it, and that a retry would be blocked the same way.

Before, the message always said to retry with a different input and to check your hooks in /hooks or in your settings.

Why

The old advice was misleading when the cause was an internal fault. Your hook setup was not the problem, so checking /hooks would not help.

See this entry in the whole of v2.1.300 →

Feedback