Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.265 ·

Hook dispatch events gain a 'raise' field

Internal hook dispatch events gained a new 'raise' field, purpose unclear

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

Unclear What the raise field actually controls or affects is not shown by the evidence.

What

The internal machinery that dispatches hooks (scripts or commands that run automatically at certain points, such as before or after a tool runs) now passes an extra raise value alongside the existing id, event, payload, environments, and origin fields when invoking a hook module's dispatch function.

Why

This is an internal plumbing change. The evidence doesn't show what raise controls or what a hook author would observe differently.

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 `raise` field actually controls or affects is not shown by the evidence.

See this entry in the whole of v2.1.265 →

Feedback