Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

plugin_policy_blocked

setting gone JSON

A Claude Code settings key, read out of the shipped bundle. It was in the build from v2.1.301 and was gone by v2.1.302.

Plugin updates blocked by org policy now fail early with a stated reason instead of quietly stalling.

Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.238.

First seen v2.1.301 15 Oct 2026
Last seen v2.1.301 15 Oct 2026, gone by v2.1.302
Builds1 / 149on this box, as of v2.1.308
Written about v2.1.238 first named in a changelog, 20 Aug 2026
v2.1.301in the build not in the build never minedv2.1.308

In the changelogs

4

Releases whose published page names plugin_policy_blocked.

  1. v2.1.287
    Plugin uninstall and update check the Anthropic Directory more strictly

    Removing or updating plugins from the Anthropic Directory now runs stricter checks, gives specific failure reasons, and can be turned off by admins

    found in this entry's text

  2. v2.1.281
    Plugin policy-block messages factored into one helper

    Plugin and marketplace policy-block messages now come from one shared helper, with the same wording as before

    found in this entry's text

  3. v2.1.268
    Plugin enable/disable results now carry a machine-readable failureCode

    Plugin enable/disable failures now return a machine-readable failureCode alongside the human-readable error message

    found in this entry's text

  4. v2.1.238
    Plugin updates blocked by org policy report why they were skipped

    Plugin updates blocked by org policy now fail early with a stated reason instead of quietly stalling.

    found in this entry's text

First cited

1

The earliest release whose published evidence quoted plugin_policy_blocked was v2.1.268, 10 Sep 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.

ReleaseDateThe span that was quoted
v2.1.26810 Sep 2026failureCode: n ? "plugin_policy_blocked" : "managed_settings_override"

Presence across releases

2
BuildsHow manyDatesReading
v2.1.3011 build15 Oct 2026 ◆in the build
v2.1.302 – v2.1.3087 builds16 Oct 2026 → 22 Oct 2026 ○not in the build

Build by build

8

One row per release since the first build this name was read out of. Absent means the build was read and the name was not in it, never mined means no bundle for that release was ever archived, and a declared type or a default is only ever what that release's own bundle stated.

BuildDateStateThe record behind it
v2.1.30115 Oct 2026·addedverdict: added
v2.1.30216 Oct 2026·removedverdict: removed
v2.1.30318 Oct 2026·absent—
v2.1.30419 Oct 2026·absent—
v2.1.30520 Oct 2026·absent—
v2.1.30621 Oct 2026·absent—
v2.1.30721 Oct 2026·absent—
v2.1.30822 Oct 2026·absent—

Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the settings key does. All settings keys.

Feedback