{"version":"2.1.277","anchor":"marketplaces-declared-only-in-settings-are-now-reconciled-an","canonical_anchor":"marketplaces-declared-only-in-settings-are-now-reconciled-an","heading":"Marketplaces declared only in settings are now reconciled and logged","tier":"notice","area":"Plugin Install","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/marketplaces-declared-only-in-settings-are-now-reconciled-an","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Marketplaces declared only in settings are now reconciled and logged\n\nPlugin marketplaces listed only in settings are now validated and reconciled automatically\n\n**What**\n\nIf a plugin marketplace is referenced in your settings but hasn't yet been recorded in the internal `known_marketplaces.json` tracking file, Claude Code now checks it: it validates the declared source and path, and either admits it (letting plugins load from it right away, with a note that it will be formally recorded once a background reconcile step runs) or records why it was skipped, such as an invalid source type, an unanchored path, a manifest not found under `.claude-plugin`, or a rejection by the registry's admission rule.\n\n**Why**\n\nThis closes a gap where a marketplace only declared in settings might not actually get recognized or used, and gives a clear reason when one is rejected instead of it silently failing to load.\n\n- Area: Plugin Install\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}