Summary
The recurring “Agent terminated due to an error” issue in Antigravity is exclusively affecting Google Workspace accounts (specifically Google AI Ultra for Business). Personal Gmail accounts — including free-tier accounts — are working perfectly fine with zero agent termination errors.
Critically, this is not an intermittent issue — the Workspace account is essentially non-functional. The agent terminates on nearly every interaction, and retrying does NOT resolve it. Retry briefly worked for only a few hours on one specific day, but otherwise the agent remains completely broken on Workspace accounts.
This distinction is critical for the engineering team to narrow down the root cause, as it strongly suggests the issue lies in how Workspace/organization-level authentication, tokens, or quota enforcement interacts with the Antigravity agent backend.
Environment & Account Details
| Detail | Workspace Account | Personal Account |
|---|---|---|
| Account Type | Google AI Ultra for Business (Workspace) | Personal Gmail (free tier) |
| Agent Terminated Errors | ||
| Retry Works? | ||
| Antigravity Version | Latest (v1.22.2+) | Same version |
| OS | Windows | Same machine |
| MCP Servers | Disabled (ruled out) | N/A |
What Happens
- On the Workspace account: The agent terminates with “Agent terminated due to an error” on nearly every interaction. Retrying does NOT fix it — the agent just terminates again. The platform is essentially unusable on the Workspace account. Retry only worked briefly for a few hours on one specific day, but has otherwise been completely non-functional.
- On a personal Gmail account (even free tier): The exact same workflows, same models, same machine — zero termination errors. Everything runs smoothly.
Why This Matters
- It’s NOT a general platform issue — personal accounts are completely unaffected.
- It’s NOT a temporary/intermittent issue — the Workspace account is persistently broken, not just occasionally failing.
- Retry does NOT help — unlike typical transient errors, retrying just results in another termination.
- It’s NOT an MCP conflict — MCP servers have been disabled and the issue persists.
- It IS account-type specific — the only variable that triggers the error is using a Google Workspace (AI Ultra for Business) account.
This points to something in the Workspace authentication flow, token refresh mechanism, organizational policy enforcement, or quota handshake that is causing the agent session to terminate prematurely — and it is not recovering on its own.
Request to the Engineering Team
- Please investigate the difference in how Workspace vs. personal account sessions are handled on the backend.
- Workspace users are paying customers (AI Ultra for Business) and currently cannot use Antigravity at all, while free-tier personal accounts work flawlessly.
- A previous post ([Bug] “High traffic” error causing agent termination 3-4x per session) was acknowledged and escalated by @Mrinal_Ghosh, but I want to make the severity and Workspace-specific nature of this bug explicitly clear — the product is completely non-functional on Workspace accounts.
Steps to Reproduce
- Sign into Antigravity with a Google Workspace account (AI Ultra for Business).
- Start any agent task (coding, research, etc.).
- The agent will terminate with “Agent terminated due to an error” almost immediately.
- Click retry — the agent terminates again (retry does NOT work).
- Sign out and sign in with a personal Gmail account.
- Run the exact same task — no termination errors occur.
Thank you for looking into this. This is a blocking issue — Workspace accounts cannot use the product at all. Happy to provide logs, feedback reports, or any additional information to help resolve this.