{"version":"2.1.295","anchor":"stop-hook-output-no-longer-excluded-when-it-ran-elsewhere","canonical_anchor":"stop-hook-output-no-longer-excluded-when-it-ran-elsewhere","heading":"Hook output is now kept even when the hook ran somewhere else","tier":"notice","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/stop-hook-output-no-longer-excluded-when-it-ran-elsewhere","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Hook output is now kept even when the hook ran somewhere else\n\nSuccessful hook output is no longer dropped just because the hook ran somewhere else\n\n**Unclear.** It is not clear which hook event this applies to.\n\n**What**\n\nA hook is a command you configure to run automatically at certain points while Claude Code works. Claude Code collects the text a hook prints. It has always kept that text when the hook succeeded, did not block anything, and printed something. Before this change, it also discarded the text if the hook had run somewhere else, for example in another process. That extra condition is gone, so output from those runs is now kept.\n\n**Why**\n\nOutput from hooks that ran elsewhere may now reach Claude, where before it was silently left out.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}