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

Managed-settings path is no longer read when the host says there are no system settings

If the host running Claude Code reports there are no system-wide settings, the folder named by CLAUDE_CODE_MANAGED_SETTINGS_PATH is now skipped too

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

Managed settings are settings an organisation puts on a machine to control Claude Code. Some programs that host Claude Code can report that the machine has no system-wide settings at all.

When the host reports this, Claude Code now skips both the operating system's policy folder and the folder named by CLAUDE_CODE_MANAGED_SETTINGS_PATH. The session then has no managed-settings files. Before, setting CLAUDE_CODE_MANAGED_SETTINGS_PATH meant that folder was still read. Sessions without local storage also load no managed-settings files.

Why

This changes which policy settings apply when Claude Code runs inside another program or on a remote host. If you rely on CLAUDE_CODE_MANAGED_SETTINGS_PATH in such a setup, it may no longer be read.

See this entry in the whole of v2.1.301 →

Feedback