Token refresh now receives the credential store instead of looking it up, and de-duplicates by store type.
What's wrong with this entry?
The token refresh entry point accepts the credential store and storage handle rather than looking them up, and de-duplicates concurrent refreshes separately for bare credentials versus store-backed ones. The store module existed before but was mostly reached ambiently.
- The same value now rides through request options objects, tool-use contexts, agent and query options, MCP login and logout handlers, UI contexts, and bridge/cowork session creation and background-exit paths.
- This is why so many function signatures grew a trailing argument in this build.
tryCreateCredentialsStore
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.
-
v2.1.234
Signing back into the same account keeps a pending auto-resume
Both mention auth
-
v2.1.234
Token screen reports actual remaining validity
Both mention auth
-
v2.1.234
Setup-token login result carries the expiry
Both mention auth