Struck in a "Unknown: Agent execution terminated due to error." for the past 24 hours

was working on a code base yesterday and my session terminated with this error, cannot seem to recover to normal state even after clearing cache and reinstalling the app.

Hi @bruhnav,

The message Unknown: Agent execution terminated due to error. is a generic error that can happen for a wide variety of underlying reasons (such as network proxy issues, corrupted workspace states or backend model capacity constraints).

Could you try the following troubleshooting steps to see if it works for you?

  • Explicitly create a completely new workspace and start a fresh chat there
  • Sometimes this happens due to temporary capacity constraints. Try changing your active model to see if the session recovers
  • Ensure you are upgraded to the latest version of Antigravity

If it still fails, please reply with your OS, Antigravity version and a Trajectory ID.

Yes, I have tried working in a new workspace, changing the active model, and updating to the latest version of Antigravity, but the error still persists.

My system details are:

  • OS: Windows 11 Home Single Language, Version 25H2
  • Antigravity IDE Version: 2.5.5
  • Trajectory ID: 8cf9188d-9a47-44c3-a020-28****

The Error ID and Trajectory ID appear to be the same in this case. The error message only displayed the Error ID, so I checked the Antigravity logs and conversation database, where this same ID was listed as the trajectory_id.

I also noticed that I am experiencing another issue when trying to log in through a different environment. I receive the following error:

Post "https://oauth2.googleapis.com/token": tls: failed to verify certificate: x509: certificate signed by unknown authority

I am not sure whether this is related to the agent execution error, but I thought it would be useful to mention it in case both issues have a common underlying cause.

The Antigravity IDE environment itself has normally worked without any issues for me until now, so the agent execution error appears to be a new problem in an environment that previously worked normally.

Please let me know if you need any additional logs or diagnostic information.

Hi @bruhnav,

Thanks for providing those details. It is very likely that the two issues you are seeing are related. If the agent cannot authenticate due to the certificate error, it will fatally terminate.

If you are seeing the underlying error tls: failed to verify certificate: x509: certificate signed by unknown authority, this occurs when a corporate network proxy, VPN or anti-virus SSL inspection tool intercepts network traffic to Google endpoints and uses a custom certificate that the agent doesn’t recognize.

To fix this, ensure your network’s custom CA certificate is installed in your Windows Trusted Root Certification Authorities store or configure your security software/proxy to bypass SSL inspection for *.googleapis.com and oauth2.googleapis.com.