Repository navigation
[Bug]: Sol 6.1 incorrectly categorized under legacy models instead of current #14301
Description
Activity
Already covered by open PR #14294 (
feat(models): add GPT-6.1-Sol), which addsgpt-6.1-soltocurrentModels.codex(and movesgpt-6-solto legacy). Linked viaFixes #14301.Reacted by Rik VisserThanks for taking the time to report this and provide the details. We revisited it during the orchestrator V2 cleanup.
Current model manifest lists gpt-6.1-sol in currentModels.codex; legacy classification checks membership in this overlay. Related PR 14294 is closed unmerged, so closure rests on current source rather than that PR.
I’m closing this based on the current source and the evidence in this thread.
Old clients or cached remote manifests may require refresh; no live model-picker check.
If you still hit this on a current build, please reply with the app/server versions and the steps that reproduce it. We can reopen this if the original problem is still there.
Before submitting
Area
Not sure
Steps to reproduce
Expected behavior
Sol 6.1 should be categorized under current models, while Sol 6 should remain under legacy models.
Actual behavior
Sol 6.1 is currently appearing under legacy models instead of current models.
Impact
Minor bug or occasional failure
Version or commit
0.0.43-nightly.20260929.2450 (27bdf1a)
Environment
macOS 27.0 (26A428)
Logs or stack traces
Screenshots, recordings, or supporting files
Screenshot 2026-09-29 at 21.00.57.png
Workaround
Choose Sol 6.1 from the legacy models dropdown.