What version of Codex CLI is running?

versions after 0.122.0

What subscription do you have?

Enterprise

Which model were you using?

gpt-5-3-codex-public

What platform is your computer?

Microsoft Windows NT 10.0.22631.0 x64

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

No response

What issue are you seeing?

When Codex is configured through a model gateway, the returned model name includes a provider prefix, e.g.:

openai/gpt-5.3-codex

Codex logs a warning that model metadata is not found, and this warning repeats on every prompt/turn.

What steps can reproduce the bug?

Reproduction steps

1. Use a model gateway that returns provider-prefixed model IDs (example: openai/gpt-5.3-codex).
2. Configure Codex to use that model.
3. Set fallback config values (model_reasoning_effort, model_context_window, model_max_output_tokens).
4. Start Codex and send multiple prompts.
5. Observe the same metadata warning each turn.

Actual behavior

Repeated warning on each prompt cycle for the same unresolved model ID.

What is the expected behavior?

• Warn once per session (or once per normalized model key), not every turn.
• Ideally normalize model IDs from gateway/provider formats before metadata lookup and warning dedupe.

Additional information

Proposed fix

• Normalize/tokenize gateway model strings before lookup and dedupe.
• Track warned keys in-session and suppress duplicates.
• Optional exit summary: “Suppressed N duplicate metadata warnings.”

Why this matters

• Reduces warning noise.
• Prevents warning fatigue.
• Keeps logs useful for actionable problems.
• Users may already supply explicit fallback metadata.

Related issues

• Model metadata for gpt-5-codex not found. Defaulting to fallback metadata; this can degrade performance and cause issues #12100
• "Model metadata for gpt-oss:20b not found" with ollama #14757
• --model flag accepted but fails with "model not supported" on ChatGPT accounts #12295