{"version":"2.1.299","anchor":"plugin-registered-commands-carry-a-plugin-field-reserved-ad","canonical_anchor":"plugin-registered-commands-carry-a-plugin-field-reserved-ad","heading":"Commands registered by plugins now say which plugin added them","tier":"notice","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/plugin-registered-commands-carry-a-plugin-field-reserved-ad","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Commands registered by plugins now say which plugin added them\n\nCommands a plugin registers now carry the plugin's name, and reserved network addresses are treated as blocked by policy\n\n**Unclear.** It is not stated which addresses count as reserved or what is blocked from reaching them.\n\n**What**\n\nTwo small changes:\n\n- Commands added by a plugin (an add-on package that extends Claude Code) now record which plugin registered them.\n\n- A new \"reserved address\" case is grouped with the cases that are blocked by policy.\n\n**Why**\n\nThe first makes it possible to tell which plugin a command came from. The second points to reserved network addresses being refused in the same way as other policy blocks.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}