Antigravity HTTP 400 "Invalid project resource name projects/"

Google Antigravity
1

Hi Antigravity team,

Persistent HTTP 400 “Invalid project resource name projects/” on every agent run, even after setting valid GCP Project ID.

Account: Personal Gmail, Google AI Pro
OS: Windows
Usage: Agent Manager for coding

Error details:
Trajectory ID: f5893009-cc45-43d1-ab23-e0c0240…
TraceID: 0xdef8b353e9e…

{
“error”: {
“code”: 400,
“message”: “Invalid project resource name projects/”,
“status”: “INVALID_ARGUMENT”
}
}

What I’ve done:

  • Enabled 2FA
  • Logged out/in with same Gmail
  • Set Cloud Project ID from AI Studio Settings (“alfa”)
  • Reinstalled Antigravity + configured Go/Python PATH
  • Relaunched terminal

Backend still sends projects/ with empty ID.

Request: Please reprovision/rebind my account to a valid project.

Happy to provide logs/screenshots.

screenshot
screenshot1370×715 58.4 KB

2

Hello @Marcos_Dias, welcome to AI Forum!

Thank you for bringing the issue to our attention. Our engineering team is currently investigating the matter, and we appreciate your patience as we work toward a resolution.

1 Like
3

Hi @Abhijit_Pramanik **

UPDATE - Followed community advice, still broken:**

New Trajectory ID: 403b7aa1-8c75-459e-
TraceID: 0xe362a18
Same “projects/” empty error.

Actions taken:

  • Removed alternate domain email from Google Account (personal-info)
  • Cleared %LOCALAPPDATA%\Google\Antigravity\Cache (both folders)
  • Fresh login with Gmail only + 2FA
  • Confirmed Project ID “alfa” in Settings

Community theory: bug triggered by old custom domain association confusing backend project binding.

Engineering team: can you confirm if this matches known issue? Need reprovisioning for this account.

4

I’m experiencing the same error here. The root cause appears to be that, while I’ve confirmed the local DB has the correct project ID and the OAuth token exists, the server-side binding is broken. The client sends the correct value, but Cloud AI Companion still receives an empty projects/ parameter. Since this is a Google bug, I cannot resolve it locally. Can the Antigravity team help?

The ‘Provide Feedback’ submit button inside Antigravity is disabled, so I cannot report this issue directly through the platform.

5

Hey @Abhijit_Pramanik,

I’m having the same issue and same error as of this morning. I’ve tried ALL the same steps to solve with no progress. Would really appreciate it if someone on the antigravity team could help me out. I am also on a personal Google One AI Pro subscription. I’m happy to share any error codes, logs or screenshots as necessary. But my side looks identical to the error @Marcos_Dias is/was facing.

6

When attempting to access Antigravity IDE with my Google account (grupofor*****@gmail.com), I receive the following message: “This service has been disabled in this account for violation of Terms of Service. Please submit an appeal to continue using this product.”

Prior to this suspension, I had already been experiencing a different technical issue with the same account: an HTTP 400 error (Invalid Project Resource Name) that prevented me from using Antigravity at all. I attempted to resolve that issue through the developer community.

In an attempt to work around the HTTP 400 error that was blocking my access to Antigravity, I installed the OpenCode application along with a third-party extension (sst-dev.opencode) inside Antigravity itself. Some of these tools allowed authentication via Google Pro account OAuth instead of an API Key. At the time, I believed this was a legitimate technical solution to the access problem I was experiencing.

I now understand that this approach violated Antigravity’s Terms of Service, specifically the clause prohibiting the use of third-party tools with personal/Pro account OAuth authentication. There was no intent to circumvent the rules — my motivation was purely technical, driven by a desire to be able to work normally on the platform.

As soon as I understood the cause of the suspension, I took the following corrective actions:

  • Complete removal of the sst-dev.opencode-0.0.13 extension from the Antigravity extensions folder;

  • Removal of the corresponding entry from Antigravity’s extensions.json file;

  • Uninstallation of OpenCode from the development environment;

  • Verification that no traces of the extension or third-party tool remain in the installation.

Request

I respectfully request the reinstatement of my access to Antigravity / Gemini Code Assist on my account (grupofor*****@gmail.com). I hereby confirm that:

  • All third-party tools have been fully removed from the installation;

  • I commit to using only official authentication methods (API Key) going forward;

  • I have read and accept the updated Antigravity Terms of Service;

  • I will not use any tool or extension that accesses Gemini/Antigravity resources via personal account OAuth.

Thank you for your time and consideration. I am available to provide any additional information needed for the review of this appeal.

Sincerely,

Marcos