Credentials are loaded early at several entry points, which should shave startup delays.
What's wrong with this entry?
A new fast-path credential priming step, absent entirely in 2.1.245, now runs before other work at the background daemon's command line, the computer-use MCP server and several other entry points.
- Each caller loads the priming function and the credential store on demand and awaits the result; the daemon runs it in parallel with fetching policy limits.
- The daemon command line now takes storage as an argument rather than deriving it.
- Runs only on the newer credential-storage branch, guarded by the same check as the surrounding policy-limits warm-up.
primeFastPathCredentials
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