{"version":"2.1.317","anchor":"permission-requests-carry-plugin-and-suppress-always-allow-r","canonical_anchor":"permission-requests-carry-plugin-and-suppress-always-allow-r","heading":"Permission requests now say which plugin asked and can hide \"always allow\"","tier":"internal","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/permission-requests-carry-plugin-and-suppress-always-allow-r","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Permission requests now say which plugin asked and can hide \"always allow\"\n\nPermission requests sent to apps that drive Claude Code now name the plugin and can say whether to hide the always-allow choice\n\n**Unclear.** It is not clear when Claude Code sets `suppress_always_allow_rule`.\n\n**What**\n\nWhen Claude Code asks for permission to use a tool, the request it sends to a program driving it now includes two more fields:\n\n- `plugin`: which plugin the request concerns.\n\n- `suppress_always_allow_rule`: whether the \"always allow\" choice should be left out.\n\n**Why**\n\nPrograms that show these requests can stop offering \"always allow\" for some tools.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}