Marketplace file probes and start-up settings reads now go through the host storage backend instead of direct filesystem calls, each naming the storage space it wants, and fall back to ordinary file reads whenever the backend is absent, does not serve that space, or errors. A new start-up pass pre-reads managed-settings.json, its drop-in directory and the project and local settings layers, seeding parsed files and folder listings so the normal settings walk does not read them a second time. Every failure path is non-fatal, so the effect is fewer duplicate reads rather than any change in which settings win.
- Probing for, reading and checking the existence of local marketplace files uses the backend only when the v5 storage backend is present, otherwise the previous direct filesystem calls.
- Plugin cache locations ask for the
systemspace and workspace-relative marketplaces ask forworkspace. - Backend errors on marketplace reads are converted to ENOENT-shaped errors, the standard "no such file" shape, wherever a missing file is the intended meaning, and are logged as
failed to read a local marketplace file (v5 backend error). - The settings pre-read pass runs only if the backend declares it serves the relevant space; when it does not serve
systemthe managed-settings tier is skipped and the policy walk reads the host's files itself. - The settings store additionally caches directory listings, records which entries were primed rather than read, counts policy walks, and decides per candidate whether a pre-read may be installed, raced or deferred.
- If the host attests there is no operating-system policy folder but a managed settings file turns up anyway, that attestation is marked contradicted for the rest of the process.
- Setting
CLAUDE_CODE_MANAGED_SETTINGS_PATHshort-circuits the no-policy-folder branch. - Diagnostic lines tagged
settingsPrime:grew from 10 to 27.
failed to read a local marketplace file (v5 backend error), settingsPrime: start-up seed of the ${t} failed: ${p(s)}; the file reads serve, settingsPrime: the managed-settings file tier is not read ahead (the backend does not serve 'system'); the policy walk reads the host's files itself
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Choose whether Claude Code applies only the highest-priority [managed source](/docs/en/managed-settings#how-claude-code-combines-managed-sources) your organization delivers, or combines every admin source it delivers. By default Claude Cod…settings-reference see the edit
* The endpoint comes from the gateway itself. If you set the same variable in an MDM profile or a local `managed-settings.json`, exports stay on the relay.claude-apps-gateway-config see the edit
Anthropic's documentation has since written up managed-settings.json, on Claude apps gateway configuration.