Critical Bug: Persistent HTTP 400 "Invalid project resource name projects/" even after Gmail switch

I am a Google AI Pro subscriber and I’m stuck with the “Arrow 400” error. My TraceID is 0x494c0fc314fb783.

What I’ve already tried:

  • Switched account from iCloud to Gmail.

  • Manual deletion of .antigravity and %APPDATA%/Antigravity folders.

  • Set GOOGLE_CLOUD_PROJECT as a system environment variable.

  • Attempted antigravity auth login --force-project-sync.

Problem: The app continues to send requests to projects/ (empty name), resulting in a 400 error. The project selection UI is missing in my version of the app. Please fix the project auto-provisioning for my account.

5 Likes

i have the same issue, did you resolve it?

I’m experiencing the same issue with my Google AI Pro plan.

I have the same problem. Some people say it’s a regional issue:

I’m in Türkiye right now, is anyone else experiencing this problem in Türkiye?

Also, the Claude models are missing. It’s very strange because I haven’t used it for 2 days but it says my quota limit has been reached.

1 Like

I have the same problem since a few days. Already contacted antigravity-support@google.com. The live chat support confirms this has to be looked at by the backend team.

I tried:

  1. Logged out and back into the Pro account multiple times.

  2. Deleted local configuration directories: .gemini and .antigravity.

  3. Verified that a Free User account works on the same machine/network, confirming this is an account-level provisioning/entitlement issue.

  4. Tried logging out back from Gemini CLI and back in

  5. Log out of the Antigravity IDE and close the app, go to Google Account Connections > Delete all connections, and signing in again in IDE.

1 Like

on OSS GPT: “Failed to send” can you confirm?

2 Likes

All same here. Tried Gemini assist on VSCode and get error in agent mode

1 Like

Same here. Tried on another computer and I got the same issue there. So definitely an account issue.

tried to troubleshoot with claude, summary:

Subject: Bug: Language server cannot read OAuth token on Linux – Invalid project resource name projects/

Environment

  • OS: Ubuntu Linux (x86_64)
  • Antigravity version: 1.16.5-1770081357
  • Installation: via official apt repository (us-central1-apt.pkg.dev)

Problem
After successfully authenticating via the Antigravity OAuth login flow, the language server fails to read the OAuth token and cannot retrieve the GCP project ID. Every agent request results in:

INVALID_ARGUMENT (code 400): Invalid project resource name projects/

Root Cause (from logs)
Two separate authentication systems are not communicating:

  1. The Electron app successfully completes OAuth login (confirmed in auth.log: “OAuth token changed”)
  2. The language server (server.go) cannot find the token (Antigravity.log: “Failed to get OAuth token: key not found”)

The language server appears to be unable to read the OAuth token stored by the Electron app in Local Storage (leveldb).

Steps to reproduce

  1. Install Antigravity on Linux via the official apt repository
  2. Log in with a Google account via the in-app OAuth flow
  3. Send any message to the agent
  4. Observe HTTP 400 error: Invalid project resource name projects/

Additional context

  • The same Google account works without issues on Windows (no GCP project configuration required)
  • Installing gcloud CLI and configuring application default credentials does not resolve the issue
  • gnome-keyring / libsecret is not installed by default, which may be relevant
  • The Electron auth flow completes successfully but the token is not accessible to the language server process

Relevant log excerpt (Antigravity.log)
E server.go:558] Failed to get OAuth token: key not found
W client.go:137] failed to set auth token
E log.go:380] agent executor error: INVALID_ARGUMENT (code 400): Invalid project resource name projects/

The bug persists. This is the worst development team I’ve ever seen. Because of these kinds of problems, I can’t use the app for a few days every few weeks. Antigravity is a complete fiasco.

4 Likes

I’ve added Gemini Code Assist extension and the whole app is working now fine. Somehow this thing adds a working project name

same issue, long-time user, no changes

I am experiencing the exact same issue. It appears to be an account-level corruption regarding the default GCP Project binding.

Symptoms:

  • Error: HTTP 400 Bad Request with message "Invalid project resource name projects/" (Empty Project ID).

  • Scope: Happens in ANY workspace, even in a completely empty folder.

  • Account Specific: Switching to a different Google account works perfectly. My main account (Gemini Pro subscriber) is the only one affected.

  • Environment: Verified on multiple machines (Mac/Windows) and Incognito mode. The issue persists, indicating it’s a server-side account config issue, not a local cache issue.

What I have tried (Failed):

  1. Hard refresh / Clearing all cookies & local storage.

  2. Revoking “Google Cloud Code” and “Project IDX” access in Google Account Security settings to force re-auth.

  3. Manually setting GCP_PROJECT env vars in .idx/dev.nix.

  4. Deleting and reinstalling gcloud SDK locally (though this shouldn’t affect the cloud IDE).

Diagnostics:

  • Trajectory ID: 3aa507a7-f782-4ca8-b105-98c915957d40

  • TraceID: 0x746e0fa39655acc (Latest) / 0x341a5207e022c9d8 (Previous)

  • Timestamp: Fri, 13 Feb 2026 20:00:36 GMT

Please investigate the backend project provisioning for my account.

The same here …. the error is :
Trajectory ID: a16e4795-9f46-49d8-aaa1-d6879ffa51e1
Error: HTTP 400 Bad Request
Sherlog:
TraceID: 0xf6fd7e12907831ef
Headers: {“Alt-Svc”:[“h3=“:443”; ma=2592000,h3-29=“:443”; ma=2592000”],“Content-Length”:[“382”],“Content-Type”:[“text/event-stream”],“Date”:[“Sat, 14 Feb 2026 08:18:36 GMT”],“Server”:[“ESF”],“Server-Timing”:[“gfet4t7; dur=195”],“Vary”:[“Origin”,“X-Origin”,“Referer”],“X-Cloudaicompanion-Trace-Id”:[“f6fd7e12907831ef”],“X-Content-Type-Options”:[“nosniff”],“X-Frame-Options”:[“SAMEORIGIN”],“X-Xss-Protection”:[“0”]}

{
“error”: {
“code”: 400,
“details”: [
{
@type”: “type.googleapis.com/google.rpc.BadRequest”,
“fieldViolations”: [
{
“description”: “Invalid project resource name”,
“field”: “name”
}
]
}
],
“message”: “Invalid project resource name projects/”,
“status”: “INVALID_ARGUMENT”
}
}

I am encountering the same issue and receiving the same error message. Has anyone received a response from the Antigravity team?

Nope its been days… I already switch to Kilo Code atp…

Thank you for bringing this to our attention. We have escalated the issue to our internal teams for a thorough investigation.

To ensure our engineering team can investigate and resolve these issues effectively, we highly recommend filing bug reports directly through the Antigravity in-app feedback tool. You can do this by navigating to the top-right corner of the interface, clicking the Feedback icon, and selecting Report Issue.

3 Likes

Same issue here. Cancelled my Antigravity account.

I’ve been dealing with the same issue since yesterday and haven’t found a fix yet. Interestingly, everything works fine when I switch to a different account. The error only persists on my main account, which has the Google AI Pro subscription. Both religion is Turkey but one of them is working…

I’ve had this issue for 1 week now. I’ve tried everything. Appears to be account related. Possibly limited/throttled?

1 Like