{"version":"2.1.292","anchor":"stop-hook-feedback-is-now-sanitised-before-being-queued","canonical_anchor":"stop-hook-feedback-is-now-sanitised-before-being-queued","heading":"Stop hook feedback is cleaned up before Claude sees it","tier":"notice","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/stop-hook-feedback-is-now-sanitised-before-being-queued","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Stop hook feedback is cleaned up before Claude sees it\n\nFeedback from a stop hook now has protected text redacted and a trailing `\n\n**What**\n\nA hook is a small piece of code that runs automatically when something happens in Claude Code. A stop hook runs when Claude is about to finish, and its feedback is passed back to Claude. Before, the summary and body of that feedback were passed on exactly as written. Now Claude Code cleans both up first:\n\n- certain listed pieces of text are blanked out\n\n- a `<` at the very end is replaced with `&lt;`, so it cannot start a tag\n\n**Why**\n\nOutput from a stop hook can no longer slip half-written tags or protected text into the message Claude receives.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}