[Bug] Still broken - "Agent Terminated" error persists on Workspace accounts after v1.22.2 fix

Google Antigravity
1

The short version

The “Agent terminated due to an error” bug on Google Workspace accounts was not fixed by v1.22.2. It worked for roughly one day after the update, then came right back. This has been an ongoing issue since early March 2026 - over a month now - and it exclusively affects Workspace accounts.

What’s happening

Every time I start an agent task on my Workspace account (Google AI Ultra for Business), the agent terminates within the first few interactions. Sometimes on the very first tool call. The only workaround is clicking retry over and over until it eventually gets through - which can take dozens of attempts on a bad day.

Today is actually one of the better days. The agent is kind of working, but it still terminates repeatedly. You click retry, it terminates again, retry, terminates, retry - and maybe on the fourth or fifth try it goes through. It’s functional enough that I can get some things done if I’m patient, but nowhere near stable enough to actually code or do sustained work.

On a bad day (which is most days), the agent is completely unusable. It terminates on every single interaction and retrying doesn’t help at all.

The Workspace-specific proof

This is the part that I really want to emphasize because it makes the root cause crystal clear:

  1. Sign into Antigravity with a Google Workspace account (AI Ultra for Business)
    1. Start any task → agent terminates repeatedly
    1. Sign out, sign into a personal Gmail account (even free tier)
    1. Run the exact same task, same machine, same setup → works perfectly, zero errors
      I’ve tested this dozens of times at this point. Same models, same workflows, same machine. The only variable is the account type. Workspace = broken. Personal = fine.

What I’ve already ruled out

  • X MCP servers - all disabled, issue persists
    • X Model-specific - happens on every available model
    • X Version-specific - running latest (v1.22.2+), same behavior
    • X Network/machine - same machine works fine with personal account
    • X High traffic / capacity - if it were capacity, personal accounts would be affected too. Also, the agent works immediately on retry, proving there’s no actual capacity issue
    • X v1.22.2 fix - worked for about one day, then the issue returned

Why this matters

Workspace users on AI Ultra for Business are paying customers. We chose the business plan specifically for professional work - coding, research, development. But for over a month, the experience has been significantly worse than what free-tier personal accounts get. That’s backwards.

I’ve filed multiple in-app feedback reports as recommended by @Mrinal_Ghosh in a previous thread. I’ve posted detailed reproduction steps. The issue was acknowledged and escalated weeks ago. But it’s still here.

What I’m asking for

  1. Acknowledgment that this is a known, active issue for Workspace accounts specifically (not resolved by v1.22.2)
    1. Transparency on what’s different about how Workspace account sessions are handled on the backend - is it auth tokens, org-level quota enforcement, session management, something else?
    1. An ETA or priority level - even a rough one. Is this actively being worked on? Is it in a queue? Just knowing it’s on someone’s sprint would help.
      I’m not trying to be difficult here. I genuinely love the platform and want to keep using it for real work. But right now, on a Workspace account, it’s not reliably usable. Happy to provide logs, recordings, feedback reports - whatever helps get this resolved.

Previous related threads:

  • [Bug] “High traffic” error causing agent termination 3-4x per session (acknowledged by @Mrinal_Ghosh)
    • [Bug] “Agent Terminated” error is EXCLUSIVE to Google Workspace accounts
      Thanks for reading.
2 Likes
2

Hey i just solved this for myself. Had the 400 error for the past week.

I had to attach a free cloud package to my workplace account. I did this to preserve my domain specific workplace email that I purchased. I then had to cancel my workplace subscription in order for google to remove my account from the enterprise state.

Once I canceled my workplace subscription Antigravity began working again.

I haven’t actually received any meaningful response from a Dev on this forum, or through the support emails. Everything has been automated and generic and basically the fixes suggested were unrelated to Antigravity at all.

Early on I tried to have Gemini help me solve it with no luck. I tried again today and just shoved everything I got told to do that wasn’t helpful into a likely terrible prompt.. and it nailed it.

it pointed me to the Antigrav docs page FAQs.
it’s actually written there: “Please try using an @gmail.com email address if having challenges with Workspace Google accounts.”

why nobody could let the numerous users posting about this problem for weeks in this forum know about that, i don’t know.

1 Like