[macOS][26.814.41407] Opening an existing conversation invalidates ChatGPT auth and redirects to sign-in
已打开 07:32AM - 18 Aug 26 UTC
bug
auth
app
### What version of the Codex App are you using?
26.814.41407 (build 6720), mac…OS arm64 production build.
The last known-good version on the same machine is 26.810.52044 (build 6662).
### What subscription do you have?
ChatGPT account authentication. Exact tier omitted because the failure is in the desktop authentication bridge and reproduces before any model request.
### What platform is your computer?
- MacBook Pro (Mac16,8)
- Apple M4 Pro
- macOS 26.5.2 (25F84)
- arm64
### What issue are you seeing?
Immediately after the automatic update to 26.814.41407, opening any existing conversation redirects the desktop app to the "Log in to ChatGPT" screen.
At launch, the app initially appears authenticated and shows the conversation list. Selecting an existing conversation successfully resumes the local thread, but within about 400 ms the desktop shell receives HTTP 401 from the ChatGPT account settings endpoint. The app then reports that the auth token is missing, changes the account state to unauthenticated, and displays the login screen.
Quitting and reopening the app temporarily shows the authenticated UI again. Selecting an existing conversation immediately repeats the failure.
Manually signing out also produced a full-screen "Oops, an error has occurred" page.
Sanitized log sequence from 26.814.41407:
```text
chatgpt-account-lookup ... authenticatedAccountPresent=true authMethod=chatgpt result=succeeded
AppServerConnection ... method=thread/resume ... errorCode=null
electron-fetch-wrapper ... desktop_fetch_auth_401 hadToken=true ... /accounts/:param/settings ... willRetry=true
AppServerConnection ... authMethod=chatgpt hasToken=false nullReason=auth_token_missing refreshToken=true tokenExpiryState=missing
chatgpt-account-lookup ... authenticatedAccountPresent=false failureType=account_info_token_unavailable result=failed
electron-message-handler ... status=401 ... Missing valid access token or actor biscuit
electron-message-handler ... status=401 ... Unauthorized
```
No account IDs, conversation IDs, token values, or local paths are included above.
### What steps can reproduce the bug?
1. Be signed into ChatGPT in Codex/ChatGPT Desktop on macOS.
2. Update the desktop app from 26.810.52044 (build 6662) to 26.814.41407 (build 6720).
3. Launch the app. It initially appears signed in and lists existing conversations.
4. Select any existing conversation.
5. Observe that the thread resumes locally, then the app immediately redirects to the ChatGPT login screen.
6. Quit and relaunch the app. It appears signed in again until an existing conversation is selected, after which the same redirect occurs.
### What is the expected behavior?
Opening an existing conversation should preserve the authenticated account state and load the conversation normally.
### Additional information
Troubleshooting completed:
- Disabled and fully quit AdGuard: no change.
- Quit and relaunched the desktop app repeatedly: no change.
- Signed out and performed a fresh ChatGPT device authorization: login succeeded, but selecting an existing conversation still triggered the same 401 and `auth_token_missing` sequence.
- Cleared and rebuilt the Electron cookies, local storage, and session storage after making backups: no change.
- Verified the bundled CLI reports ChatGPT authentication configured and provider/WebSocket reachability healthy.
- Tested both the bundled app-server and stable Codex CLI 0.147.0: no change.
- Rolled back only the desktop app to the official signed and notarized 26.810.52044 build while preserving the same account, local thread data, and network environment.
Rollback result:
- Existing conversations resumed successfully.
- The authenticated account remained present.
- The `desktop_fetch_auth_401` and `auth_token_missing` events disappeared.
- The app became usable immediately without changing AdGuard, account, or network configuration.
This makes the regression strongly specific to desktop build 26.814.41407 rather than the account, local conversation data, or network path.
Related but not identical reports:
- #38482 — macOS authentication/token exchange failure immediately after automatic update.
- #39139 — CLI reports ChatGPT authentication while account-dependent commands still ask the user to sign in.
hsiangron 08-23 16:172楼
yuefeng_yang 08-23 16:223楼