Release notes

FEATURE

Antigravity quota card no longer gets stuck on a wrong percentage

When you check Antigravity quota in usage, its card should finally agree with the official CLI's /quota result. Since Antigravity CLI 1.1.5, the OAuth credential (proof that you authorized the sign-in) moved from an ordinary disk file into macOS Keychain, where Macs keep passwords and login data. Its quota backend—the server handling the lookup—also moved. The card kept reading the old token file; it could refresh that abandoned credential, but received numbers based on a stale grant, leaving the percentage stuck and wrong. It now checks the gemini / antigravity Keychain entry first, falls back to the legacy file only when needed, and calls the new backend. It is like a bank moving its ledger into a vault and changing counters while an old display board still copies figures from the closed counter; now it visits the vault and the right counter first.

Original changelog

Original changelogAntigravity quota card no longer gets stuck on a wrong percentage
**Antigravity quota showed a stuck, wrong percentage since the CLI's 1.1.5 update.** The Antigravity CLI moved its OAuth credential from a plain file on disk into the macOS Keychain (`security` service `gemini`, account `antigravity`, `go-keyring-base64:`-wrapped JSON) and switched its quota backend from `cloudcode-pa.googleapis.com` to `daily-cloudcode-pa.googleapis.com`. The card kept reading the now-abandoned token file, which silently refreshed against a stale grant and returned numbers that no longer matched the CLI's own `/quota` output. It now reads the Keychain entry first (falling back to the legacy file), and posts to the current backend.