fix: add xAI models grok-4.20-multi-agent-0309#606
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
requested review from
Alex Z (CLowbrow),
aswink,
Caitlin Pinn (cpinn),
Erin McNulty (erin2722) and
Ken Jiang (knjiang)
![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: 188c637c36
ℹ️ 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".
| "grok-4.20-multi-agent-0309": { | ||
| "format": "openai", | ||
| "flavor": "chat", | ||
| "input_cost_per_mil_tokens": 1.25, | ||
| "output_cost_per_mil_tokens": 2.5, | ||
| "max_input_tokens": 2000000, | ||
| "available_providers": [ |
There was a problem hiding this comment.
The newly added grok-4.20-multi-agent-0309 entry is missing key fields (reasoning, multimodal, input_cache_read_cost_per_mil_tokens, and max_output_tokens) that are present on the existing grok-4.20-multi-agent-beta-0309 variant in the same file. Because model_list.json is consumed as model capability/pricing metadata, this makes the canonical model appear less capable and less expensive than its equivalent alias, which can disable reasoning-related UX and produce incorrect cost estimates for cached-token usage.
Useful? React with 👍 / 👎.
1 participant
fix: add xAI models grok-4.20-multi-agent-0309
Closes #565
Source issue: #565
Summary
grok-4.20-multi-agent-0309grok-4.20-multi-agent-0309Verified 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.