/model picker omits usable gpt-6-astra and shows an incorrect default model

What version of Codex CLI is running?

codex-cli 0.153.4

What subscription do you have?

ChatGPT Pro

Which model were you using?

gpt-6-astra

What platform is your computer?

Linux 6.6.117-45.1.oc9.x86_64 x86_64 x86_64

What terminal emulator and version are you using (if applicable)?

SSH session from Codebuddy

Codex doctor report

Codex CLI version: 0.153.4
  Background app-server version: 0.148.0
  Authentication mode: ChatGPT
  Configured model: gpt-6-astra
  Latest available CLI version: 0.153.4

What issue are you seeing?

The interactive /model picker does not list gpt-6-astra, even though the model is available to the authenticated account and works when selected explicitly.

The raw model catalog includes Astra:
gpt-6-astra GPT-6-Astra visibility=list

Direct invocation also succeeds:
codex exec --ephemeral --skip-git-repo-check
-m gpt-6-astra
"Reply with exactly ASTRA_OK"

Output:
model: gpt-6-astra
provider: openai
ASTRA_OK

After setting the following configuration:
model = "gpt-6-astra"
model_reasoning_effort = "medium"

…a newly started TUI correctly shows gpt-6-astra in the status line. However, opening /model still omits Astra and incorrectly labels gpt-5.6-sol as the default model.

The picker currently lists:

• gpt-5.6-sol (default)

• gpt-5.6-terra

• gpt-5.6-luna

• gpt-5.5

• gpt-5.4-mini

• gpt-5.3-codex-spark

No API or authentication error is displayed.

What steps can reproduce the bug?

Repro (cleaned up, English, markdown):

1. Install or update Codex CLI:

   bash
   codex update
   codex --version

2. Log in using ChatGPT authentication.

3. Confirm that Astra is present in the model catalog:

   bash
   codex debug models |
   jq '.models[] select(.slug == "gpt-6-astra")
   {slug, display_name, visibility}'

4. Confirm that direct model selection works:

   bash
   codex exec --ephemeral --skip-git-repo-check
   -m gpt-6-astra
   "Reply with exactly ASTRA_OK"

5. Set Astra as the configured model in ~/.codex/config.toml:

   toml
   model = "gpt-6-astra"
   model_reasoning_effort = "medium"

6. Start a new interactive session:

   bash
   codex

7. Inside the TUI, run /model.

8. Observe that gpt-6-astra is absent from the picker, and gpt-5.6-sol
   is shown as the default model (even though the status line correctly shows
   gpt-6-astra).

Thread ID: not applicable.

Note on expected behavior: in Codex CLI 0.153.1+ the bundled gpt-6-astra catalog entry ships with visibility = "hide" (not "list"), so the /model picker intentionally omits it while -m gpt-6-astra / model = "gpt-6-astra" still resolves and runs. If your local codex debug models dump really prints visibility=list, that is a catalog-vs-picker divergence worth filing upstream — but the “status line correct, /model falls back to gpt-5.6-sol” half is the documented gated-rollout behavior, not a config parse bug.

What is the expected behavior?

No response

Additional information

No response

Start with the /model picker and the codex debug models output, using the reported gpt-6-astra catalog entry and ~/.codex/config.toml as comparison points. Reproduce the behavior with codex exec -m gpt-6-astra and an interactive /model session, then determine whether the picker and default label match the catalog visibility and configured model; done means the intended Astra visibility and default behavior are consistent.