fix(server): keep Daybreak Blue out of legacy models - #6193
Closed
t3-code[bot] wants to merge 1 commit into
Closed
Conversation
github-actions
Bot
added
vouch:trusted
Contributor
Thread transfer impact
This comment will update automatically after the next completed run. |
![macroscopeapp[bot]](https://avatars.githubusercontent.com/in/900172?s=60&v=4){kind=small}
Contributor
ApprovabilityVerdict: Approved 82553a4 Simple configuration change adding 'gpt-daybreak-blue-latest' to the current Codex models allowlist. The change only affects whether this model is tagged as legacy in UI model listings, with corresponding test coverage. You can customize Macroscope's approvability policy. Learn more. |
Contributor
Author
|
closing as already addressed. Daybreak legacy-model classification merged in #7659. |
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
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.
What Changed
Treat
gpt-daybreak-blue-latestas a current Codex model and cover it in the model classification regression test.Why
Daybreak Blue was incorrectly marked as legacy in model listings, which hid it behind the legacy model treatment.
Checklist
Verified with the focused provider test (7 tests), server typecheck, targeted lint, and
git diff --check.Model: OpenAI
Harness: T3bot
Note
Low Risk
Single allowlist entry and test update; only affects Codex model classification in the UI/listings.
Overview
Adds
gpt-daybreak-blue-latestto the server's current Codex model allowlist soisLegacyCodexModelno longer flags it and model listings stop applying legacy treatment to Daybreak Blue.The classification regression test is updated to assert Daybreak Blue is non-legacy alongside the other current GPT-5.6 family slugs.
Reviewed by Cursor Bugbot for commit 82553a4. Bugbot is set up for automated code reviews on this repo. Configure here.
Note
Keep
gpt-daybreak-blue-latestout of legacy Codex modelsAdds
gpt-daybreak-blue-latestto theCURRENT_CODEX_MODELSset in CodexProvider.ts, soisLegacyCodexModelreturnsfalsefor this model. The test in CodexProvider.test.ts is updated to cover this model.Macroscope summarized 82553a4.