Claude Code can skip reading policy settings from disk when the host says there are none.
What's wrong with this entry?
When the storage backend attests the machine has no OS policy folder, the settings walk is handed an empty managed-settings tier without touching disk. If CLAUDE_CODE_MANAGED_SETTINGS_PATH was set explicitly, that contradiction is recorded and the walk reads the files itself.
settingsPrime: the host attests this machine has no OS policy folder ('system' absent); the policy walk is served an empty managed-settings file tier without reading the host
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.235
Remote settings can be primed from local storage instead of probing disk
Both mention path
-
v2.1.236
Managed-settings review prompt dropped from the main UI
Both mention managed
-
v2.1.242
Startup can wait on a remote managed-settings refresh, with a deadline
Both mention managed