# Google AI Pro shows Antigravity Starter Quota — auth clean, no eligibility error (Linux 2.12.2)

**URL:** <https://discuss.ai.google.dev/t/google-ai-pro-shows-antigravity-starter-quota-auth-clean-no-eligibility-error-linux-2-12-2/181090>\
**Category:** Google Antigravity\
**Tags:** bug\
**Created:** [September 7, 2026, 2:53am UTC](https://discuss.ai.google.dev/t/google-ai-pro-shows-antigravity-starter-quota-auth-clean-no-eligibility-error-linux-2-12-2/181090 "2026-09-07T02:53:43Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![juas](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/juas/32/147555_2.png) [@juas](https://discuss.ai.google.dev/u/juas)\
**Post date:** [September 7, 2026, 2:53am UTC](https://discuss.ai.google.dev/t/google-ai-pro-shows-antigravity-starter-quota-auth-clean-no-eligibility-error-linux-2-12-2/181090/1 "2026-09-07T02:53:43Z")

</div>

through a Google AI plan at this time."

Only a weekly limit, no 5-hour cycle — so the backend classifies the account as  
non-Pro, not just a UI mislabel.

Setup: Antigravity 2.12.2 (linux-x64 tar.gz), agy CLI 1.1.27, consumer Gmail,  
Croatia. App install ID 0e3de236-c027-4610-9c40-6eb207ae1a74.

First onboarding returned 403 PERMISSION\_DENIED / VALIDATION\_REQUIRED from  
[cloudcode-pa.googleapis.com](http://cloudcode-pa.googleapis.com). That cleared on its own. After a full token, cookie  
and session wipe plus fresh sign-in, the log is clean — no 403, no eligibility  
error, doRefreshQuota succeeds. The backend answers fine and still returns Starter.

Tried: re-auth on app and CLI, full credential wipe, confirmed tier/ownership/billing  
in Google One, confirmed signed-in address matches the subscription.

Anything resyncable account-side, or is this server-side?