bug: /gpt-account add renders an empty OpenAI Codex method prompt

[eddieparc]

What happened?

/gpt-account add sends the OpenAI Codex OAuth select prompt through a text-input adapter. The UI renders a blank input below Select OpenAI Codex login method: rather than the two choices. Submitting it passes an empty method to the OAuth flow and produces Error: Unknown OpenAI Codex login method:.

The extension adapter should render the provided option labels and map the chosen label back to the OAuth option id (browser or device_code).

Steps to reproduce

1. Use OmO Native 5.0.0-0.beta.48 (Senpi 2026.9.7-2) with no existing credentials.
2. Run /gpt-account add in an interactive terminal (also reproduced under Linux tmux with TERM=xterm-256color).
3. Observe the empty field under Select OpenAI Codex login method: and submit it.

No OAuth browser flow, device code, or token was entered during reproduction.

Expected behavior

Render Browser login (default) and Device code login (headless) and pass their ids, respectively browser and device_code, to the OAuth flow. /login → Sign in with an account → OpenAI Codex already does this correctly.

Workarounds: use that /login path, or enter browser / device_code directly into the affected field.

Version

OmO Native 5.0.0-0.beta.48; Senpi 2026.9.7-2.

Fix and verification

The fix branches on prompt.type === "select", uses the extension selector for option labels, and returns the matching option id. Manual/text prompts keep their text-input path.

Verified by a regression test covering both ids, root bun run check, and isolated tmux TUI smoke. No real authentication was performed.

[code-yeongyu]

Duplicate of #1485 — fixed on main by #1486 (merge commit a1ac401). Summary of the landed behaviour and the release that will carry it: #1485 (comment)

Until that senpi release is pinned by OmO Native: /login → Sign in with an account → OpenAI Codex → Device code login (headless).