Message: "Invalid project resource name projects/" status: INVALID_ARGUMENT

I’m seeing a persistent Antigravity Agent failure on Windows where every Agent run terminates immediately with:

Error: Agent execution terminated due to error
HTTP 400 Bad Request
message: “Invalid project resource name projects/”
status: INVALID_ARGUMENT

Debug details from Antigravity:

Trajectory ID: cd7150a4-bffc-4ae0-8de3-01dd031db56b
TraceID: 0xeb6570940ec05771
Header includes: X-Cloudaicompanion-Trace-Id
Server: ESF
Content-Type: text/event-stream

The failing request appears to be sent with:
projects/

instead of:
projects/involuted-forge-357013

My Google Cloud project is valid and active:

Project ID: involuted-forge-357013

What I have already verified:

  • gcloud auth login completed

  • gcloud auth application-default login completed

  • gcloud auth application-default set-quota-project involuted-forge-357013

  • GOOGLE_CLOUD_PROJECT env var set and visible inside Antigravity terminal

  • GOOGLE_APPLICATION_CREDENTIALS set to ADC json path

  • Confirmed env vars echo correctly in IDE terminal

  • Restarted Antigravity after each change

I also fully reset Antigravity locally:

  • Deleted/renamed:

    • C:\Users\Chris.antigravity

    • AppData\Roaming\Antigravity

    • AppData\Local\Antigravity

  • Signed out and back in

  • Tried different Google account

  • Reinstalled Antigravity

  • Created new workspace

  • Tried multiple models (Gemini, Claude, GPT-OSS)

Behavior is identical across all models.

Local Antigravity logs are mostly 0 KB for the failing session, which suggests the failure happens in the companion/agent backend layer before local execution logging.

This looks like the companion service is not binding the project ID and is constructing requests with an empty project string.

Can someone confirm:

  1. Whether this is a known regression in the Antigravity Agent / Cloud AI Companion service?

  2. Whether project binding is expected to come from gcloud/ADC or from Antigravity account session?

  3. Any manual override config file or flag to force project ID?

Happy to provide more logs if you tell me exactly which file to capture.

Environment:

  • Windows 11

  • Latest Antigravity build (as of today)

  • Google Cloud project with billing enabled

3 Likes

Hey, I’ve the same issue.
Did you found a way to fix it for your workspace account?


After working correctly for a few days, the same problem occurred here.

The same troubleshooting procedure was followed, without success.

Report Issue.

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.

2 Likes

I tried all sorts of fixes without success, until I read this link: Critical Bug: Persistent HTTP 400 "Invalid project resource name projects/" even after Gmail switch - #27 by mattorq