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

Claude Code v2.1.302 ·

Organization policy plugin options are filtered by a different check

Claude Code changed how it decides which plugin option values from organization policy are kept, and sets none when no values pass

Under the hood Internal Changes
JSON All of v2.1.302
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
Managed SettingsArea: what it touches
Internal ChangesKind: in v2.1.302,
What probably matters to youSection of the release

Unclear Which policy plugin option values are now kept or dropped compared with before is not shown.

What

An organization's administrator can set managed settings, which apply to everyone in the organization. These can include pluginConfigs, the stored answers to a plugin's configuration dialog. Claude Code changed how it decides which of these option values from policy to keep. It now uses a different check, and if no values pass, it sets no plugin configuration at all instead of an empty one. A built-in plugin name, sec-default@builtin, appears alongside this code.

Why

The option values that survive from an organization's policy may differ from before.

Read from
Names in the bundlepluginConfigs
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 doubtWhich policy plugin option values are now kept or dropped compared with before is not shown.

See this entry in the whole of v2.1.302 →

Feedback