chore: sync new models - #1145
Conversation
a2d606d to
d789964
Compare
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d789964e23
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "Codex (@codex) review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "Codex (@codex) address that feedback".
| "gpt-5.6-sol": ["openai", "azure", "openrouter"], | ||
| "gpt-5.6-terra": ["openai", "azure", "openrouter"], | ||
| "gpt-5.6": ["openai", "azure"], | ||
| "gpt-5.6-cyber": ["openai", "azure"], |
There was a problem hiding this comment.
Move provider mappings to the active gateway
This addition, along with the Daybreak mappings below, changes AvailableEndpointTypes, which is the deprecated proxy's provider-routing table. Repository instructions explicitly direct model-routing changes to the parent repository's gateway/ directory, so these edits update only the legacy implementation rather than active production routing; retain the valid catalog additions in model_list.json but apply any required routing changes in the gateway.
AGENTS.md reference: AGENTS.md:L6-L12
Useful? React with 👍 / 👎.
| "available_providers": [ | ||
| "openai", | ||
| "azure" | ||
| ] |
There was a problem hiding this comment.
Link the Daybreak Blue alias to its Bedrock model
When daybreak-blue-latest is requested where Bedrock is the usable provider, this entry exposes only OpenAI/Azure and has no fallback_models, even though the existing openai.gpt-daybreak-blue-5.6-sol catalog entry identifies itself as Daybreak Blue and maps to Bedrock. Because getModelEndpointTypes unions equivalent providers only through fallback_models, this new alias cannot select that Bedrock endpoint; add the existing Bedrock model ID as a fallback, as is done for gpt-5.6-cyber.
Useful? React with 👍 / 👎.
Add openai.gpt-daybreak-blue-5.6-sol to daybreak-blue-latest's fallback_models so getModelEndpointTypes can union the Bedrock endpoint for this alias, mirroring how gpt-5.6-cyber links to openai.gpt-5.6-cyber (addresses codex P2). daybreak-red-latest correctly keeps no fallback (no Bedrock counterpart exists). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Automated sync of model metadata and newly available models from the approved provider allowlist.