{"version":"2.1.304","anchor":"tool-wrapper-hidden-when-a-condition-holds-auto-mode-and-pl","canonical_anchor":"tool-wrapper-hidden-when-a-condition-holds-auto-mode-and-pl","heading":"In auto mode, plugins can only tighten calls that a hook cannot approve","tier":"notice","area":"Auto Mode","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/tool-wrapper-hidden-when-a-condition-holds-auto-mode-and-pl","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### In auto mode, plugins can only tighten calls that a hook cannot approve\n\nIn auto mode a plugin can no longer approve a call that a hook's allow cannot approve, and some held plugin decisions now fall back to asking you\n\n**Unclear.** It is not clear in which situation the add-on tool is now hidden.\n\n**What**\n\nAuto mode lets Claude Code decide on its own whether to run many tool calls (the actions it takes, such as running a command). Hooks are your own scripts that run at set moments. Plugins are add-ons. Several permission rules changed:\n\n- In auto mode, or in plan mode with auto mode on, a plugin can only make a call stricter when it is one that a hook's allow cannot approve. A hook's allow in auto mode can no longer be overridden by a plugin.\n\n- When a plugin's decision is held and only a person can give it, Claude Code now asks you instead.\n\n- An add-on tool is now hidden in one more situation.\n\n- Auto mode's usage reporting now records whether a remote-browser rule applied.\n\n**Why**\n\nA plugin can no longer push through, in auto mode, a call that a hook would not be allowed to approve. This keeps such calls under stricter control.\n\n- Area: Auto Mode\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}