v0.3.2 — GPT-6 Sol and Luna

The accepted model set now matches the listed entries of the live Codex catalog (/backend-api/codex/models), and the proxy impersonates the latest Codex CLI.

Models (#5)

• gpt-6-sol and gpt-6-luna are accepted and advertised, after gpt-6-astra in catalog order. Both require minimal_client_version 0.155.0.
• gpt-5.5 is accepted again. The catalog still lists it for the pro plan, and it answers over a ChatGPT account again (it returned 400 on 2026-09-07). It is deliberately absent from the sample fallback maps: if the pool refuses it, clients see that error rather than a paid answer.
• Hidden catalog entries (gpt-reserve, codex-auto-review) are neither advertised nor accepted. Older generations the catalog no longer lists (gpt-5.4, the *-codex models) are still refused with model_not_found.

Verified live over a ChatGPT pro account: gpt-6-sol, gpt-6-luna, gpt-6-astra and gpt-5.5 all complete.

Codex CLI 0.155.1

The impersonated CLI version moves 0.153.4 → 0.155.1 (upstream.cli_version, CODEXPROXY_CLI_VERSION). Besides the User-Agent fingerprint, the catalog endpoint filters by client_version, so an older identity would not see the new models at all.

Fallback maps

If you map gpt-6 models onto OpenRouter, note the price spread there: gpt-6-astra $10/M input and $50/M output, gpt-6-sol $2/M and $10/M, gpt-6-luna $0.10/M and $0.50/M. Mapping gpt-6-astra to openai/gpt-6-sol keeps a pool outage from being billed at astra prices.