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

Prompt hooks that time out are now logged

A prompt hook that times out is now logged and recorded instead of vanishing silently.

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

When a hook that runs on your prompt hits its time limit, Claude Code logs a warning naming the hook event and records a timeout event with the event name, the limit and the actual duration. Previously a timed-out prompt hook left no trace. The limit is still 30000ms unless the hook sets its own timeout.

Details
  • The evaluator stamps a start time and reports only when its own signal aborts while the session is still running, so ordinary session cancellation is not counted as a hook timeout.
Evidence

tengu_hook_prompt_timeout

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Names in the bundletimeout
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Confirmed since Anthropic's documentation has since written up timeout, on Batches. - `type: "timeout_error"` api/messages/batches see the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up timeout, on Batches.

See this entry in the whole of v2.1.232 →

Feedback