Feature Request: Skip the extra Enter prompt after web auth login

Resolved 💬 1 comment Opened Nov 7, 2025 by Jarrodsz Closed Dec 31, 2025

Summary

After completing “Sign in with ChatGPT” in the browser, the CLI returns to a screen that says “Press Enter to continue…” before finally dropping back into the Codex prompt. This extra acknowledgement offers no new information—the authentication is already complete—and forces users to hit Enter every single time. Please make this pause optional (e.g., auto-advance immediately, or gate it behind a config flag) so a successful login lands straight back at the prompt with no extra keystroke.

Current behavior

  1. Run codex and choose Sign in with ChatGPT.
  2. Finish the device-code flow in the browser.
  3. Return to the terminal: Codex prints a confirmation but then waits on “Press Enter to continue…”.
  4. Only after pressing Enter does the TUI load.

Desired behavior

  • As soon as authentication succeeds, Codex should resume the session automatically (or offer a suppress_login_pause = true option in config.toml).
  • Users coming back from the browser should see the prompt immediately, ready to type /status or a normal instruction.

Motivation

  • The extra confirmation is redundant; everything shown on that screen (login success, account email) is already printed in the log.
  • It slows down repeated logins, especially when scripts or IDE integrations relaunch Codex frequently.
  • Accessibility: some setups trigger Codex from other windows/terminals, so having to refocus solely to hit Enter is disruptive.

Environment

  • codex-cli 0.55.0
  • macOS 15 (Darwin 25.0.0 arm64)
  • Auth: Sign in with ChatGPT

Additional context

If the pause is needed for users who want to read the success message, it could remain the default while exposing a config flag or prompt answer like “Automatically continue after login? (y/n)”. The key request is to eliminate the mandatory keystroke for users who just want to get back to the TUI.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