GPT-5.3-Codex-Spark quota visible but model unavailable for ChatGPT Pro account #45972

What version of Codex CLI is running?

0.154.0

What subscription do you have?

ChatGPT Pro

Which model were you using?

gpt-5.3-codex-spark

What platform is your computer?

macOS, Apple Silicon (arm64), MacBook Pro

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

Apple Terminal.app

Codex doctor report

Diagnostics and logs were uploaded through the Codex /feedback command.

Thread ID: 01a0aae8-5907-72c3-b35e-146eff26d6fa

Codex CLI version: 0.154.0
Login method: ChatGPT
Error received:

HTTP 400 invalid_request_error:
"The 'gpt-5.3-codex-spark' model is not supported when using Codex with a ChatGPT account."

The ChatGPT usage page shows available GPT-5.3-Codex-Spark 5-hour and weekly quotas, but the model does not appear in the model selector.

What issue are you seeing?

My ChatGPT Pro account shows separate GPT-5.3-Codex-Spark 5-hour and weekly usage quotas, but the model does not appear in the Codex model selector.

When I manually start Codex with:

codex -m gpt-5.3-codex-spark

the CLI accepts the model name. However, sending any prompt fails with:

HTTP 400 invalid_request_error
"The 'gpt-5.3-codex-spark' model is not supported when using Codex with a ChatGPT account."

Codex login status reports:
Logged in using ChatGPT

What steps can reproduce the bug?

Uploaded thread: 01a0aae8-5907-72c3-b35e-146eff26d6fa

What is the expected behavior?

GPT-5.3-Codex-Spark should appear in the Codex model selector and should accept requests through my ChatGPT Pro account, because separate Spark 5-hour and weekly usage quotas are visible on the account usage page.

Additional information

Codex CLI version: 0.154.0
Subscription: ChatGPT Pro
Platform: macOS, Apple Silicon
Terminal: Apple Terminal.app
Authentication: Logged in using ChatGPT

The CLI also displayed:
"Model metadata for 'gpt-5.3-codex-spark' not found. Defaulting to fallback metadata."

Diagnostic logs were uploaded through the Codex /feedback command.

Thread ID:
01a0aae8-5907-72c3-b35e-146eff26d6fa