Feature-flag requests can now attach auth asynchronously, but that path stays off in this build.
The authed feature-flag request path requires a gate whose fallback is false, so it never runs here.
tengu_gb_eval_authed_enable Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.223: on
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.
Read once, for one account on one subscription tier, against v2.1.223. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
Eval-authed requests and GrowthBook client init await an async auth-header resolver behind a predicate rather than calling the synchronous header builder.
- On resolver failure the error is logged and the request continues without auth.
- Client init aborts if the account changed mid-flight.
- The eval-authed path still requires
tengu_gb_eval_authed_enable, whose fallback is false, so it is off in this build.
GrowthBook: auth header resolution failed (
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.