Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Desktop app model selector briefly shows Custom when opening conversations [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#19263•Fetched 2026-04-24 10:39:50
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
GGBondBlueWhaleGGBondBlueWhale
Participants
GGBondBlueWhaleGGBondBlueWhalegithub-actions[bot]github-actions[bot]
Timeline (top)
labeled ×3commented ×1

Root Cause

This is confusing because it looks like the model setting has been reset or lost. It is also unclear what model/configuration will actually be used if I send a prompt while the selector is still showing Custom.

RAW_BUFFERClick to expand / collapse

What version of the Codex App are you using (From “About Codex” dialog)?

Version 26.422.21637 (2056)

What subscription do you have?

Pro

What platform is your computer?

macOS

What issue are you seeing?

When I open a new conversation, or open an existing/old conversation, the model selector initially shows Custom instead of the actual selected model.

After waiting for a short time, the selector changes back to the currently selected model, for example 5.5 Extra High.

This is confusing because it looks like the model setting has been reset or lost. It is also unclear what model/configuration will actually be used if I send a prompt while the selector is still showing Custom.

What steps can reproduce the bug?

  1. Open the Codex desktop app.
  2. Select a model, for example 5.5 Extra High.
  3. Start a new conversation, or open an existing/old conversation.
  4. Look at the model selector immediately after the conversation loads.
  5. The selector temporarily shows Custom.
  6. After waiting for a short time, it changes back to the actual selected model, such as 5.5 Extra High.

What is the expected behavior?

The model selector should immediately show the actual selected model when a new or existing conversation is opened.

For example, if the selected model is 5.5 Extra High, it should display 5.5 Extra High right away and should not temporarily display Custom unless the conversation is actually using a custom configuration.

Additional information

Permission mode shown in the UI: Full access.

I can provide screenshots showing:

  • The app version: 26.422.21637 (2056)
  • The selector temporarily showing Custom
  • The selector later showing 5.5 Extra High
<img width="1730" height="756" alt="Image" src="https://github.com/user-attachments/assets/f8c42fcf-6a50-4665-ba32-59942e4ba038" /> <img width="582" height="406" alt="Image" src="https://github.com/user-attachments/assets/0fa74b85-5218-4904-9feb-2ba4b5cbfbef" />

extent analysis

TL;DR

The issue can be mitigated by waiting for a short time after opening a conversation, allowing the model selector to update to the actual selected model.

Guidance

  • Verify that the issue is specific to the Codex App version 26.422.21637 (2056) and not a general problem with the model selector.
  • Check if the issue persists when using different models or conversation types to determine if it's model-specific.
  • Consider providing more details about the conversation loading process to help identify potential causes of the delay in updating the model selector.
  • Test if the issue occurs when the app is run with a different permission mode, such as limited access, to see if it's related to permission settings.

Notes

The provided information suggests a timing issue with the model selector update, but without further details about the app's internal workings or the conversation loading process, it's difficult to provide a definitive fix.

Recommendation

Apply workaround: wait for the model selector to update after opening a conversation, as the issue seems to resolve itself after a short time. This is recommended because it allows users to continue using the app with minimal disruption while a more permanent fix is investigated.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#chain error#conversation history#tool integration#LLM response#prompt template

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Desktop app model selector briefly shows Custom when opening conversations [1 comments, 2 participants]