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

Closed
opened 2026-02-16 18:07:21 -05:00 by yindo · 1 comment
Owner

Originally created by @jc-244 on GitHub (Jan 24, 2026).

Originally assigned to: @adamdotdevin on GitHub.

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

Originally created by @jc-244 on GitHub (Jan 24, 2026). Originally assigned to: @adamdotdevin on GitHub. ### Feature hasn't been suggested before. - [x] 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. <img width="292" height="365" alt="Image" src="https://github.com/user-attachments/assets/c0d1ddf6-59a5-4781-ad3b-2eead2996105" /> 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](url) **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**
yindo added the discussionweb labels 2026-02-16 18:07:21 -05:00
yindo closed this issue 2026-02-16 18:07:21 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Jan 24, 2026):

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

  • #10150: [BUG] Azure gpt-5.2-codex (vision-capable) is unable to read screenshots - mentions gpt-5.2-codex specifically
  • #10421: [FEATURE]: OAuth Device Code flow for ChatGPT / Codex plans - related to OAuth and Codex configuration
  • #10454: /models command does not list authenticated Copilot models - related to model discovery and authentication

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

@github-actions[bot] commented on GitHub (Jan 24, 2026): This issue might be related to existing issues about model picker clarity and OAuth configuration. Please check: - #10150: [BUG] Azure gpt-5.2-codex (vision-capable) is unable to read screenshots - mentions gpt-5.2-codex specifically - #10421: [FEATURE]: OAuth Device Code flow for ChatGPT / Codex plans - related to OAuth and Codex configuration - #10454: /models command does not list authenticated Copilot models - related to model discovery and authentication While not exact duplicates, these issues touch on related concerns about model picker clarity and OAuth authentication behavior.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#7496