Follow Discord
Sweep 25 Sep 2026 · 19:33Z Build v2.1.283 504 read Stable v2.1.274 Latest v2.1.283 Next v2.1.283 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.280 ·

Hooks gain a hard deadline (cutAt) in addition to their time budget

Hooks now carry a hard cutoff time (cutAt) alongside their existing time budget, and can be re-armed

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

What

  • Hooks (scripts that run automatically at certain points, like before a tool call) now carry a cutAt value: an absolute deadline, separate from the existing budgetMs time budget.
  • This cutAt value is passed through the internal event object used to dispatch a hook, alongside the existing id, event, payload, environments, leftOut, origin, hookOrigin, raise, and floors fields.
  • The hook chain runner and its error handling now take this deadline into account, and a hook's per-run timeout can be re-armed (reset) with a new rearm() mechanism.

Why

Giving hooks a hard deadline on top of a soft time budget lets Claude Code enforce a firm cutoff for how long a hook chain can run, while still allowing individual timeouts to be reset when appropriate.

Read from
Names in the bundlecutAt
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 cutAt field represents or is used for is not stated in the finding.

See this entry in the whole of v2.1.280 →

Feedback