Confused About the Differences in how credits work Between , Antigravity CLI, and Google AI Studio

[mikmaneggahommie]

I am so confused why there are three tabs for google , not only that but the models listed in them , some have lot of models some very little , and how does credits work like do all three run out of credit at the same time or they are split individually ,

on top of that when listing antigravity remaining tokens , it lists outdated tokens ,no mention of 3.5 flash , on top of that i am having a very hard time adding all the models i can get inside of the actuall antigravity ide , which were 3.5 flash , high ,medium and low , but inside omniroute , this model flat out crash ,antigravity/gemini-3.5-flash-preview , making the antigravity tab usuless since it doesn't contain the claude opus... and it is only hosting very old models like 2.5 ,

And moving on to antigravity cli tab , choosing models like agy/gemini-3.1-pro-high , just displays, [400]: {"id":"chatcmpl-1780610286473-337b1906","object":"chat.completion","created":1780610286,"model":"gemini-3.1-pro-high","choices":[{"index":0,"message":{"role":"assistant","content":""},"finish_reason":"stop"}]} and like it also missing lot of models that u can get inside the actuall antigravity IDE.

then there is the Gemini Google AI Studio tab that too is very confusing lets say i use gemini/gemini-3.1-pro-preview inside claude code it litrally dosn't work and just gives me this response , API Error: Request rejected (429) · All credentials for model gemini-3.1-pro-preview are cooling down on and on , and no 3.5 flash.. in that tab so the only good model is 3.1 pro and that doesn't work either hence making the tab useless , when at-lest the two antigravity and cli could be consolidated as one tab to make it more intuitive , right now im soo confused and on top of that have very little success rate with the old version models

Would love if you address my concerns

![Uploading Screen Shot 2026-06-05 at 1.08.45 AM.png…]()

[diegosouzapw]

Hey @mikmaneggahommie -- this is a lot of genuinely confusing surface area, so let me lay out the whole Google picture and then hit each error. All verified against the v3.8.9 code.

Why there are three "Google" tabs

They're three different backends, not three views of one account:

Tab	Provider	Auth	Backend	Claude?	gemini-3.5-flash?
Antigravity	antigravity	OAuth	Antigravity IDE (daily-cloudcode-pa)	No (removed in Antigravity 2.0)	Yes (gemini-3.5-flash-preview)
Antigravity CLI	agy	OAuth	same IDE backend, imported separately	Yes (claude-opus-4-6-thinking, claude-sonnet-4-6)	partial (gemini-3.5-flash-low/extra-low)
Gemini (Google AI Studio)	gemini	API key	generativelanguage.googleapis.com	No	No

The two things that should un-confuse you immediately:

• Claude Opus is in the "Antigravity CLI" (agy) tab, not the "Antigravity" tab. Google removed Claude from Antigravity 2.0 (May 2026), so OmniRoute's antigravity provider dropped them too (antigravityModelAliases.ts:110). The agy tab is the one that mirrors the full Antigravity-IDE model set, Claude included.
• gemini-3.5-flash lives in the "Antigravity" tab (gemini-3.5-flash-preview). It is not a Google-AI-Studio model, which is why it's absent from the Gemini tab.

Credits

They don't share one OmniRoute counter. antigravity and agy use the same Google OAuth app but are separate connections you import independently (separate tokens/pools); the Google-AI-Studio gemini tab is a separate API key with its own Google quota. Whether your Google account shares quota across them is on Google's side, not OmniRoute's.

Your specific errors

1. antigravity/gemini-3.5-flash-preview "crashes" -- the model ID maps fine; the likeliest cause is a missing projectId on that Antigravity account (it returns a 422 oauth_missing_project_id from the Cloud Code endpoint, antigravity.ts:566-615). Re-auth the Antigravity connection so the projectId populates. It doesn't help that this error currently surfaces as an empty completion instead of a clear message -- that masking is part of the bug I'm filing below. If re-auth doesn't fix it, paste the exact error body and I'll trace it.
2. agy/gemini-3.1-pro-high -> [400] empty envelope -- confirmed bug. gemini-3.1-pro-high/-low are speculative tier-suffix IDs left in the agy catalog (agyModels.ts:39,48) with no upstream mapping -- that suffix convention 404s upstream (antigravityModelAliases.ts:101), and the 400 then gets masked as that empty chat.completion. Workaround now: use a plain agy model -- agy/gemini-3-flash, agy/gemini-2.5-pro, or agy/claude-opus-4-6-thinking. Fix tracked in [BUG] agy/gemini-3.1-pro-high & -low return 400 (speculative tier-suffix, unaliased) masked as empty chat.completion #3229.
3. gemini/gemini-3.1-pro-preview -> [429] cooling down -- that's Google's real rate limit on your API key for that model, not an OmniRoute bug. OmniRoute locks just that one model out briefly (per-model cooldown; self-heals after the window). If it's constant, you're hitting Google AI Studio's per-model quota on a single key -- add another key or wait. Separately, the Gemini tab's model list is stale (only 2.0/1.5; missing the 3.x IDs Google actually serves), which is why you see "no 3.5 flash / only 3.1 pro" -- refreshing it is tracked in [feature] Gemini (Google AI Studio) model list is stale — add Gemini 3.x (only 2.0/1.5 listed) #3231.

