Repository navigation
chore: add model to catalog - #1714
Erin McNulty (erin2722) merged 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. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 67a1723e63
ℹ️ 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".
| "available_providers": [ | ||
| "databricks" |
There was a problem hiding this comment.
When a user selects databricks-kimi-k3.1-pro with Databricks credentials, this entry advertises a route that Databricks does not currently offer, so the upstream request will fail for an unknown model/service. The official Databricks-hosted inference catalog, last updated 2026-11-02, lists Kimi K3 as the sole Moonshot model; add this provider mapping only after K3.1 Pro appears in the provider catalog.
Useful? React with 👍 / 👎.
Automated targeted model-catalog addition from the model-drop workflow.