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.305 ·

Plugin enable and disable respect managed settings

Turning a plugin on or off is refused with managed_settings_override when your organization's managed settings already decide it, unless recordOverManagedSettings is passed

Group of 2 You'll notice Improvements
JSON All of v2.1.305
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.305,
ImprovementsSection of the release

Unclear It is not clear whether the refusal applies to turning plugins on, turning them off, or both.

What

Plugins are add-on packages for Claude Code. Managed settings are settings your organization sets centrally, and enabledPlugins in them can decide whether a plugin is on or off.

  • New refusal: enabling or disabling a plugin that enabledPlugins in the policy settings already decides now fails with the failureCode managed_settings_override.
  • Bypass: the check is skipped when the call passes recordOverManagedSettings, and one plugin disable call now passes recordOverManagedSettings: true.
  • Separately, a failed set_model response (the request that changes which model is used) now includes error_code "internal_error".

Why

In an organization with managed settings, you get a clear refusal instead of a quiet change that goes against policy. Programs talking to Claude Code also get a code they can check when changing the model fails.

Read from
Names in the bundleenabledPlugins
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 whether the refusal applies to turning plugins on, turning them off, or both.

See this entry in the whole of v2.1.305 →

Feedback