{"version":"2.1.290","anchor":"held-sessionstart-hook-output-across-workers","canonical_anchor":"held-sessionstart-hook-output-across-workers","heading":"Late SessionStart hook output can be held and delivered later","tier":"notice","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/held-sessionstart-hook-output-across-workers","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Late SessionStart hook output can be held and delivered later\n\nOutput from a SessionStart hook that arrives late can be set aside and passed on later instead of being lost\n\n**Unclear.** It is not clear what makes Claude Code set the output aside rather than deliver it straight away.\n\n**What**\n\nA 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.\n\nIf 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)\".\n\n**Why**\n\nThis affects whether context from your `SessionStart` hooks reaches Claude in resumed sessions and in non-interactive runs.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}