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 ·

Command hooks can now be stopped by their configured timeout

Command hooks run through this path now stop when their configured timeout in seconds runs out

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

Unclear It is unclear whether this applies to every command hook or only to one particular way of running them.

What

A hook is a command you configure to run automatically at certain points. Each hook can have a timeout setting, measured in seconds.

Before, command hooks in this path ran with no timeout of their own and stopped only if the whole operation was cancelled. Now the hook's timeout is applied too, so the hook is stopped when either the time runs out or the operation is cancelled.

Why

A slow or stuck hook can no longer run past the timeout you set for it here.

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 unclear whether this applies to every command hook or only to one particular way of running them.

See this entry in the whole of v2.1.300 →

Feedback