{"version":"2.1.305","anchor":"spawn-runner-hook-output-handling-after-exit","canonical_anchor":"spawn-runner-hook-output-handling-after-exit","heading":"Runner hook output is no longer lost when the hook exits","tier":"notice","area":"Elsewhere","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/spawn-runner-hook-output-handling-after-exit","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Runner hook output is no longer lost when the hook exits\n\nIn runner mode, the spawn-runner hook's last partial lines are kept and output from processes it left running is still logged, up to a limit\n\n**What**\n\nA hook is a command Claude Code runs automatically at a set point. In runner mode, the spawn-runner hook's output is read and logged, and that reading changed:\n\n- An unfinished last line is written out when the hook exits instead of being dropped.\n\n- Output from processes the hook left running keeps being logged as after-exit lines, up to a cap.\n\n- Errors while reading the hook's normal output or error output are handled.\n\n- When the hook exits, a short grace period now passes before it is treated as finished.\n\n**Why**\n\nRunner logs no longer lose the end of a hook's output or hang on stray output from leftover processes. This only matters in runner mode.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}