Follow Discord
Sweep 02 Oct 2026 · 18:55Z Build v2.1.288 509 read Stable v2.1.285 Latest v2.1.287 Next v2.1.288 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.287 ·

Organization-enabled plugins keep managed status only when their source matches

A plugin turned on by managed settings is treated as organization-managed only if its marketplace source matches what those settings declare

You'll notice Improvements
JSON All of v2.1.287
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
PluginsArea: what it touches
ImprovementsKind: in v2.1.287,
ImprovementsSection of the release
What

Managed settings are settings an organization sets centrally for everyone using Claude Code. A plugin turned on through managed settings now counts as organization-managed only if the marketplace it came from matches the source those managed settings declare. A marketplace is a catalog Claude Code installs plugins from.

When the source does not match, Claude Code logs a warning. The plugin's hooks then run at the same level as the user's own plugins, not at the organization level. Hooks are commands a plugin runs automatically at certain points.

A plugin delivered from a remote source does not get organization-managed status in this release. That is planned for a later release.

Why

Administrators should check that the marketplace sources in their managed settings match where their plugins actually come from. If they don't, the organization's plugin hooks can quietly drop to the user level, and the only sign is a warning in the log.

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 what information Claude Code compares when it decides whether a plugin's source matches.

See this entry in the whole of v2.1.287 →

Feedback