Hello,
My personal Gmail account has a Google AI Pro subscription and previously worked in Antigravity IDE. It now receives this error:
“Your account is not eligible for Gemini Code Assist for individuals at this time.”
What I have verified:
-
The affected account successfully signs in to the standalone Antigravity application.
-
Another Google account signs in successfully to Antigravity IDE on the same Mac.
-
The browser reports successful authentication, but the IDE then rejects the affected account.
-
I completed the requested Google account verification.
-
Clearing application caches and signing in again did not resolve the issue.
Environment:
Could you investigate the IDE eligibility/entitlement check for my account and advise how to restore access? I can provide account details through a private support channel.
Thank you.
I also started facing this issue when I tried to login today
Same issue here.
Environment: Windows 11, Antigravity IDE 2
Account: personal @gmail.com with active Google AI Pro
Works: signs in to standalone Antigravity 2.0 with the same account
Fails: Antigravity IDE shows the error below after browser auth succeeds
Started on: 28-09-2026
Tried: sign out/in, renamed the “Antigravity IDE” AppData folder
Hi @Agosh_Forever, @Waqar_Ahmad and @Gautam_Parmar,
Your accounts work perfectly in the standalone Antigravity app but fail in the Antigravity IDE, this strongly indicates that the IDE’s internal authentication state (specifically globalStorage or state.vscdb) has become out of sync with your actual Google AI Pro entitlements.
Even if you clear standard application caches, the IDE can sometimes hold onto a stale eligibility flag. To force a deep reset of the IDE’s auth state and the underlying credential store, please try the following exact sequence:
- Open the Antigravity IDE and open the Command Palette (
Cmd+Shift+P on Mac, Ctrl+Shift+P on Windows).
- Type and run the command:
Antigravity: Reset Onboarding.
- Completely close/quit the Antigravity IDE.
- Open your standard terminal (or command prompt) and run the following command to wipe the underlying CLI credential store:
agy logout
- Then, log back in via the terminal:
agy login
- Finally, reopen the Antigravity IDE and proceed through the sign-in prompt.
This forces the IDE to pull a completely fresh entitlement check from the backend rather than relying on its cached state. Please let me know if this fixes the issue for you!