Credentials now travel with the storage handle through most call paths, groundwork for per-session logins.
What's wrong with this entry?
A credentials value now travels with the existing storage handle through app config, tool-use contexts, artifact and skill call sites, OAuth and gateway login, session title generation and trusted-device enrollment. Several auth reads became asynchronous as a result.
- The design OAuth token read now goes through a store read and logs "Failed to read design OAuth tokens" when it fails.
credentials: r.credentials,
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