{"version":"2.1.302","anchor":"plugin-loading-reworked-marketplace-conflicts-become-per-pl","canonical_anchor":"plugin-loading-reworked-marketplace-conflicts-become-per-pl","heading":"Plugin manifest conflicts are now collected as errors for each plugin","tier":"notice","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/plugin-loading-reworked-marketplace-conflicts-become-per-pl","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### Plugin manifest conflicts are now collected as errors for each plugin\n\nA clash between a plugin's plugin.json and its marketplace entry is now recorded as an error in a list instead of failing the load\n\n**Unclear.** Whether a plugin with conflicting manifests still loads and works is not shown.\n\n**What**\n\nA plugin is an add-on to Claude Code, and a marketplace is a list of plugins you can install from. When both a plugin's plugin.json file and its marketplace entry list the plugin's components, Claude Code reports that the plugin \"has conflicting manifests\". Before, that stopped the load and returned the error. Now the error is added to a list of errors for that plugin and the loader returns the plugin. After loading, Claude Code also records which plugins were synced, merged or demoted.\n\n**Why**\n\nPlugin load problems show up as errors attached to the plugin rather than as a single failure.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}