Setting CLAUDE_CODE_PROVIDER_MANAGED_BY_HOST makes the parent process dictate your model settings, ignoring your settings file.
What's wrong with this entry?
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.
- 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.
hostManagedProvider
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.229
OpenTelemetry can be sent through Anthropic's first-party gateway
Both mention provider managed host
-
v2.1.225
OAuth 401 recovery no longer silently replaces a user-supplied token
Both mention provider managed host