{"version":"2.1.167","anchor":"finer-grained-managedbyhost-flag-tracking","canonical_anchor":"finer-grained-managedbyhost-flag-tracking","heading":"Finer-grained managedByHost flag tracking","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.167\/e\/finer-grained-managedbyhost-flag-tracking","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.167","markdown":"### Finer-grained `managedByHost` flag tracking\n\nThe internal host-management state object now distinguishes between two cases that previously both set `managedByHost = true`:\n\n- `CLAUDE_CODE_PROVIDER_MANAGED_BY_HOST` set \u2192 `managedByHost: true`, `managedByHostFlag: true`\n- `CLAUDE_CODE_HOST_AUTH_ENV_VAR` set \u2192 `managedByHost: true`, `managedByHostFlag: false`\n\nOnly the first case \u2014 explicit host provider management \u2014 now also activates the settings-filtering behavior described below. The second case (host auth env var only) keeps its existing behavior unchanged.\n\n**Evidence**\n\n`managedByHostFlag` field added to host state initialization (search for `\"managedByHostFlag\"`)"}