You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
HooksArea: what it touches
ImprovementsKind: in v2.1.290,
ImprovementsSection of the release
Unclear It is not clear what makes Claude Code set the output aside rather than deliver it straight away.
What
A hook is a command you configure to run at a certain moment. A SessionStart hook runs when a session begins or resumes, and its output can add context for Claude. When that output arrives late, Claude Code can now set it aside and restore it later, including when a later worker process takes over.
If set-aside output cannot be read back, it is dropped and Claude Code logs: "SessionStart hook output an earlier worker set aside could not be read (dropped)".
Why
This affects whether context from your SessionStart hooks reaches Claude in resumed sessions and in non-interactive runs.
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 doubtIt is not clear what makes Claude Code set the output aside rather than deliver it straight away.
