{"version":"2.1.317","anchor":"permission-ask-schema-no-persistent-rule-for-plugin-started","canonical_anchor":"permission-ask-schema-no-persistent-rule-for-plugin-started","heading":"Permission questions from plugin-started runs should hide the always-allow option","tier":"internal","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/permission-ask-schema-no-persistent-rule-for-plugin-started","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Permission questions from plugin-started runs should hide the always-allow option\n\nFor permission questions from a run a plugin started, Claude Code saves no rule from your answer, and hosts are told to hide the always-allow choice\n\n**What**\n\nClaude Code can send permission questions to a host, the program that shows you Claude Code's prompts, such as an app built on the Claude Agent SDK. A question can carry `suppress_always_allow_rule`, which tells the host not to offer a lasting \"always allow\" choice.\n\nIts description used to cover one case: whole-tool allow rules broader than the action being asked about. It now also covers questions from a run that a plugin (an add-on package for Claude Code) started. For those, Claude Code saves no rule from your answer, not even for the current session, and the host should hide the option.\n\n**Why**\n\nYour answer to a question from a plugin-started run only covers that one action, so an \"always allow\" choice there would promise something Claude Code does not do.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}