{"version":"2.1.312","anchor":"auto-mode-flags-calls-that-a-hook-or-plugin-changed-after-re","canonical_anchor":"auto-mode-flags-calls-that-a-hook-or-plugin-changed-after-re","heading":"Auto mode reports when a hook or plugin changed a call after it was reviewed","tier":"notice","area":"Auto Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/auto-mode-flags-calls-that-a-hook-or-plugin-changed-after-re","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Auto mode reports when a hook or plugin changed a call after it was reviewed\n\nAuto mode now says when a hook or plugin changed a call after auto mode reviewed it, so auto mode could not check what would run\n\n**Unclear.** It is not clear whether the changed call is blocked or only produces a warning.\n\n**What**\n\nAuto mode lets Claude Code approve actions without asking you, after a safety review. A hook is a script you configure to run at certain points, and a plugin is an add-on. A tool call is one action Claude asks to take, such as running a command. A new message now says that a hook or plugin changed, or may have changed, a call after auto mode reviewed it, so auto mode could not check what would run. Claude Code also looks for tools that are exempt from bypassing and are not sent through the safety review.\n\n**Why**\n\nThis closes a gap where a hook or plugin could change an action after auto mode had already approved it.\n\n- Area: Auto Mode\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}