Under the hood
Useful2 Signal2
Feature flags now resolve from your session's own credentials and storage, earlier in startup.
What's wrong with this entry?
Anonymous. No account, no email.
What
Startup, the agents list command and MCP serve setup now all hand the feature-flag client both the account credentials and the storage the session itself uses, before any flags are evaluated, so remote flag values and their token refresh resolve from that storage rather than a default and earlier in the session than before.
Details
- Runs in those blocks only when the newer storage path is active.
- The storage handle is passed on into the flag client's OAuth token refresh.
- Handing in a second storage backend is ignored, with a warning saying the later one was dropped.
Evidence
setGrowthBookCredentials, setGrowthBookStorageBackend: G, GrowthBook: a storage backend was already handed in; the later one is ignored
Strings lifted out of the shipped bundle, so the claim above can be checked against them.