Antigravity broken: getting only "Agent execution terminated due to error."

[dewolf]

Does anyone have a fix for this? I have an Ultra account, but Antigravity is almost impossible to use on Mac.

[Jan_Razny]

Only “fix” is switching to Gemini. But it seems now Gemini Pro is no longer being routed to Gemini Flash, so it might handle some tasks (it is no Opus tho).

They seem to be trying to quantize all Claude models and failing at it.
Or just forcing people to use Gemini 3 Pro despite it not delivering on its promises.

[dewolf]

I have noticed the same behavior with Gemini as well.
Even after the latest update last night, I am experiencing the same issue.
Is anyone else encountering this problem? (macOS, Ultra account)

[Curtis_Hoareau]

ok there have been two updates since 1.14.2 that have moved the goal posts a little, however this agent exectuion error is still hiding whats going wrong for me. 1.15.6 brough about

Excertp one ; “2026-01-25 09:18:27.218 [info] (Antigravity) 2026-01-25 09:18:27.217 [INFO]: LS lspClient started successfully

2026-01-25 09:22:35.300 [info] E0125 09:22:35.300046 10456 log.go:354] encountered conflicting override on experiment: cascade-knowledge-config

2026-01-25 09:22:35.430 [info] I0125 09:22:35.429799 10456 planner_generator.go:275] Requesting planner with 7 chat messages at model retry attempt 1 and API retry attempt 1

