Skip to content

[Bug]: Codex picker shows Ultrafast selected when CLIProxyAPI serves Standard #40652

Closed as not planned

Description

@stijnhoste

Area

Codex model picker and provider integration.

Account context

I’m on the $20/month ChatGPT Plus plan. In my T3 setup, Codex connects through CLIProxyAPI, and the picker still offers Ultrafast for GPT-6.2 Sol. The probe used the same configured proxy endpoint. I did not independently verify which upstream account the proxy selected for that request.

Steps to reproduce

  1. Connect T3 to a local Codex app-server configured to use CLIProxyAPI as its Responses provider.
  2. Choose GPT-6.2 Sol with Medium reasoning and select Ultrafast in the T3 composer.
  3. Send a short prompt. The picker shows Ultrafast selected, and T3 records the requested tier as Ultrafast.
  4. Independently send a short GPT-6.2 Sol request to the same CLIProxyAPI WebSocket endpoint with service_tier: "ultrafast". Inspect response.service_tier in the final response.completed event.

Expected behavior

When a completed response reports a different tier, T3 should surface the served tier or show that the request fell back to Standard. When the provider only exposes the requested tier, the UI should distinguish that selection from a verified effective tier. A model catalog entry alone cannot establish account eligibility, particularly for a proxy whose upstream credentials T3 may not know.

Actual behavior

T3 makes Ultrafast selectable for GPT-6.2 Sol and shows it as selected without indicating whether the provider honored it. The local Codex model catalog advertises Ultrafast for Sol. The independent WebSocket request succeeded at the default tier:

Request:             model=gpt-6.2-sol  service_tier=ultrafast
response.created:    service_tier=auto
response.completed:  service_tier=default  status=completed

CLIProxyAPI v8.0.79's request translator preserves the Ultrafast value. The test verifies the completed tier for the direct probe. The T3 run record verifies the requested tier for the UI turns. OpenAI's Codex plan documentation also lists Ultrafast as unavailable on ChatGPT Plus for direct ChatGPT sign-in.

Impact

The picker gives the impression that Ultrafast is active even when the configured provider serves the request at Standard speed.

Version and environment

  • T3 server 0.1.11-nightly.20261120.4979 on Linux (Omarchy)
  • Codex CLI 0.171.0
  • CLIProxyAPI v8.0.79, Responses WebSocket endpoint

Activity

  1. juliusmarminge commented on Nov 22, 2026

    @juliusmarminge
    Member

    Thanks for writing this up. It asks for new behaviour rather than reporting a defect, so it does not belong in the bug tracker and I'm closing it as not planned here. Feature ideas are discussed in Discussions: please post it there.

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions