Follow Discord
Sweep 03 Nov 2026 · 22:27Z Build v2.1.318 536 read Stable v2.1.311 Latest v2.1.318 Next v2.1.318 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.317 ·

Settings passed with --managed-settings can now be kept out of the policy level

Settings given with --managed-settings may now be kept out of the policy level of settings, and Claude Code logs a warning when that happens

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

Unclear It is not stated when settings passed with --managed-settings are kept out of the policy level.

What

Claude Code combines settings from several levels. The policy level holds settings an organization enforces. Settings passed with the --managed-settings flag can now be kept out of that level in some cases. When the reason for keeping them out changes, Claude Code logs a warning that begins '--managed-settings left out of the policy tier:'.

Why

If your organization passes settings with --managed-settings, check for this warning. It means those settings were not applied at the policy level.

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 stated when settings passed with `--managed-settings` are kept out of the policy level.

See this entry in the whole of v2.1.317 →

Feedback