{"version":"2.1.280","anchor":"auto-approve-on-accept-rule-generalized-beyond-a-single-hard","canonical_anchor":"auto-approve-on-accept-rule-generalized-beyond-a-single-hard","heading":"Auto-approve-on-accept rule generalized beyond a single hardcoded tool","tier":"notice","area":"Permissions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/auto-approve-on-accept-rule-generalized-beyond-a-single-hard","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Auto-approve-on-accept rule generalized beyond a single hardcoded tool\n\nAuto-approving a suggested permission rule after acceptance now works for any tool, not just one hardcoded tool\n\n**What**\n\nWhen Claude Code suggests a freeform permission rule and you accept it, it can turn that into an always-allow rule going forward. Previously this logic only worked for one specific hardcoded tool and skipped MCP (Model Context Protocol, a way of connecting external tools) tools entirely. It now instead asks the actual tool whether it supports this via a `suppressesAllPermissionUpdates()` check, and builds the new rule using that tool's real name.\n\n**Why**\n\nThis means the always-allow-after-accept behavior can now apply to more tools, including ones beyond the single tool it used to be limited to, as long as the tool supports it.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}