What
When Claude Code runs under a host that manages the provider, settings-file model configuration is ignored in favour of policy handed down by the parent process.
Details
- Settings resolution gained
hostManagedProvider: te.CLAUDE_CODE_PROVIDER_MANAGED_BY_HOST. - With that env var set,
model,fallbackModel,modelOverridesand provider env vars are stripped from the policy view. - A
hostModelOverlaybuilt from parent-managed settings is applied in their place; adminmodelOverridesare stashed and re-applied to enforcement. - The managed-settings source enum gained a "parent" value, returned when a parent slice or host model overlay exists.
- Inactive unless
CLAUDE_CODE_PROVIDER_MANAGED_BY_HOSTis set.
Evidence
hostManagedProvider
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundleCLAUDE_CODE_PROVIDER_MANAGED_BY_HOST
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agree
Fixed host model-selection keys not taking precedence over a stale on-disk managed-settings.json when CLAUDE_CODE_PROVIDER_MANAGED_BY_HOST…