Skip to content

[FEATURE]: [Desktop][OAuth] Clarify gpt-5.2 vs gpt-5.2-codex (both route to CODEX_API_ENDPOINT) #10476

Closed

Description

@jc-244

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

Hi, I noticed that after connecting OpenAI via ChatGPT Pro/Plus OAuth (subscription login), the model picker shows both gpt-5.2 and gpt-5.2-codex.

Image

However, in OAuth mode the custom fetch seems to rewrite any request to the same Codex endpoint. Given this, it looks like both gpt-5.2 and gpt-5.2-codex are routed to the same CODEX_API_ENDPOINT:

https://github.com/anomalyco/opencode/blob/460513a83530d76bd5c3aa61c2e4e6b0dcce8536/packages/opencode/src/plugin/codex.ts#L445-L458

Question: Are gpt-5.2 and gpt-5.2-codex meaningfully different in OAuth mode, or just aliases under the same Codex route?
Request: If the route is the same, please clarify in the model picker (label/rename) or collapse the duplicate option.
THANK YOU

Activity

  1. added
    discussionUsed for feature requests, proposals, ideas, etc. Open discussion
    on Jan 25, 2026
  2. github-actions commented on Jan 25, 2026

    @github-actions
    Contributor

    This issue might be related to existing issues about model picker clarity and OAuth configuration. Please check:

    While not exact duplicates, these issues touch on related concerns about model picker clarity and OAuth authentication behavior.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

discussionUsed for feature requests, proposals, ideas, etc. Open discussionwebRelates to opencode on web / desktop

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions