{"version":"2.1.299","anchor":"permission-requests-carry-a-plugin-field","canonical_anchor":"permission-requests-carry-a-plugin-field","heading":"Permission requests now pass along which plugin made them","tier":"internal","area":"SDK","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/permission-requests-carry-a-plugin-field","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Permission requests now pass along which plugin made them\n\nThe `plugin` field on a `can_use_tool` permission request is now passed through to Claude Code's permission handling\n\n**What**\n\nA `can_use_tool` request is how Claude Code asks for permission before a tool runs, through the control protocol that SDK clients use. When such a request includes a `plugin` field naming a plugin, that name is now passed through to the permission handling. Requests that are forwarded on also have their contents adjusted before they are sent.\n\n**Why**\n\nA permission prompt that comes from a plugin can be traced back to that plugin, so the prompt can say where it came from.\n\n- Area: SDK\n- Names: `can_use_tool`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}