Repository navigation
Classify Daybreak models as specialized access-gated, not legacy #7597
Description
Activity
I’m seeing the same issue with Codex connected through CLIProxyAPI.
Codex’s
model/listincludes both GPT and Claude models from the proxy. T3 marks every model as legacy unless it matches one of three hardcoded GPT-5.6 slugs. This puts all 15 Claude models under “Legacy models,” even when they are current.The “Codex” label makes sense because Codex is still the runtime. The legacy classification is the bug.
Instead of adding more models to the allowlist, unknown or proxied models should not be treated as legacy by default.
Summary
Daybreak Blue/Red are currently handled as legacy models, but OpenAI docs show them as active specialized models behind trusted access. They are shown with dedicated access tiers, not legacy deprecation.
gpt-daybreak-blue(alias:gpt-5.6-sol)gpt-daybreak-red(alias:gpt-5.6-cyber)Expected behavior
gpt-5.5-cyber-preview(if present) in legacy handling, since OpenAI marks it as legacy.Evidence
Screenshot
Screenshot attached in this issue.