Summary
The “Agent terminated due to an error” bug has been plaguing Google Workspace accounts since January 2026 — over 3 months now. It is exclusive to Workspace accounts (AI Ultra for Business). Personal Gmail accounts, including free-tier ones, work perfectly with zero agent terminations. This is a paying-tier-only failure.
I have posted about this issue multiple times. The community thread started by @etienne on January 15 (“Antigravity broken: getting only ‘Agent execution terminated due to error’”) has now reached 451 replies — making it one of the largest bug threads on this entire forum. And it is still not fixed.
Timeline of this issue
| Date | Event |
|---|---|
| Jan 15 | @etienne opens the original thread. 451 replies and counting. |
| ~Early April | I start experiencing the issue consistently on my AI Ultra for Business (Workspace) account. Personal account works flawlessly. |
| Apr 5 | I post about the “Preview” badge discrepancy on Workspace accounts + frequent agent terminated errors. |
| Apr 9 | Official system update claims v1.22.2 restores stability. |
| Apr 10 | v1.22.2 works for roughly ONE DAY, then the terminations come back with full force. |
| Apr 14 | I post two more bug reports. @kmnahidulislam also posts about agent crashing instantly. |
| Apr 15 (today) | The last 2 days are the ONLY days I have been able to use the agent even a little. Even now it terminates every 2-3 prompts. |
The core pattern
- Personal Gmail accounts (free or paid): Work perfectly. Zero terminations.
- Google Workspace accounts (AI Ultra for Business): Agent terminates every 2-4 prompts. Sometimes instantly. Sometimes mid-tool-use.
- v1.22.2 “fix”: Worked for approximately 1 day, then the issue returned.
- Switching models: Makes no difference — the error occurs on Gemini, Claude, and all available models.
- Reinstalling, clearing cache, restarting: None of these help.
What this points to
This is not a model-level or client-side issue. The fact that identical hardware, identical networks, and identical prompts work on personal accounts but fail on Workspace accounts points to a backend issue in how Workspace/organization-level authentication tokens, quotas, or entitlements are being handled.
The additional “Preview” badge discrepancy I reported (Workspace accounts showing “Preview” despite being on a paid Business plan) further supports this — something in the licensing/entitlement pipeline is broken specifically for the Workspace path.
What I am asking for
- Acknowledgment that this is a known, Workspace-specific backend issue — not a client-side configuration problem.
- A dedicated engineering investigation into Workspace token handling, org-level quota enforcement, and entitlement sync — not another generic “stability improvement” that does not address the root cause.
- A public status update when progress is made. 451 replies on the main thread and growing — this community deserves transparency.
My experience over the last two days
To be fair: the last 2 days (April 14-15) are the first time since early April that I have been able to use Antigravity at all on my Workspace account, even intermittently. The agent still terminates unexpectedly every few prompts, but at least it does not crash instantly anymore. This is progress — but it is nowhere near stable enough for serious development work. I still cannot rely on it for multi-step coding tasks, which is the entire point of an agentic IDE.
Environment: Windows, Antigravity latest, AI Ultra for Business (Workspace), stable broadband connection.