chore: update model catalog from bot issues - #1281
Conversation
|
Codex (@codex) review |
|
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: 26f014ba86
ℹ️ 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".
| "moonshotai.kimi-k3": ["bedrock"], | ||
| "us.moonshotai.kimi-k3": ["bedrock"], | ||
| "global.moonshotai.kimi-k3": ["bedrock"], | ||
| "gemini-3.8-live": ["google"], | ||
| "gemini-3.8-live-extended-thinking": ["google"], |
There was a problem hiding this comment.
Move endpoint-routing additions to the gateway repository
These AvailableEndpointTypes entries modify provider-routing metadata in the deprecated proxy, even though the repository guidance directs all model-routing work to the parent gateway/ repository and permits only model_list.json catalog changes here. The entries are also unnecessary locally because each new model’s format already resolves to the same default endpoint type; keep the catalog additions but remove these index.ts changes and apply any required routing update in ../gateway/.
AGENTS.md reference: AGENTS.md:L10-L15
Useful? React with 👍 / 👎.
Automated daily batch of model catalog updates from bot issues.
Included issues
Summary
moonshotai.kimi-k3us.moonshotai.kimi-k3global.moonshotai.kimi-k3moonshotai.kimi-k3us.moonshotai.kimi-k3global.moonshotai.kimi-k32
gemini-3.8-livegemini-3.8-live-extended-thinkinggemini-3.8-livegemini-3.8-live-extended-thinking2
3
4
5
Verified metadata
#1271: [BOT ISSUE] Bedrock: add missing Moonshot Kimi K3 models (moonshotai.kimi-k3 + geo variants)
Verification notes
No LLM verification step ran; model metadata was already complete in the issue.
sync_models vs proposed update
sync_models cross-check found differences. Official provider verification was used for the applied values, and sync_models discrepancies are listed below for review.
#1279: [BOT ISSUE] Google: add missing gemini-3.8-live and gemini-3.8-live-extended-thinking
Verification notes
Verification Checklist
sync_models vs proposed update
sync_models cross-check found no pricing/token discrepancies for the changed models.
No sync_models discrepancies were noted.