A prompt hook that times out is now logged and recorded instead of vanishing silently.
What's wrong with this entry?
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.
- 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.
tengu_hook_prompt_timeout
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.248
Session-end hook timeout parsing simplified
Both mention timeout hook
-
v2.1.234
SessionEnd hooks lose the
bypass_permissions_disabledreasonBoth mention hook
-
v2.1.236
Hooks and Ctrl-C go quiet once shutdown has started
Both mention hook