{"version":"2.1.323","anchor":"hook-output-areplansindocs-option-and-posttooluse-output-re","canonical_anchor":"hook-output-areplansindocs-option-and-posttooluse-output-re","heading":"PostToolUse hooks only trigger the output-rewrite notice on real changes","tier":"notice","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/hook-output-areplansindocs-option-and-posttooluse-output-re","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### PostToolUse hooks only trigger the output-rewrite notice on real changes\n\nWhen a PostToolUse hook returns updated output, Claude Code now shows its notice only if the output actually changed\n\n**Unclear.** What the new option about where plans are kept changes for hook users is not stated.\n\n**What**\n\nA hook is a command you configure to run automatically at certain points. A `PostToolUse` hook runs after a tool call (one action Claude takes, such as reading a file) succeeds. It can return updated output for that tool. Claude Code now shows its notice about this updated output only when the output really differs from the original.\n\nHook output handling also now receives an extra option about where plans are kept.\n\n**Why**\n\nYou should see fewer notices from hooks that hand back output unchanged. The way hooks behave may also differ slightly in some cases.\n\n- Area: Hooks\n- Names: `PostToolUse`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}