Sweep 19 Sep 2026 · 02:36Z Build v2.1.278 500 read Stable v2.1.267 Latest v2.1.278 Next v2.1.278 Feeds RSS JSON llms.txt Unofficial

Claude Code now validates strictKnownMarketplaces and blockedMarketplaces entries and warns or falls back when they can't actually be enforced

TierYou'll noticehow much it should matter to you
Useful2my rating, 1 to 5
Signal1worth watching, 1 to 5
AreaSettingswhat it touches
KindImprovementsin v2.1.277,
Group of 3 You'll notice

Claude Code now validates strictKnownMarketplaces and blockedMarketplaces entries and warns or falls back when they can't actually be enforced

What

  • Entries in the strictKnownMarketplaces and blockedMarketplaces settings are now checked for whether they can actually be enforced: regex patterns must compile, GitHub-source entries with an owner wildcard must be written exactly as <owner>/*, wildcard sources are only allowed in GitHub form, and refs can't contain *.
  • An invalid strictKnownMarketplaces value falls back to an empty allowlist, meaning no marketplaces are admitted until the setting is fixed. An invalid blockedMarketplaces entry is kept rather than dropped (with a warning), since removing it would loosen restrictions instead of tightening them.
  • On managed-settings tiers, each invalid entry now gets an explicit message: an unenforceable blockedMarketplaces entry is kept but inert ("it can never match, so it blocks nothing"), while an unenforceable strictKnownMarketplaces entry is silently stripped. In user, project, or local settings files, an invalid entry in either key is simply inert.

Why This stops administrators from unknowingly relying on marketplace restrictions that look active but can never actually match anything, and makes clear whether a broken rule is being kept for safety or dropped.

Read from
Names in the bundlestrictKnownMarketplacesblockedMarketplaces
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Confirmed since Anthropic's documentation has since written up blockedMarketplaces, on Deploy managed settings. | `blockedMarketplaces` | An individual invalid entry is stripped and the valid subset is enforced. An entry that parses but can never match, such as a `hostPattern` regex that doesn't compile, is kept with a warning. It blocks nothing unt… managed-settings see the edit
Confirmed since Anthropic's documentation has since written up strictKnownMarketplaces, on Deploy managed settings. | `strictKnownMarketplaces` | Enforced as an empty allowlist until the value is fixed, so no [marketplace source](/docs/en/plugin-marketplaces#managed-marketplace-restrictions) is admitted. An individual entry that is invalid or can't be e… managed-settings see the edit
How sure we are
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up strictKnownMarketplaces, on Deploy managed settings.
Anthropic's release notes agreeFixed one malformed strictKnownMarketplaces or blockedMarketplaces entry silently disabling the whole enterprise marketplace policy

See this entry in the whole of v2.1.277 →