Repository navigation
feat(models): make GPT-6 current and default to Sol - #406
Merged
Merged
Conversation
incognitojam
changed the title
Move the Codex legacy-classification overlay to the current GPT-6 family. Codex still gets the available model list from its app server, so older GPT-5.6 models remain selectable under Legacy models. This follows the Codex portion of upstream commit 17e3477. Its Claude overlay change is handled in the separate Claude PR, so this is not a full upstream intake record.
incognitojam
force-pushed
the
styal/current-gpt-6-models
branch
from
September 23, 2026 11:17
b8874b2 to
0e58c3b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Codex discovers available models from its own app server, but styal's manifest still classifies GPT-5.6 as current. GPT-6-Astra, GPT-6-Sol, and GPT-6-Luna therefore appear under Legacy models even when the installed Codex CLI offers them. New Codex threads also still default to GPT-5.6-Sol.
Classify the GPT-6 family as current and prefer GPT-6-Sol for new Codex threads. If Sol is unavailable, prefer GPT-6-Astra, then an available GPT-5.6 model; if none of these are present, keep Codex's own reported default. The GPT-5.6 models remain selectable from the live CLI inventory under Legacy models. Choosing Sol over Astra is a deliberate styal default difference from current upstream. This change is separate from the Claude catalog update in #405 because it affects a different provider.
The installed Codex CLI 0.155.1 reported all three GPT-6 models and the GPT-5.6 models in its
model/listresponse. In an isolated headless Chrome run, a fresh composer selected GPT-6-Sol with Medium effort, the picker showed the GPT-6 family as current, and GPT-5.6-Sol appeared under Legacy models. Chrome reported no page errors. Focused Codex provider, manifest, and fork ledger tests passed (28 tests), including preference and fallback cases. Contract and server typechecks, ledger validation, and targeted formatting checks passed. Remote update checks were disabled for the updated local run because the fork's published manifest still predates this PR. No authenticated model inference request was sent.Written by an agent (Codex, GPT-6).