Repository navigation
chore: add model to catalog - #1722
github-actions[bot] wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1cb0d7e479
ℹ️ 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".
| "format": "openai", | ||
| "flavor": "chat", | ||
| "displayName": "moonshotai-kimi-k3", | ||
| "fallback_models": [ |
There was a problem hiding this comment.
Include all existing Kimi K3 provider fallbacks
When a request uses this new slug and Cerebras is unavailable or rate-limited, the fallback graph only considers model IDs explicitly listed here (getModelEndpointTypes in schema/index.ts). The catalog already exposes the same Kimi K3 as accounts/fireworks/models/kimi-k3 and moonshotai/Kimi-K3 for Fireworks, Baseten, and Together, but neither ID is included, so those configured providers cannot be considered while the listed Bedrock, Databricks, and OpenRouter aliases can. Add both existing IDs to complete the provider-family fallback set.
Useful? React with 👍 / 👎.
Automated targeted model-catalog addition from the model-drop workflow.