2026-01-25 09:22:36.522 [info] E0125 09:22:36.521753 10456 log.go:362] agent executor error: PERMISSION_DENIED (code 403): You are currently configured to use a Google Cloud Project but lack a Gemini Code Assist license. Please contact your administrator to request a license. (#3501): PERMISSION_DENIED (code 403): You are currently configured to use a Google Cloud Project but lack a Gemini Code Assist license. Please contact your administrator to request a license. (#3501)“

and this is still present on 1.15.8

Ive been doing some more digging, here is what me and the cli have come up with;
The most critical step to resolve the PERMISSION_DENIED (403) error is to link an active billing account to your project antigravity-fix-project . This is a common prerequisite for using many Google Cloud APIs, even for free-tier services, however “Google Antigravity” positions itself as being free to use and not need a billing account.
```

• The Catch-22: The primary account is trapped in a loop where its history demands a billing-enabled project, which the user is unwilling/unable to provide for free-tier usage, leading to the persistent error.

for any of you who think clearing your cache is a good idea, it isnt I would like you to chime in if you resonate with the problems ive encountered os the steps taken below.

Report: Google Antigravity - PERMISSION_DENIED (403) Error Troubleshooting

1. Problem Description

When attempting to use Google Antigravity (an AI-powered development environment) with Gemini models, the application’s agent executor consistently fails with the following error:

PERMISSION_DENIED (code 403): You are currently configured to use a Google Cloud Project but lack a Gemini Code Assist license. Please contact your administrator to request a license.

This occurs despite the user’s local Antigravity configuration explicitly pointing to a personal Google account ([YOUR_GMAIL_ACCOUNT]). The desired functionality is to utilize the free tier of Gemini models.

2. Technical Context

• Application: Google Antigravity (AI-powered development environment).
• Core Functionality Affected: Access to Gemini models for AI-driven tasks.
• User Account Type: Personal Google account ([YOUR_GMAIL_ACCOUNT]).
• Error Code: HTTP 403 Forbidden - PERMISSION_DENIED.
• Suspected Cause (Initial): Identity conflict between personal account and inferred enterprise context, or misconfiguration.

3. Troubleshooting Performed

A systematic troubleshooting process was conducted, investigating various potential causes on the user’s local machine and Google Cloud Project configuration:

• Initial Log Analysis (ohcrap1.txt): The following key errors and warnings were observed during Antigravity startup attempts:

  2026-01-25 06:36:28.632 [info] E0125 06:36:28.631754 12248 log.go:354] encountered conflicting override on experiment: cascade-knowledge-config
  2026-01-25 06:36:29.742 [info] E0125 06:36:29.740961 12248 log.go:362] agent executor error: PERMISSION_DENIED (code 403): You are currently configured to use a Google Cloud Project but lack a Gemini Code Assist license. (#3501): PERMISSION_DENIED (code 403): You are currently configured to use a Google Cloud Project but lack a Gemini Code Assist license. (#3501)
  2026-01-25 06:37:47.158 [info] W0125 06:37:47.157616 10652 client.go:137] failed to set auth token
  2026-01-25 06:37:47.161 [info] W0125 06:37:47.159632 10652 log_context.go:106] Cache(userInfo): Singleflight refresh failed: You are not logged into Antigravity.
  2026-01-25 06:37:47.349 [info] 2026/01/25 06:37:47 http: TLS handshake error from 127.0.0.1:8562: read tcp 127.0.0.1:8545->127.0.0.1:8562: wsarecv: An established connection was aborted by the software in your host machine.
  

• Local Configuration Files: Inspected Antigravity’s and Gemini CLI’s configuration files (e.g., google_accounts.json, settings.json, mcp_config.json, argv.json). All indicated a personal account setup and no conflicting project IDs or enterprise settings.

• Environment Variables: Checked for Google Cloud-specific environment variables (GOOGLE_CLOUD_PROJECT, GOOGLE_CLOUD_LOCATION, GOOGLE_APPLICATION_CREDENTIALS). None were found to be set.

• Local Application Cache: Antigravity’s application data cache (%APPDATA%\Antigravity) was cleared and reset. The error persisted, indicating no corrupted local state.

• Formal Cloud Identity Check: Attempted to log in to admin.google.com with the personal account. This confirmed the account is NOT formally managed by an enterprise Google Cloud Identity (i.e., the user is not an “admin” of a formal Cloud Identity/Workspace organization).

• Explicit Google Cloud Project Configuration (Attempted): A new, free-tier Google Cloud Project ([YOUR_PROJECT_ID]) was created, and the “Gemini for Google Cloud API” was enabled for it. An attempt was made to explicitly configure Antigravity’s settings.json with this project ID. This led to a language server timeout, and the change was reverted, indicating a deeper issue (later identified).

• Diagnostic Test with Alternate Google Account:

  • Action: Logged into Antigravity with a different personal Google account that has no prior developer history (i.e., no past Google Cloud Project creation, API enablement).
  • Result: Antigravity functions perfectly with Gemini services using this alternate, clean account.

4. Root Cause Confirmed: Account History Propagation and Context Collision (“Catch-22”)

The diagnostic test with the alternate account definitively confirms that the “developer history” associated with the user’s primary Google account ([YOUR_GMAIL_ACCOUNT]) is the root cause. This history causes Google’s backend to propagate an implicit “developer” or enterprise context, overriding local settings and free-tier intent, leading to a critical context collision.

• The Collision: When Antigravity tries to authenticate, a collision occurs where the backend system cannot reconcile the free-tier personal intent (from local settings) with the propagated “developer” status from the account’s history. This causes a conflict where the system expects a fully managed Google Cloud environment.

• Backend Misinterpretation: Despite local configuration and intent for free-tier personal use, the backend interprets requests from [YOUR_GMAIL_ACCOUNT] as originating from a context that requires a fully configured Google Cloud Project with billing.

• Clarification on “Admin” Status: The user is not a formal administrator of a Google Cloud organization. The problem stems from their account’s developer history creating a backend “profile” that infers a Google Cloud Project context, even without formal administrative status.

• Billing Requirement: The Google Cloud Assistant confirmed that the PERMISSION_DENIED (403) error (citing a missing “Gemini Code Assist license”) is actually due to the absence of an attached and enabled billing account on the Google Cloud Project ([YOUR_PROJECT_ID]), which is a mandatory prerequisite for most Google Cloud services, even for free-tier usage, to track resource consumption, prevent abuse, and apply free credits.

• Google Cloud Assistant Full Q&A (ohcrap2.txt):

  **Prompt provided to assistant:**
  Assume the role of a Google Cloud expert specializing in IAM and API configurations. I need to ensure my project `antigravity-fix-project` is correctly configured to allow an external application (Google Antigravity) to use Gemini models via my personal account `[YOUR_GMAIL_ACCOUNT]` on the free tier.
  
  The external application is failing with a `PERMISSION_DENIED (403)` error, stating I lack a 'Gemini Code Assist license', even though I expect to use the free tier.
  
  Please verify the following for project `antigravity-fix-project` and provide a detailed, step-by-step analysis and confirmation for each point:
  
  1.  Is the 'Gemini for Google Cloud API' (`cloudaicompanion.googleapis.com`) fully enabled and ready for use?
  2.  Are there any other essential APIs required for basic Gemini access that might be missing (e.g., Vertex AI API)?
  3.  Does my personal user account `[YOUR_GMAIL_ACCOUNT]` have the necessary IAM roles on this project to use the Gemini API? Specifically, confirm that I have `roles/cloudaicompanion.use and `roles/serviceusage.serviceUsageConsumer`. If not, provide the `gcloud` commands to add them.
  4.  Is there a billing account attached to this project? If not, is a billing account required to make free-tier Gemini API calls?
  5.  Is there any other project-level configuration, setting, or lien that could cause a personal account to be incorrectly processed as needing an enterprise license for this API?
  
  **Assistant's Response:**
  Here is a detailed analysis of your project's configuration for the Gemini for Google Cloud API:
  
  1. Gemini for Google Cloud API Enablement
  The 'Gemini for Google Cloud API' ( cloudaicompanion.googleapis.com ) is fully ENABLED for your project antigravity-fix-project . This was confirmed by the serviceusage.googleapis.com API call.
  
  2. Other Essential APIs for Basic Gemini Access
  Based on the list of enabled services from the serviceusage.googleapis.com API call, the Vertex AI API ( aiplatform.googleapis.com ) is not explicitly listed as enabled. While the Gemini for Google Cloud API is enabled, some advanced Gemini features or integrations might rely on the Vertex AI API.
  
  To ensure full functionality, you might consider enabling the Vertex AI API. You can do this using the following gcloud command:
  
  gcloud services enable aiplatform.googleapis.com --project=antigravity-fix-project
  Generated code may be subject to license restrictions not shown here. Use code with care. Learn more 
  
  3. IAM Roles for [YOUR_GMAIL_ACCOUNT]
  Your personal user account [YOUR_GMAIL_ACCOUNT] does not currently have the roles/cloudaicompanion.use or roles/serviceusage.serviceUsageConsumer roles directly assigned to it on project antigravity-fix-project .
  
  The IAM policy retrieved from cloudresourcemanager.googleapis.com shows that curtis.hoareau@gmail.com (note: the email in the memory is gmail.com not googlemail.com ) has the roles/owner role. The Owner role ( roles/owner ) is a primitive role that includes all permissions for all resources, including the permissions granted by roles/cloudaicompanion.use and roles/serviceusage.serviceUsageConsumer . Therefore, you should have sufficient permissions through your Owner role.
  
  If you still wish to explicitly add these roles, you can use the following gcloud commands:
  
  gcloud projects add-iam-policy-binding antigravity-fix-project \
      --member="user:[YOUR_GMAIL_ACCOUNT]" \
      --role="roles/cloudaicompanion.use"
  
  gcloud projects add-iam-policy-binding antigravity-fix-project \
      --member="user:[YOUR_GMAIL_ACCOUNT]" \
      --role="roles/serviceusage.serviceUsageConsumer"
  Generated code may be subject to license restrictions not shown here. Use code with care. Learn more 
  
  4. Billing Account Status
  There is no billing account attached to project antigravity-fix-project . This was confirmed by the cloudbilling.googleapis.com API call, which showed billingEnabled: false and an empty billingAccountName .
  
  A billing account is generally required for most Google Cloud services, even for free-tier usage, to track resource consumption and apply any free-tier credits. While some APIs might have a limited free quota that doesn't immediately require billing, the PERMISSION_DENIED (403) error indicating a missing "Gemini Code Assist license" could be indirectly related to the absence of an active billing account, as free-tier access often still necessitates a billing setup for identification and quota management.
  
  5. Other Project-Level Configurations, Settings, or Liens
  Based on the cloudresourcemanager.googleapis.com API call, the project antigravity-fix-project is in an ACTIVE lifecycle state. No project liens were found (the API call to list liens resulted in a 404, which typically means no liens exist or the API is not enabled/accessible for this specific resource type, but it doesn't indicate an active lien).
  
  Recommendation: The most critical step to resolve the PERMISSION_DENIED (403) error is to link an active billing account to your project antigravity-fix-project . This is a common prerequisite for using many Google Cloud APIs, even for free-tier services, however "Google Antigravity" positions itself as being free to use and not need a billing account.
  

• The Catch-22: The primary account is trapped in a loop where its history demands a billing-enabled project, which the user is unwilling/unable to provide for free-tier usage, leading to the persistent error.

5. Resolution Options

Given that the developer history of the primary account is the core issue and cannot be easily reset or overridden:

1. Recommended: Use an Alternate Google Account for Antigravity.

   • Pros: This is the most direct and functional solution, proven by the diagnostic test. It completely bypasses the problematic history of the primary account.
   • Cons: Requires the user to manage two Google accounts if they wish to keep their primary for other uses.

2. If Primary Account is Mandatory (and Billing is Acceptable): Attach Billing.

   • Pros: Allows the primary account to use Antigravity’s Gemini features.
   • Cons: Requires attaching a credit/debit card, which the user was previously hesitant to do. While free-tier limits apply, the setup requires financial information. This does not address the underlying propagation issue, but rather satisfies the backend’s demand.

3. Advanced / Less Likely: Contact Google Support.

   • Pros: Might lead to a specific override or “cleaning” of the primary account’s backend profile for Antigravity.
   • Cons: Can be a lengthy process with uncertain outcomes, and might not be supported for free-tier users.

---

Generated by Gemini CLI Agent as part of a troubleshooting session.

[Ripal_Godhani]

This issue has become completely critical.
The agent crashes every 1 minute when running, making the IDE effectively unusable.

I have already tried all standard troubleshooting steps:

Disabled every “MCP “(100% clean setup).
Started multiple fresh sessions.
Restarted the IDE entirely.

Nothing works.

The agent continues to terminate due to an error every single minute.

At this point, I hesitate to even call Antigravity an IDE — basic functionality is broken.
This is not a configuration issue on my side.

why does even solution in Doc says disable MCP servers - really in 2026?

[Martin_Gros]

Impossible to work, all model constantly retourn Agent execution terminated due to error.
I was able to work 1h, then impossible. All troubleshooting steps are failing…

[wang_daniel]

High frequency of getting this error again today. I’m using the claude opus 4.5

[Jan_Razny]

Indeed. Antigravity is an unusable paperweight. If this continues I will not renew my subscription.
This is slower than doing everything by hand, and I pay for the frustration of re-running every single inference 5 times. And the times it does actually complete it is handled by a lobotomized and quantized model.

[samiralibabic]

What a rollout by Google. I must admit it’s unusual. They started vibe-coding?!

Anyway, this what happens in my case: Fix for Quota Limits - OAuth issue

[J_O]

This had so much potential. It 10xed my productivity when it first released.
Now they cant keep this going and everythings going down the drain.
Such a disappointment and a bait and switch.

First get everyone onboard with generous claude quotas and then nerf claude to the extend that it cant even remember what it said one message earlier.

If you can get any reply at all.

Absolutely unusable now. Doing this to paying customers (ultra here) is an absolute disgrace.
Reminds me again why i absolutely despise google

[German_Aristov]

‘Agent terminated due to error’ - Ultra plan, not again please? constant errors like this started appearing again…

[Deepankar]

Same issue on Google AI Ultra: “Agent execution terminated due to error.” Unusable for 24 hours. I’ve had the subscription for 5 days and it’s been down for 2. What kind of uptime should we expect over a 30-day month?

[Sapphire]

Today, the Gemini 3 Pro model had fewer errors, while the Opus model had over 90% errors. A simple problem required repeated attempts to complete, consuming approximately 40%-60% of the five-hour time limit. However, the Gemini 3 Pro performed as poorly as ever. I cannot confidently entrust work to Gemini.

[Hugh_Lyu]

For those suffering from this error, i have created one simple desktop agent to auto-click the Retry to bypass this issue. Please check out here https://www.npmjs.com/package/@tiwater/viber

1. Run Antigravity with CDP enabled on port 9333:
   Antigravity --remote-debugging-port=9333

   it’s fine to see this warning: Warning: ‘remote-debugging-port’ is not in the list of known options, but still passed to Electron/Chromium.

2. Run this command in terminal: npx @tiwater/viber , and leave this terminal open there.

That’s it. it will monitor the Antigravity window and click Retry as soon as it pops up. Enjoy.

[StevenX]

Although it’s working reasonably well again and there are fewer errors, Gemini 3 Flash in particular has become extremely slow. It’s truly unbearable. I hope it improves. I have no idea if this was done intentionally to artificially reduce the quota, or if it’s a bug or server overload, but this absolutely needs to be fixed. Four weeks ago it was much faster.

[corelink]

I’m extremely new of this AI coding stuff(don’t know a single code). i feel the same, model not as expected sometimes it said “done“ but the fact is not.. I’m subscribe Pro, i found a way that combine with google Gemini and Antigravity Agent works fine. hope it can help.

[donk7413]

Same here. Pro plan,Agent terminated due to error since 2 hours. Randomly works..

[etienne]

Same issue again, does not work.

[Krisz_Kom]

+1 experiencing the same issue

[Hussam_Mj]

same issue . does not work