Plugin commands wait for your organization's managed settings

Most claude plugin commands now wait for remote managed settings to load and do not run if those settings are not approved

You'll noticeTier: how much it should matter to you

2Useful: my rating, 1 to 5

1Signal: worth watching, 1 to 5

PluginsArea: what it touches

ImprovementsKind: in v2.1.292, 06 Oct 26

ImprovementsSection of the release

Unclear It is not clear in which situations Claude Code waits, so it is unknown whether every reader is affected.

What

Managed settings are settings an organization's administrator sets centrally for everyone. Most claude plugin commands now wait until these settings have loaded from the server. If the settings are not approved, or Claude Code is shutting down, the command does not run.

These commands do not wait:

claude plugin list
claude plugin marketplace list
claude plugin validate
claude plugin tag
claude plugin test
claude plugin eval init

Why

In an organization that manages plugin policy, people can no longer install or change plugins before that policy has been confirmed.

Read from

Names in the bundleclaude plugin

What the documentation says

claude plugin Claude Code changelog modified, high confidence * Added to `claude plugin validate`: each hook a mod registers at a gating site is listed with whether it has a `.catch` (`gatingHooks` under `--json`) see the edit

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.

Added since 8 Oct 2026 A small documentation edit on Marketplace reference touched a line naming claude plugin after this was published. * **The download folder of a registered GitHub marketplace, `<owner>-<repo>`**: Claude Code downloads a marketplace added from a `github` source such as `acme/x-tools` through a folder named `acme-x-tools`, whatever that marketplace's own … plugins/marketplace-reference see the edit

Confirmed since 7 Oct 2026 Anthropic's documentation has since written up claude plugin, on Claude Code changelog. * Fixed `claude plugin test` failing for mods that call `$.session.append`; tests can read the appended rows back with the new `mock.session` changelog see the edit

How sure we are

Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.

The writer flagged doubtIt is not clear in which situations Claude Code waits, so it is unknown whether every reader is affected.

Anthropic's documentation agreesclaude plugin on Claude Code changelog

Anthropic's release notes agreeFixed claude plugin commands such as marketplace add and install running before an organization's managed settings had loaded on a first run

See this entry in the whole of v2.1.292 →

The build it came inv2.1.292

6 Oct 2026 · 331 entries, this one is #140.

Use it now19
You'll notice163
Nothing to try yet14
Under the hood135

Either side of it

v2.1.291Older
v2.1.293Newer

Open the release →

Anthropic's notes

Upstream's own release notes for v2.1.292 name something this entry names, so the two are probably about the same change. Probably: the pairing is made on a shared name rather than on the words around it.

Fixed claude plugin commands such as marketplace add and install running before an organization's managed settings had loaded on a first run
Fixed claude plugin validate listing a matcher or state value for a hooks module that the engine reads from elsewhere
Fixed claude plugin validate listing a $.state value read through a top-level var that was declared again or reassigned; such a module is now refused
Changed claude plugin test: a failed expect inside a hook the test registered, or a stub answer the engine refuses, now fails the test instead of passing silently

Is this right?