Feature-flag handling now cleans up properly, restoring the original fetch when disposed.
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.227: not a boolean we can read
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.227. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
Client creation, exposure logging, remote evaluation, disk sync and the periodic refresh loop moved from module-level globals into one class with injected dependencies behind a lazy singleton. Disposing now restores the SDK's own fetch function instead of leaving the patched wrapper installed, and a disposed instance stops creating clients or refreshing.
- The authenticated evaluation endpoint is still decided per call by
tengu_gb_eval_authed_enable, whose in-source fallback is false; nothing in this build sets it, so the real value comes from remote config.
tengu_gb_eval_authed_enable
Strings lifted out of the shipped bundle, so the claim above can be checked against them.