Sub2API screenshot shows gpt-5.6-sol requests returning gpt-6-sol
A community screenshot shows requests sent as gpt-5.6-sol returning gpt-6-sol in the upstream response metadata, triggering a model mismatch warning, alongside other hints like a third-party platform adding a gpt-6-sol entry and Codex weakening 5.6 Sol's description.
GPT-6 Sol may already be sitting behind some GPT-5.6 Sol traffic 👀 A community Sub2API screenshot shows requests sent as gpt-5.6-sol returning: response.model = gpt-6-sol which triggers a Model mismatch warning. Sub2API reads that from the upstream response metadata, not from the model self-identifying. Then on Sept 19, third-party platform Okou merged: “feat(api-contracts): add gpt-6-sol run model” adding a separate gpt-6-sol entry alongside Astra across its model catalog, provider mappings and Codex runtime: https://github.com/okou-ai/okou/pull/35391 Two days later, OpenAI changed GPT-5.6 Sol’s Codex description from: “Latest frontier agentic coding model.” to: “Reliable agentic workhorse for everyday tasks.” https://github.com/openai/codex/pull/47085 My theory: 5.6 Sol could be the public-facing name while some traffic is already routed to a backend labeled gpt-6-sol. Could still just be internal routing/catalog cleanup. No official confirmation yet.