Skip to content

feat(tui): ChatGPT account launch uses the same picker as providers - #86

Open
xjoker wants to merge 1 commit into
devfrom
cursor/tui-account-launch-dd00
Open

feat(tui): ChatGPT account launch uses the same picker as providers#86
xjoker wants to merge 1 commit into
devfrom
cursor/tui-account-launch-dd00

Conversation

@xjoker

@xjoker xjoker commented Aug 27, 2026

Copy link
Copy Markdown
Owner

Summary

TUI launch on the Accounts tab was an immediate start with no model, reasoning, or extra argv. Providers already had a picker. Accounts o (list and account menu) now opens that same picker.

  • First row is (Codex default) (no --model), matching the previous one-key launch.
  • Cached ChatGPT /models slugs appear when the TUI has already fetched them.
  • One-shot reasoning and Tab extra argv apply to this launch only.
  • Confirming still stages that ChatGPT profile’s auth.json.
  • ChatGPT launch splices --model and -c model_reasoning_effort=… after exec / resume / … (Codex 0.149).

Enter on Accounts still opens the account menu.

Tests

  • TUI: Accounts o / menu o open the picker; default row omits --model; picking a cached slug keeps its default reasoning and extra argv.
  • Picker render title is Launch account.
  • chatgpt_codex_argv places --model and reasoning -c after exec.
  • CLI: launch work -- exec --json ping still passes through with no --model.

Docs

Changelog Unreleased plus Feature-Guide / Command-Reference / Providers / Chinese-Guide.

Open in Web Open in Cursor 

Accounts o (list and menu) opens the launch picker: Codex default or a
cached /models slug, one-shot reasoning, and extra Codex argv. Confirming
still stages that profile. ChatGPT launch now splices --model and
model_reasoning_effort after exec.

Co-authored-by: lolitaupdate <lolitaupdate@gmail.com>
@xjoker
xjoker marked this pull request as ready for review August 27, 2026 10:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants