{"version":"2.1.323","anchor":"hook-tampering-messages-for-answers-and-slack-reads","canonical_anchor":"hook-tampering-messages-for-answers-and-slack-reads","heading":"Hooks blocked from changing your answers and Slack messages in some sessions","tier":"notice","area":"Hooks","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/hook-tampering-messages-for-answers-and-slack-reads","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Hooks blocked from changing your answers and Slack messages in some sessions\n\nIn some sessions, a hook that tries to change your answer to Claude's question or Slack messages Claude read is ignored, and Claude says so\n\n**Unclear.** It is not stated which sessions block these hook changes.\n\n**What**\n\nA hook is a command you configure for Claude Code to run automatically, and some hooks can change what a tool returns before Claude sees it. Claude Code now has two messages for when a hook tries to make a change it is not allowed to make in the current session:\n\n- Your answer to a question Claude asked you: Claude reads your answer without the hook's change.\n\n- Slack messages Claude read: Claude reads them without the hook's change.\n\nIn both cases Claude uses the original, unmodified version and says that the hook's change was not applied.\n\n**Why**\n\nIn some sessions, hooks can no longer rewrite these results. If you rely on a hook that edits answers or Slack messages, it may not take effect there.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: yes"}