The Antigravity gemini 3.7 (below) all variant high, med, low are all gone now, only that left is tiered

[WUIX69]

[diegosouzapw]

Thanks @WUIX69, the screenshot shows the cause. Your Antigravity connection's model list has gemini-3.7-flash-tiered and gemini-3.8-flash-tiered, and none of the -high / -medium / -low ids. Antigravity's upstream does that for 3.7 on purpose: the tiers are a single "tiered" model, and OmniRoute maps gemini-3.7-flash-high|medium|low onto it and steers the thinking budget separately. For 3.8 our code assumes the opposite, that the tiers are served directly, so it doesn't map them onto -tiered. If the upstream has moved 3.8 to the tiered shape too, as your list suggests, the 3.8 tiers are unreachable by their old names.

I haven't confirmed that against the live service yet, so treat it as the likely cause, not a proven one. It's tracked in #15659. Until then, you can select gemini-3.8-flash-tiered directly: it's in your list and should be callable by that id. If it isn't, tell me the error.

[WUIX69]

Before i used to use Gemini 3.7 <varaints> all variants because it was still available back then, but when Claude Opus 5.5 was drop on antigravity for Pro and above subscribed users and also the apo latest version notifies us that they will remove Gemini 3.7, 3.6, 3.5 sooner.. omniroute remove those variants only leaving the tiered for these gemini flash models.. I do already run the Import Upstream Models to get the latest updates/changes and models on this screenshot is what all of them now

[diegosouzapw]

Thanks @WUIX69, that detail changes my earlier explanation, so a correction. I said the upstream might have "moved" the 3.8 tiers behind a tiered model. Looking again at the code, the more specific cause is per-account provisioning: Google's backend only allows the -high/-medium/-low ids on accounts or projects it specifically provisioned for them, and every other account can only call the shared -tiered id. OmniRoute already handles that for 3.7 (it forces the 3.7 display ids onto -tiered, from #11824), but the 3.8 mapping assumes every account has the tier ids. Your list after Import Upstream Models shows only the tiered rows, which fits an account without that provisioning. I've put the correction on #15659.

So the 3.7 tier names you used before disappearing is on the data side: your account's upstream list doesn't have them, and the import reflects what it returns. I can't see why the 3.7 tiers were available earlier and aren't now. What I can say is that gemini-3.8-flash-tiered should be the id to use, and I haven't confirmed it against a live account yet. If you try antigravity/gemini-3.8-flash-tiered and it fails or answers differently, tell me the error.

[WUIX69]

using -tiered on any gemini flash models works as expected, waiting for the hotfix to use the other variants

[diegosouzapw]

Thanks @WUIX69. That confirms gemini-3.8-flash-tiered works on your account, which is useful: it's the first live confirmation of the id I suggested. On the other variants, I should be plain: #15659 has no pull request yet, and the fix still needs a live check, so I can't give you a hotfix date. Using -tiered for Flash is the way to go until then.