Troubleshooting Codex Sign-In

Feature statusReference
Applies to0.13.0-alpha.1 (pre-alpha)
Last verified2026-07-31

Symptom: the sign-in link doesn't open automatically

Likely cause: the automatic browser handoff didn't trigger, or your device doesn't have a default browser configured for it.
What to try: use the tap-to-open option shown alongside the link, or copy the printed URL and open it manually in your browser.
Data preserved: unaffected — this doesn't touch your projects or other sessions.

Symptom: sign-in seems stuck after completing the browser step

Likely cause: a network interruption between your device and OpenAI's sign-in servers, or the browser step wasn't fully completed.
What to try: confirm you have a working network connection, return to Deputy Shell, and try signing in again from the start.
Data preserved: your projects and other sessions are unaffected regardless of Codex sign-in status.

When to contact support

If sign-in repeatedly fails with a working network connection, create a diagnostics export (it excludes credentials and terminal content) and contact support@deputyshell.com with your device model and Android version.