{"version":"2.1.299","anchor":"plugin-command-registration-refuses-names-that-clash-with-al","canonical_anchor":"plugin-command-registration-refuses-names-that-clash-with-al","heading":"Plugin commands can no longer take a name another command uses as an alias","tier":"notice","area":"Plugins","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/plugin-command-registration-refuses-names-that-clash-with-al","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Plugin commands can no longer take a name another command uses as an alias\n\nPlugins registering a slash command are now refused if the name matches an alias of an enabled command, built-in ones included\n\n**What**\n\nPlugins are add-on packages that extend Claude Code. When a plugin registers a command through `$.command.register`, the name used to be checked only against other commands' names. It is now also checked against every alias, or alternative name, of every enabled command that is not hidden, including Claude Code's built-in ones. A name that clashes is refused as already taken.\n\n**Why**\n\nA plugin can no longer take over an alias that already opens another command.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}