Skip to content

Spark shows available quota, but does not appear in the selector and the server rejects its use #45728

Open
Open
Spark shows available quota, but does not appear in the selector and the server rejects its use#45728
Labels
CLIIssues related to the Codex CLIbugSomething isn't workingrate-limitsIssues related to rate limits, quotas, and token usage reportingwindows-osIssues related to Codex on Windows systems

Description

@carlosmanuelfernandezsosa2004-ui
carlosmanuelfernandezsosa2004-ui
opened on Sep 15, 2026

Entorno

  • Windows x64, PowerShell.
  • Codex CLI 0.154.0.
  • Inicio de sesión con una cuenta de ChatGPT completado correctamente.

Problema observado

En el momento de la prueba, /status mostraba:

  • Límite de cinco horas de GPT-5.3-Codex-Spark: 100 % disponible.
  • Límite semanal de Spark: 50 % disponible.
  • Límite general semanal: 0 % disponible.

Sin embargo, gpt-5.3-codex-spark no aparece en el selector /model. Al solicitarlo directamente, el servidor devuelve un error 400:

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

Pasos realizados

  1. Instalar Codex CLI y comprobar la versión con codex --version.
  2. Completar codex login con la cuenta de ChatGPT.
  3. Ejecutar esta prueba:
codex exec --skip-git-repo-check --sandbox read-only -m gpt-5.3-codex-spark "Responde solo con OK. No uses herramientas ni accedas a archivos."
  1. Observar el rechazo del servidor indicado arriba.
  2. Abrir una sesión interactiva de Codex y revisar /status y /model: se muestra cuota de Spark disponible, pero el modelo no figura en el selector.

Resultado esperado y solicitud

Por favor, revisen la discrepancia entre la cuota mostrada y el acceso real. Confirmen si Spark debe estar disponible para esta modalidad de inicio de sesión y, en caso contrario, expliquen claramente por qué siguen apareciendo límites disponibles.

No se ha confirmado la causa del rechazo ni que el límite general agotado sea su causa. Se solicita una aclaración y los pasos necesarios para resolver la discrepancia.

No se adjuntan capturas, correo, enlaces de inicio de sesión ni identificadores de sesión.

Activity

  1. github-actions
    added
    bugSomething isn't working
    CLIIssues related to the Codex CLI
    windows-osIssues related to Codex on Windows systems
    rate-limitsIssues related to rate limits, quotas, and token usage reporting
    on Sep 15, 2026
  2. github-actions
    changed the title [-]Spark muestra cuota disponible, pero no aparece en el selector y el servidor rechaza su uso[/-] [+]Spark shows available quota, but does not appear in the selector and the server rejects its use[/+] on Sep 15, 2026

  3. github-actions commented on Sep 15, 2026

    @github-actions
    github-actionsBot
    on Sep 15, 2026 – with GitHub Actions
    Contributor

    English translation:

    Environment

    • Windows x64, PowerShell.
    • Codex CLI 0.154.0.
    • Successfully signed in with a ChatGPT account.

    Observed problem

    At the time of testing, /status showed:

    • GPT-5.3-Codex-Spark five-hour limit: 100 % available.
    • Spark weekly limit: 50 % available.
    • Overall weekly limit: 0 % available.

    However, gpt-5.3-codex-spark does not appear in the /model selector. When requesting it directly, the server returns a 400 error:

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

    Steps taken

    1. Install Codex CLI and check the version with codex --version.
    2. Complete codex login with the ChatGPT account.
    3. Run this test:
    codex exec --skip-git-repo-check --sandbox read-only -m gpt-5.3-codex-spark "Responde solo con OK. No uses herramientas ni accedas a archivos."
    1. Observe the server rejection indicated above.
    2. Open an interactive Codex session and check /status and /model: available Spark quota is shown, but the model is not listed in the selector.

    Expected result and request

    Please investigate the discrepancy between the displayed quota and actual access. Confirm whether Spark should be available for this sign-in method and, if not, clearly explain why available limits are still displayed.

    Neither the cause of the rejection nor whether the exhausted overall limit is its cause has been confirmed. Clarification and the steps needed to resolve the discrepancy are requested.

    No screenshots, email, sign-in links, or session identifiers are attached.

  4. github-actions commented on Sep 15, 2026

    @github-actions
    github-actionsBot
    on Sep 15, 2026 – with GitHub Actions
    Contributor

    Potential duplicates detected. Please review them and close your issue if it is a duplicate.

    Powered by Codex Action

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    CLIIssues related to the Codex CLIbugSomething isn't workingrate-limitsIssues related to rate limits, quotas, and token usage reportingwindows-osIssues related to Codex on Windows systems

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions