ChatGPT desktop Codex sign-in loop after successful authentication
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
Title: ChatGPT desktop Codex sign-in loop after successful authentication
After signing in with ChatGPT, Codex in the macOS desktop app briefly recognizes my account, then immediately returns to the sign-in screen. The bundled Codex CLI remains authenticated and successfully completes prompts.
Environment:
- macOS 26.3.1 (25D2128)
- ChatGPT desktop 26.820.60940 (build 7119), bundle com.openai.codex
- Bundled CLI 0.150.0-alpha.8
- MonoProxy: HTTP 127.0.0.1:8118, SOCKS5 127.0.0.1:8119
Reproduction:
- Sign in using ChatGPT/device authorization.
- CLI login status reports “Logged in using ChatGPT”; an authenticated prompt returns AUTH_OK.
- Launch ChatGPT with proxy variables inherited.
- Open Codex; it returns to the sign-in page.
Key log sequence:
- account lookup succeeds: authenticatedAccountPresent=true
- GET /backend-api/accounts/:param/settings uses cached token but returns 401
- error: “Missing valid access token or actor biscuit”
- auth status then changes to hasToken=false, nullReason=auth_token_missing, refreshToken=true
- account lookup fails with account_info_token_unavailable
- subsequent /wham requests return 401 without an attached token
I reinstalled the official signed app, reset its preferences/caches/containers, logged out/in again, and tested system/global proxy plus explicit proxy variables. The CLI and WebSocket connection now work, but the desktop 401/login loop remains.
Please investigate whether the desktop client or backend is losing the actor biscuit or account/workspace binding. No tokens, auth.json, device codes, or account IDs are included.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the loop in the macOS desktop Codex flow and inspect the reported authentication sequence around the account settings and /wham requests. Trace where the cached token, actor biscuit, or account binding becomes unavailable; done means the desktop client remains signed in and authenticated prompts work without changing the already-working CLI behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, rust
- Domain
- authentication, desktop
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100