GrowthBook feature flag evaluation can now use an authenticated endpoint (/api/eval-authed/) that attaches your auth headers, enabling per-user flag targeting. Falls back to the unauthenticated /api/eval endpoint on any error.
- Controlled by
tengu_gb_eval_authed_enable(default: false). - When enabled, GrowthBook's
fetchRemoteEvalCallhook is monkey-patched once at startup (idempotent — a boolean sentinel prevents double-installation). Subsequent feature-flag evaluations POST to<host>/api/eval-authed/<clientKey>instead of the standard<host>/api/eval/<clientKey>. - Auth headers are sourced from the user's current authentication state via
getAuthHeaders(): an OAuth access token addsAuthorization: Bearer <token>and theanthropic-betaheader; an API key addsx-api-key; gateway or third-party provider sessions attach no auth headers, leaving the request functionally unauthenticated despite hitting the authed endpoint. - On non-2xx response: logs
"GrowthBook eval-authed returned non-ok; falling back to /api/eval"and re-runs the call via the original unauthenticated path. - On network or exception error: logs
"GrowthBook eval-authed fetch threw; falling back to /api/eval"and falls back similarly.
"GrowthBook eval-authed fetch threw; falling back to /api/eval" (search for "/api/eval-authed/")
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
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.212: 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.
Read once, for one account on one subscription tier, against v2.1.212. It isn't a statement about your account. What a flag value here can and cannot tell you
New in this build: tengu_gb_eval_authed_enable