{"version":"2.1.307","anchor":"plugin-ui-labels-a-built-in-marketplace-and-plugin-disable","canonical_anchor":"plugin-ui-labels-a-built-in-marketplace-and-plugin-disable","heading":"Plugin lists use a fixed label for one marketplace, and disabling names the scope","tier":"notice","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/plugin-ui-labels-a-built-in-marketplace-and-plugin-disable","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Plugin lists use a fixed label for one marketplace, and disabling names the scope\n\nPlugin lists show a fixed label for one marketplace, and the `\/plugin` disable message now says which settings scope it wrote to\n\n**What**\n\nThree small changes in how Claude Code handles plugins, which are add-on packages of commands, tools and settings:\n\n- Plugin lists show one particular marketplace (a catalogue plugins are installed from) under a fixed label instead of its own marketplace name.\n\n- The confirmation after `\/plugin disable` still names `.claude\/settings.local.json` as the file it wrote to, and now adds the settings scope after that path.\n\n- Enabling or disabling a plugin now checks that a synced plugin is not hidden behind another plugin of the same name.\n\n**Why**\n\nThese are mostly wording changes. The scope note makes it clearer where a disable was recorded.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}