{"version":"2.1.296","anchor":"async-rewake-hook-output-lines-are-pre-filtered","canonical_anchor":"async-rewake-hook-output-lines-are-pre-filtered","heading":"Background rewake hooks filter their output lines before reading them","tier":"notice","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/async-rewake-hook-output-lines-are-pre-filtered","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Background rewake hooks filter their output lines before reading them\n\nOutput lines from `asyncRewake` hooks must now pass a check before being read as JSON, and their summary is kept correctly\n\n**Unclear.** It is not stated what the new check requires of an output line, so hook authors cannot tell which lines are read.\n\n**What**\n\nHooks are commands Claude Code runs at set moments, and `asyncRewake` hooks run in the background. For these hooks, each line of output now has to pass a check before Claude Code reads it as JSON. Before, every line starting with `{` was read. The summary such a hook produces is now stored in the right place.\n\n**Why**\n\nIn practice, the summary from a rewake hook should now be kept instead of going missing.\n\n- Area: Hooks\n- Names: `asyncRewake`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}