Bug Report: ChatGPT Windows authentication-loop diagnostic
`Steps to Reproduce`
Install and launch the Microsoft Store ChatGPT app on the Windows system
described below.
From the signed-out screen, choose Continue and complete the ChatGPT OAuth
browser flow. The sign-in reports success and the app initially loads the
account normally.
Leave the app open for approximately 15 to 120 seconds, or close and reopen
it while the newly issued credentials are still present.
Observe the app return to the sign-in/onboarding screen
`Expected Result`
The successful OAuth login is saved and reused across app launches.
The app remains signed in and refreshes the active ChatGPT session
automatically before token expiry, without another browser login.
Once startup completes, the bundled app-server returns to normal idle CPU use
and does not cause sustained fan activity.
The account initially loads and protected backend requests return HTTP 200.
The first account-settings/refresh cycle then returns HTTP 401, and the
backend logs refresh_token_invalidated.
The UI changes to auth_token_missing and returns to the sign-in/onboarding
screen even though the newly saved local credential remains valid, readable,
complete, and unexpired.
In the decisive clean reproduction, the first 401 occurred at
12:00:43.508 PDT and refresh_token_invalidated at 12:00:4
`Environment`
Microsoft Windows 11 Pro 25H2, 64-bit, OS version/build: 10.0.26200 / 26200.9168
hardy sky
