Unclear Whether this changes how background hooks finish or only reorganises existing behaviour is not clear.
What
Hooks are your own commands that Claude Code runs at set moments, and async hooks run in the background without holding Claude Code up. Claude Code now handles unfinished async hooks for an event like this:
- it waits a short grace period for them to finish
- it cancels any still running after that
- it reads each finished hook's result, and if it cannot, logs that and drops the result
Why
It may change how background hooks wrap up, for example when a session ends. If an async hook's output goes missing, a failed read at the end is one reason.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
Whether this changes how background hooks finish or only reorganises existing behaviour is not clear.