fix: add Databricks models databricks-gpt-5 +2 more#650
fix: add Databricks models databricks-gpt-5 +2 more#650github-actions[bot] wants to merge 1 commit into
Conversation
|
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: e8a4593463
ℹ️ 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".
| "flavor": "chat", | ||
| "multimodal": true, | ||
| "displayName": "GPT-5", | ||
| "max_input_tokens": 400000, |
There was a problem hiding this comment.
Set GPT-5 Databricks input limit to the real prompt cap
max_input_tokens is documented in this repo as an input-only limit, but these new Databricks GPT-5 entries set it to 400000 (the total context window) instead of the effective prompt cap used elsewhere for GPT-5-family models (272000). This overstates capacity by 128k tokens, so any caller that trusts model metadata can send prompts that pass local checks but are rejected upstream for token-limit overflow.
Useful? React with 👍 / 👎.
fix: add Databricks models databricks-gpt-5 +2 more
Closes #641
Source issue: #641
Summary
databricks-gpt-5databricks-gpt-5-1databricks-gpt-5-minidatabricks-gpt-5databricks-gpt-5-1databricks-gpt-5-mini2
Verified metadata
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.