The real issues this surfaced (filing now)

• [BUG] agy/gemini-3.1-pro-high & -low return 400 (speculative tier-suffix, unaliased) masked as empty chat.completion #3229 -- agy gemini-3.1-pro-high/-low 400 (alias to plain gemini-3.1-pro or drop them) + stop masking 4xx as empty completions.
• [BUG] Antigravity CLI (agy) usage/quota not implemented — getUsageForProvider missing case "agy" #3230 -- the "Antigravity CLI" remaining-tokens never works (getUsageForProvider has no agy case, usage.ts:1513 -> "Usage API not implemented for agy"). That's why the quota looks outdated/empty on that tab.
• [feature] Gemini (Google AI Studio) model list is stale — add Gemini 3.x (only 2.0/1.5 listed) #3231 -- refresh the Google-AI-Studio (gemini) model list to include Gemini 3.x.

On consolidating the two Antigravity tabs: I hear you. They're separate because they're separate account imports with different model sets (CLI has Claude; the IDE provider has the image / computer-use models), but the overlap is real and the broken agy quota makes it worse -- I'll keep the UX request on file.

tl;dr right now: Claude -> agy tab; gemini-3.5-flash -> antigravity tab (re-auth for projectId); avoid agy/*-high and agy/*-low until #3229 lands. Thanks for the detailed write-up -- it surfaced two genuine bugs.

[mikmaneggahommie]

@diegosouzapw thanks so much for that thorough response! It cleared everything up for me, and I hope others find their answers from it too. Thanks again!

[diegosouzapw]

Glad it cleared things up, @mikmaneggahommie! Quick recap for anyone landing here later: Claude lives in the "Antigravity CLI" (agy) tab, gemini-3.5-flash lives in the "Antigravity" tab, and "Gemini (Google AI Studio)" is a separate API-key provider -- the three don't share a credit counter. The two agy bugs this thread surfaced (the gemini-3.1-pro-high/-low 400 and the missing agy usage view) are tracked in #3229 and #3230 and I'll fix them. Thanks again for the detailed write-up!

[mikmaneggahommie]

just confirmed claude can also live inside the anitgravity Oauth, i have listed the missing models and UX suggestion on ,#3184 (comment)

[diegosouzapw]

Thanks for doing the legwork of testing each ID, @mikmaneggahommie -- and I owe you a correction. Earlier in this thread I said Claude was removed from the Antigravity backend and only lived in the "Antigravity CLI" (agy) tab. Your test shows that's wrong: the Antigravity OAuth provider does serve antigravity/claude-opus-4-6-thinking and antigravity/claude-sonnet-4-6 (same backend as agy) -- they were just missing from OmniRoute's antigravity catalog, which carried a stale "Claude removed in Antigravity 2.0" assumption your empirical test disproves.

Fixed in #3303 (against issue #3184): I added claude-opus-4-6-thinking, claude-sonnet-4-6, gemini-3.1-pro-high, gemini-3.1-pro-low, gemini-3.5-flash-low and gemini-3.5-flash-extra-low to the antigravity catalog (matching the agy set, since it's the same backend), and corrected the wrong comment + the tests that encoded it.

One thing I did not do yet: remove gemini-3.5-flash-preview / gemini-3-pro-preview. Their failure for you looks like the missing-projectId 422 (re-auth the Antigravity connection so the projectId populates), not the model being gone -- so removing them would break accounts that have projectId set. The "consolidate the two Antigravity tabs into one" UX request is a fair point and I'm tracking it as a separate follow-up. Thanks again -- your testing made this a clean fix.

[mikmaneggahommie]

Thanks for your top-tier maintenance! Glad to help.

[diegosouzapw]

Closing this thread as stale due to inactivity.

No maintainer follow-up happened after the last maintainer message for over 15 days. If this is still relevant, feel free to open a new discussion with fresh logs/steps and I’ll pick it up with updated context.

[diegosouzapw]

Closing this thread as stale due to inactivity.

No maintainer follow-up happened after the last maintainer message for over 15 days. If this is still relevant, feel free to open a new discussion with updated logs/steps and I’ll pick it up with fresh context.