codex_auth

Open the ChatGPT account page in the user's browser.

Used by /auth to let signed-in users jump to chatgpt.com (e.g., to change account, manage billing).

Run the ChatGPT OAuth Authorization Code Flow with PKCE inline.

Dismissal value:

• True: a token was saved (caller should refresh provider lists / retry the operation that needed the credential).
• False: the user cancelled, or the flow failed irrecoverably.

The flow lives in a worker so the modal stays responsive to the cancel keybinding while _wait_for_oauth_callback blocks for up to 5 minutes; pressing Esc sets the worker's cancel_event, which frees the loopback port within one poll interval rather than holding it until the timeout.

Outcome of the CodexSignedInScreen quick-action overlay.

Encoded as an enum (mirroring AuthResult) rather than bare strings so a typo in either the producing action_* method or the consuming dispatch is a type error, not a silent no-op.

Quick-action overlay shown when openai_codex is already signed in.

Dismissal values:

• CodexSignedInAction.SIGN_OUT: delete the stored token.
• CodexSignedInAction.REAUTH: open the OAuth flow again.
• None: close without changes.

ChatGPT OAuth integration for the openai_codex model provider.

Thin orchestration layer over langchain_openai.chatgpt_oauth. Reuses the upstream PKCE/token primitives directly (_generate_pkce_pair, _build_authorize_url, _CallbackHandler, _post_form, _token_from_response, _FileChatGPTOAuthTokenProvider) so this module only adds:

• a UI-friendly entry point that surfaces the authorize URL to the caller before the callback server starts blocking (the upstream login_chatgpt uses print(), which is invisible inside a Textual app),
• a cancel-aware reimplementation of the loopback callback wait so a cancelled sign-in releases the bound port promptly instead of holding it until the upstream wall-clock timeout elapses (see _wait_for_oauth_callback), and
• helpers for /auth to read sign-in status, expiry, and the linked account without re-implementing token parsing.

The browser-loopback flow mirrors the MCP one in mcp_auth from the user's POV — PKCE + state CSRF + browser launch with a manual-URL fallback — but the callback server here is upstream's single-threaded polling http.server.HTTPServer (reused via _CallbackHandler), not the ThreadingHTTPServer that mcp_auth runs itself. The OAuth-specific parts (token exchange, refresh, file storage with 0600 perms) are delegated to upstream.