Repository navigation
Antigravity usage always reports "Usage unavailable" #19561
Description
The Antigravity provider derives its usage from the Gemini Code Assist quota. For an individual Google account loadCodeAssist now answers:
"reasonCode": "UNSUPPORTED_CLIENT",
"reasonMessage": "This client is no longer supported for Gemini Code Assist for individuals. To continue using Gemini, please migrate to the Antigravity suite of products"
So the Gemini read fails, and the mirror has nothing to publish — the status bar shows "Usage unavailable" permanently, even on a paid Google AI Pro plan with quota left.
Antigravity keeps its own quota behind RetrieveUserQuotaSummary (5-hour and weekly buckets, per model pool), which is where it should be read from.
Activity
suyash-ls commentedon Sep 8, 2026
I'm seeing the same issue.
chzisnull commentedon Sep 10, 2026
I'm seeing the same issue.
chzisnull commentedon Sep 10, 2026
When can it be repaired @nwparker @orca-ide
orca-ide commentedon Sep 10, 2026
nwparker commentedon Sep 19, 2026
I took over the native quota implementation in draft #21654, preserving credit for #20797 and adding the pre-invocation version guard requested in its review. Agy 1.1.10, the 1.1.11 prerelease, and unknown version output never receive
/usage; supported versions are checked on each refresh.ELI5: Orca asks Antigravity for its own quota numbers instead of copying Gemini's meter. No returned numbers means “usage unavailable,” not “0% used.”
Verified the guarded production fetcher and actual Refresh → Antigravity usage panel against installed agy 1.2.7 on macOS. This machine returns empty quota groups. The PR includes that live screenshot and a separately labeled populated renderer fixture. 201 focused tests, full typecheck, and changed-code quality pass. Live populated OAuth quota, Windows/WSL/SSH, and paired-runtime behavior remain unverified; no auth changes or repeated old-version inference probe were made. The account login/card work remains open.
nwparker commentedon Sep 19, 2026
Draft #21678 fixes another migration gap on top of #21654: quota refresh now uses the configured Antigravity executable instead of silently looking for a different
agyon PATH.Verified with installed agy 1.2.7 through a wrapper at a path with spaces, both directly and through the rebuilt hidden Orca app. The wrapper received the version check and
/usage; the actual CLI returned empty quota groups, correctly shown as unavailable. No populated OAuth quota or successful generation claimed.Argument-bearing launch commands get an explicit explanation rather than being executed as quota commands or replaced with another installation. Changing the command also discards quota from the previous executable. The draft includes live before/after screenshots and passing tests/typecheck. Keeping the broader quota/account issues open; CI is pending.
nwparker commentedon Sep 27, 2026
Closing as fixed by #21654 and #21678. Antigravity usage now comes from its native quota endpoint and refreshes through the configured executable; the merged PR verification reports populated quota buckets.