{"version":"2.1.280","anchor":"same-policy-diagnostic-treatment-extended-to-marketplace-blo","canonical_anchor":"same-policy-diagnostic-treatment-extended-to-marketplace-blo","heading":"Same policy-diagnostic treatment extended to marketplace-blocked-by-policy","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/same-policy-diagnostic-treatment-extended-to-marketplace-blo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Same policy-diagnostic treatment extended to marketplace-blocked-by-policy\n\nPlugin marketplace 'blocked by policy' errors now get the same detailed diagnostic as Artifacts\n\n**What**\n\nWhen a plugin marketplace is blocked because Claude Code couldn't fetch your organization's policy (a `marketplace-blocked-by-policy` error), it now shows the same detailed diagnostic used elsewhere for policy-fetch failures, naming the host and specific error cause, instead of always showing a generic \"blocked by enterprise policy\" or \"not in the allowed marketplace list\" message.\n\n**Why**\n\nThis gives a clearer, more actionable explanation when a plugin marketplace can't be reached, rather than a one-size-fits-all denial message.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}