{"version":"2.1.167","anchor":"auth-helper-settings-filtered-under-explicit-host-management","canonical_anchor":"auth-helper-settings-filtered-under-explicit-host-management","heading":"Auth-helper settings filtered under explicit host management","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.167\/e\/auth-helper-settings-filtered-under-explicit-host-management","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.167","markdown":"### Auth-helper settings filtered under explicit host management\n\nWhen `managedByHostFlag` is true (i.e., `CLAUDE_CODE_PROVIDER_MANAGED_BY_HOST` is explicitly set), auth-related settings such as `apiKeyHelper` and `awsAuthRefresh` are now stripped from the configuration overlay that the host applies. Previously only a narrower set of settings was filtered. This prevents host-controlled auth helpers from being inadvertently overridden by project or user-level settings when the host is fully managing the provider.\n\n**Evidence**\n\nadditional `continue` branch in the settings-filter loop that skips `xF7`-listed keys when `Lb$.managedByHostFlag` is true (search for `\"managedByHostFlag\"`)"}