Codex RescueCodex troubleshooting
Codex login & authentication errors
Troubleshoot Codex login failures, browser callbacks and authentication problems. Identify the affected client and follow source-linked recovery steps.
A browser sign-in can finish while the Codex client still waits for a callback. Authentication failures can also depend on the selected account or client environment. Use the login guide to locate the failing step before signing in again.
A sign-in failure can occur before the browser opens, while an account is selected, while the browser returns to the local client, or when a later session refresh happens. The first useful question is therefore where the flow stopped. Record the client, platform and visible stage. A successful browser page does not by itself prove that the CLI or desktop app received its callback, and a previously logged-in status does not guarantee that a later request can refresh its session.
Open the linked guide for the stage-by-stage checks, keeping authorization codes, tokens, cookies and callback URLs out of public screenshots. Do not reset the whole Codex home just to retry authentication; doing so can disturb saved session state while leaving the underlying callback or account problem unchanged. If the only symptom is a quota notice after login, use the usage-limit section instead. If a public incident is active, note its affected component before treating a local sign-in message as a service-side event.
What to check first
- Note whether the failure happens in the browser or the Codex client.
- Check that the expected account and workspace are selected.
- Keep tokens and authorization codes out of screenshots and support messages.
Login troubleshooting guides
Codex login failed? Troubleshoot sign-in
Identify whether the browser, local callback or token exchange failed; use the callback port shown by your client.
Back to all Codex error messages →
Reached a usage limit instead? Check Codex usage limits and reset times.