fix(catalog): redirected Gemini 3.1 Pro high-effort traffic to gemini-pro-agent

- Updated the Gemini 3.1 Pro variant collapse so high effort now routes to `gemini-pro-agent` instead of `gemini-3.1-pro-high`.
- Kept `gemini-3.1-pro-high` in the collapse members list so the raw discovery ID remains handled.
- Lowered `contextWindow` from `163840` to `131072` tokens in `models.json`.
This commit is contained in:
can1357
2026-06-12 11:50:21 +02:00
parent ae84502b82
commit ed5eb70dda
2 changed files with 9 additions and 4 deletions
+1 -1
View File
@@ -54417,7 +54417,7 @@
"cacheRead": 0.135,
"cacheWrite": 0
},
"contextWindow": 163840,
"contextWindow": 131072,
"maxTokens": 16384,
"thinking": {
"mode": "effort",
+8 -3
View File
@@ -123,12 +123,17 @@ export const ANTIGRAVITY_VARIANT_COLLAPSE_TABLE: VariantCollapseTable = {
{
id: "gemini-3.1-pro",
name: "Gemini 3.1 Pro",
// `gemini-pro-agent` is consumed as a member but unused in routing.
members: ["gemini-3.1-pro-low", "gemini-3.1-pro-high", "gemini-pro-agent"],
// High routes to `gemini-pro-agent` — the upstream `gemini-3.1-pro-high`
// deployment returns INVALID_ARGUMENT on every streamGenerateContent
// request (both CCA endpoints) while discovery still lists it;
// `gemini-pro-agent` is the same model ("Gemini 3.1 Pro (High)", same
// thinking budget/caps) and accepts the identical request body.
// `gemini-3.1-pro-high` stays a member so the dead raw id is consumed.
members: ["gemini-3.1-pro-low", "gemini-pro-agent", "gemini-3.1-pro-high"],
routing: {
off: "gemini-3.1-pro-low",
[Effort.Low]: "gemini-3.1-pro-low",
[Effort.High]: "gemini-3.1-pro-high",
[Effort.High]: "gemini-pro-agent",
},
thinking: { mode: "google-level", efforts: GEMINI_3_PRO_FAMILY_EFFORTS },
suppressWhenOff: true,