You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit d20e566
Browse filesBrowse the repository at this point in the historyBrowse files
fix(pi): short-lived Pi processes no longer lose rotated OAuth tokens
T3 starts `pi --mode rpc` for jobs it stops as soon as they answer:
provider status and per-workspace command discovery, text generation
and thread forks. Every RPC-mode Pi starts a background model-catalog
refresh at launch, and that refresh also renews any expired OAuth
credential. When T3's stop (SIGTERM milliseconds after the last answer,
or taskkill /T /F on Windows) lands after the token request has left Pi
but before the response is saved, the provider has already spent the
single-use refresh token and auth.json keeps the spent one. The next
refresh fails with invalid_grant and the user must log in again. With
ChatGPT sign-in's one-hour tokens, the 5-minute status probe ends the
login after the first idle hour.
buildPiRpcLaunch takes `shortLived`, and those four spawn sites pass
it. A short-lived process runs with --offline, which skips Pi's startup
network work, the catalog refresh included; the request-path token
refresh is unaffected. A user's own --offline is not repeated. Thread
processes keep their launch arguments, so they still refresh the
catalog that discovery then reads from Pi's stored copy.
0 commit comments