{"version":"2.1.307","anchor":"auto-mode-permission-denied-decision-keyed-on-plugin-not-de","canonical_anchor":"auto-mode-permission-denied-decision-keyed-on-plugin-not-de","heading":"Plugin \"ask\" decisions are treated as asking a person","tier":"notice","area":"Plugins","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/auto-mode-permission-denied-decision-keyed-on-plugin-not-de","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Plugin \"ask\" decisions are treated as asking a person\n\nAn \"ask\" permission decision now counts as asking a person when it comes from a plugin, not when it is marked as made by a person\n\n**What**\n\nAn outside check, such as a hook (a command you set to run at certain points), can answer a permission request with \"ask\". Claude Code used to treat that answer as a question to a person when the answer was marked as made by a person. It now does so when the answer comes from a plugin, an add-on package.\n\n**Why**\n\nThis changes how permission answers from outside Claude Code are handled.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}