{"version":"2.1.290","anchor":"late-sessionstart-plugin-hook-output-waits-for-open-tool-cal","canonical_anchor":"late-sessionstart-plugin-hook-output-waits-for-open-tool-cal","heading":"Late SessionStart hook output now waits for running tool calls","tier":"notice","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/late-sessionstart-plugin-hook-output-waits-for-open-tool-cal","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Late SessionStart hook output now waits for running tool calls\n\nOutput from a SessionStart hook that arrives late is now held until any open tool call finishes, instead of being added at once\n\n**What**\n\nA `SessionStart` hook is a command you or a plugin set up to run when a session begins or resumes. Its output is added to the conversation. When that output arrives late, Claude Code now holds it while a tool call is still open, instead of adding it straight away. A tool call is one action Claude takes, such as running a command. If the output cannot be added at all, Claude Code logs that it was dropped.\n\n**Why**\n\nAdding text between a tool call and its result could break the order the conversation depends on. Waiting keeps each tool call and its result together.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}