Google's Antigravity Terms Say Using OpenClaw Can Get Your Entire Google Account Suspended
Google's Antigravity terms of service contain a clause that most developers skimmed past: connecting a third-party tool like OpenClaw or OpenCode to your Antigravity OAuth session counts as a breach of the agreement. That's not a hypothetical reading of dense legal text. Developer Gergely Orosz called it out directly, quoting the relevant line, and Google's own AI developer forum has multiple active threads from people who woke up to a suspended account after doing exactly that.
The clause, in Google's own words
Antigravity's additional terms state that using third-party software, tools, or services to access the service, the terms give OpenClaw as the named example, is a breach of the agreement, and Google reserves the right to suspend or terminate both your Antigravity and Gemini CLI access for it. Orosz's post on X put it bluntly: "if they determine you use Antigravity in a way they suspect is eg third-party usage... they can suspend your Google account. One reason to NOT use Antigravity. I'm not taking this risk, sorry."
That last part is the detail worth sitting with. This isn't scoped to your Antigravity access. It's your Google account, the same one behind Gmail, Drive, Photos, and whatever else you've built on Google's identity layer over the years.
This has already happened to real people
Search Google's own AI developer forum and you'll find it isn't a theoretical risk. Threads titled things like "Appeal Request for Erroneous Account Suspension (403 ToS Violation)" and "This service has been disabled in this account for violation of Terms of Service" show paying customers locked out with little warning, then stuck filing appeals into a support process with no clear timeline. Some of these threads go back months, so this isn't a brand-new enforcement wave, but it's the kind of policy most developers never read closely enough to know it applies to them until it does.
Why this happens to solo operators specifically
Indie developers are the ones most likely to trip this. If you're on a team with a dedicated Google Workspace admin, your AI tooling and your personal account are probably already separated by policy. If you're a solo operator, there's a good chance your Antigravity or Gemini subscription is tied to the same personal Google account you've used for fifteen years, because setting up a second one felt like unnecessary friction.
And solo operators are also the ones most likely to chain tools together. Wiring Antigravity's OAuth token into a third-party CLI, an orchestration layer, or an agent framework that isn't Google's own is a completely normal thing to do when you're trying to get more leverage out of a subscription you're already paying for. It's also, per this clause, exactly the behavior that gets flagged.
What I'd actually do
Isolate the account before you need to, not after. If you're going to use Antigravity or the Gemini CLI with any third-party tool, agent framework, or OAuth relay that isn't a Google-official surface, do it from a dedicated Google account that isn't the one holding your email, your domain admin access, or anything else you can't afford to lose. It costs you a few minutes of setup. Losing Gmail and Drive because a suspension appeal takes three weeks costs you a lot more than that.
If you're already running Antigravity through your primary account and using it with anything outside Google's own CLI and desktop app, that's worth fixing today, not after your next appeal thread.
The honest take
I don't think Google is wrong to have terms preventing abuse of its infrastructure through unofficial channels, and I'd guess a real share of the affected accounts were doing something closer to quota abuse than an ordinary indie dev workflow. What I do think is unreasonable is tying that enforcement to a person's entire Google identity instead of scoping consequences to the product where the violation happened. A Gmail account isn't a subscription tier. Until Google draws that line more carefully, the safest move is to draw it yourself.
Author
Lukas
@lukcombinator