{"version":"2.1.299","anchor":"plugin-commands-record-the-plugin-that-registered-them","canonical_anchor":"plugin-commands-record-the-plugin-that-registered-them","heading":"Commands added by plugins now record which plugin added them","tier":"internal","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/plugin-commands-record-the-plugin-that-registered-them","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Commands added by plugins now record which plugin added them\n\nCommands registered by a plugin now note the plugin that registered them, with some exceptions\n\n**What**\n\nPlugins (add-on packages for Claude Code) can add their own commands. Most of those commands now record which plugin registered them, though some plugins are excluded. The way Claude Code settles things after a reload was reworked to match.\n\n**Why**\n\nNothing changes in how the commands work today. It lays the groundwork for tying each plugin command back to its plugin, including when plugins are reloaded.\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}