Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.267 ·

Managed-settings-only secDefault flag controls seating of the bundled sec-default plugin

A new managed-settings-only flag lets organizations put their bundled sec-default plugin ahead of user-installed plugin hooks

Use it now No documentation found New Features
JSON All of v2.1.267
Use it nowTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Plugins SecurityArea: what it touches
New FeaturesKind: in v2.1.267,
What probably matters to youSection of the release
What

A new settings field, honored only when set in managed settings (not user, project, local, or --settings), controls whether the organization's bundled "sec-default" plugin takes the outermost seat in the chain of plugin hooks, ahead of any plugins listed in prependPlugins.

Why

This keeps things like classic hooks, prompt content, managed settings, and tool policy protected from being overridden by plugins that users install themselves, since only an administrator setting managed settings can control this placement.

Read from
Names in the bundlesecDefault
How sure we are
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: secDefault

See this entry in the whole of v2.1.267 →

Feedback