Uh oh!
There was an error while loading. Please reload this page.
fix: add Google models deep-research-preview-04-2026 and deep-research-max-preview-04-2026 - #614
fix: add Google models deep-research-preview-04-2026 and deep-research-max-preview-04-2026#614github-actions[bot] wants to merge 1 commit into
Conversation
…h-max-preview-04-2026
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:df9c2b7a25
ℹ️ 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".
| ] | ||
| }, | ||
| "deep-research-preview-04-2026": { | ||
| "format": "google", |
There was a problem hiding this comment.
These new catalog entries classify both deep-research IDs as normal format: "google" chat models, which makes the proxy send them to /models/{model}:generateContent / :streamGenerateContent in handleGoogleRequest (packages/proxy/src/proxy.ts, lines 3398-3415). For these model IDs, Google expects the Interactions API, so requests will fail at runtime (streaming and non-streaming) as soon as users select these models from the catalog. Either add model-specific Interactions routing before listing them, or keep them out of the supported model list until that path exists.
Useful? React with 👍 / 👎.
fix: add Google models deep-research-preview-04-2026 and deep-research-max-preview-04-2026
Closes#589
Source issue: #589
Summary
deep-research-preview-04-2026deep-research-max-preview-04-2026deep-research-preview-04-2026deep-research-max-preview-04-20262
3
4
5
Verified metadata
Verification notes
Verification
Fields verified from official sources
deep-research-preview-04-2026,deep-research-max-preview-04-2026googlechattrue["google"]truetrueFields NOT published / omitted
max_input_tokensinputTokenLimitfor these agent models. Estimated usage (~900k for Max) implies ≥1M context window consistent with Gemini 2.5 family. Value 1048576 is inferred from Gemini 2.5 family, not a verified hard limit. Included in metadata to satisfy resolver requirements.max_output_tokensoutputTokenLimitfor these agent models. Estimated output ~60k (preview) and ~80k (max) includes reasoning tokens from agentic loops. Value 65535 is inferred from Gemini 2.5 family. Included in metadata to satisfy resolver requirements.input_cost_per_mil_tokensoutput_cost_per_mil_tokensinput_cache_read_cost_per_mil_tokenssupported_regionsparentreasoning_budgetdeprecation_datesync_models (LiteLLM) cross-check
Neither
deep-research-preview-04-2026nordeep-research-max-preview-04-2026exists in the LiteLLMmodel_prices_and_context_window_backup.jsoncatalog. No cross-check is possible. All proposed values are sourced from official Google documentation.Important note for PR reviewers
These models use the Interactions API (
/v1beta/interactions), not the standardgenerateContentendpoint used by otherformat: "google"models. The proxy may need specific handling for these models. Themax_input_tokensandmax_output_tokensvalues are inferred from the Gemini 2.5 family (not published explicitly for these models) and should be validated against the API'smodels.getresponse when possible.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.