{"version":"2.1.223","anchor":"growthbook-auth-header-resolution-is-now-async-and-gated","canonical_anchor":"growthbook-auth-header-resolution-is-now-async-and-gated","heading":"GrowthBook auth header resolution is now async and gated","tier":"internal","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/growthbook-auth-header-resolution-is-now-async-and-gated","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### GrowthBook auth header resolution is now async and gated\n\nFeature-flag requests can now attach auth asynchronously, but that path stays off in this build.\n\n**What**\n\nEval-authed requests and GrowthBook client init await an async auth-header resolver behind a predicate rather than calling the synchronous header builder.\n\n**Details**\n\n- On resolver failure the error is logged and the request continues without auth.\n- Client init aborts if the account changed mid-flight.\n- The eval-authed path still requires `tengu_gb_eval_authed_enable`, whose fallback is false, so it is off in this build.\n\n**Evidence**\n\n`GrowthBook: auth header resolution failed (`\n\n- Flag `tengu_gb_eval_authed_enable`: Not enough to say (read for one account on one subscription tier against v2.1.223; this account: no value returned, anonymous baseline: no value returned, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Present in the build but not switched on"}