Same issue here — Google AI Ultra subscriber on macOS. Triggered by a Google account email rename.
I have a unique data point that may help debug this.
I recently used Google’s new feature to rename my Google account email (from a Workspace email to Gmail). After the rename, the Antigravity agent chat broke with the exact same error:
"message": "Invalid project resource name projects/",
"status": "INVALID_ARGUMENT"
What I’ve confirmed:
-
Gemini CLI works perfectly with the same account — it picks up the project via
gcloudconfig -
gcloud authworks fine; the account is properly authenticated as the new email -
I created a new GCP project, enabled
cloudaicompanion.googleapis.com, and set it in bothgeminicodeassist.projectandgclouddefault — Antigravity ignores all of it -
Full nuclear reset: deleted
~/.antigravity,~/Library/Application Support/Antigravity, and all~/.geminiauth files. Reinstalled fresh, signed in again — same error -
Set
GOOGLE_CLOUD_PROJECTvialaunchctl setenv— no effect -
Installed the Gemini Code Assist extension (as suggested by @Aleksandr_Kalashniko) — no effect for me
Root cause theory:
Antigravity’s language server resolves the GCP project from Google’s backend API (not from local config or gcloud). After my account email rename, the server-side project binding is broken — the old project was provisioned for the old email identity, and auto-provisioning never created a new binding for the renamed account.
Gemini CLI bypasses this because it reads the project from gcloud config instead.
Trace IDs for investigation:
-
0xf1e8295488e44b8b
-
0x4605b6f617d6e9c
-
0xdabc3f77bf9f5467
This looks like a server-side provisioning bug. The account works everywhere else (Gemini CLI, gcloud, GCP Console). Only Antigravity’s agent backend returns an empty project.
Can someone from the Google team please look into re-provisioning the project binding for renamed accounts?
Environment: Antigravity latest (fresh install), macOS arm64, Google AI Ultra plan.