I’m encountering what appears to be an account-specific eligibility issue with the official Antigravity CLI.
Environment
- Antigravity CLI: v1.1.4
- macOS (Apple Silicon)
Issue
I have three personal Google accounts, all with an active Google AI Pro subscription.
For all three accounts:
- Google AI Pro is active.
- Gemini works normally.
- Google AI Studio works normally.
- OAuth completes successfully.
However, Antigravity CLI consistently fails with:
Eligibility check failed:
Your current account is not eligible for Antigravity.
Verify your account to continue.
Alternatively, try signing in with another personal Google account.
The browser authentication flow succeeds and displays that authorization was successful. After returning to the CLI, the eligibility check fails immediately.
The CLI correctly recognizes the signed-in account before displaying the error. For example:
Antigravity CLI 1.1.4
<email@example.com>
Gemini 3.5 Flash (High)
Eligibility check failed:
Your current account is not eligible for Antigravity.
Troubleshooting performed
- Reinstalled the CLI.
- Logged out and back in multiple times.
- Cleared authentication.
- Verified Google AI Pro is active.
- Confirmed Gemini and AI Studio both work with the same accounts.
- Verified browser OAuth completes successfully every time.
I also inspected the IDE logs. They show successful requests to backend endpoints such as:
v1internal:loadCodeAssistv1internal:fetchAvailableModels
on daily-cloudcode-pa.googleapis.com, but the logs do not expose the backend eligibility response, so I couldn’t determine why the accounts are being rejected.
Expected behavior
Personal Google accounts with an active Google AI Pro subscription should be able to use Antigravity CLI, or the CLI should provide a more specific explanation of which eligibility requirement is not satisfied.
Actual behavior
OAuth succeeds, but the CLI immediately reports:
Eligibility check failed:
Your current account is not eligible for Antigravity.
If there’s an additional requirement beyond Google AI Pro, could you clarify what it is? Otherwise, this appears to be an issue with the account eligibility check.