To the builders: we heard you. We're welcoming back everyone who recently had their Google Antigravity accounts restricted for use of third-party tools. Moving forward, we’ll have clear steps for users to restore their account if it’s restricted.
— Google Antigravity (@antigravity) February 27, 2026
To maintain the integrity of…
Update 02/03/26 – 04:19 pm (IST): Google has reversed course. On February 27, the official Google Antigravity account posted on X that it is welcoming back everyone whose account was restricted for using third-party tools. This is a broader reinstatement than what Varun Mohan had initially hinted at, where only “eligible” users would get a path back.
Google also updated its FAQ to explicitly name Claude Code, OpenClaw, and OpenCode as prohibited third-party tools, and recommends switching to a Vertex or AI Studio API key for anyone who wants to use a third-party coding agent with Gemini. The ban on using third-party tools with an Antigravity login remains in place, but Google says it will now have clear steps for account restoration if restrictions happen again going forward.
Original article published on February 24, 2026, follows:
Google’s Antigravity has been stealing the spotlight for all the wrong reasons in the past few days. Developers started seeing that dreaded red warning pop up saying their Google Account has been disabled. Many traced it straight back to using OpenClaw with their paid Antigravity or Gemini AI subscriptions.
We dug into the start of this ban wave and Peter Steinberger’s take on it yesterday. You can read the full story here.
The pattern is clear. People on the $250 per month Google AI Ultra plan hooked up their OAuth tokens through OpenClaw to power their coding agents. It worked great for a while. Then Google flipped the switch. Users got hit with messages about policy violations, no warning emails, and a push to restore access before data gets wiped.
Varun Mohan, who runs Antigravity at Google, came out on X with an explanation. They said that they noticed a massive jump in backend usage that hurt service for everyone else. So they moved fast to block accounts where most activity wasn’t actual Antigravity product use. Over 90% proxy traffic in many cases.
Interestingly, though, Varun claims that only Antigravity access got cut. Gmail, YouTube, Photos, the rest of Google services, they’re all still working. But other affected users would beg to differ. As we mentioned in our previous coverage, some users did claim that their entire Google accounts were disabled.
One fresh example is from user @iamlukethedev. They posted a screenshot of the email they received notifying them that their Google account was disabled. It’s worth noting that the email itself doesn’t mention OpenClaw or the exact reason why it was disabled, but it does pin it down to a policy violation.
Meanwhile, a few others in Varun’s replies noted that they were banned from Gemini CLI as well. This real-world user experience contradicts the information Varun shared.
On forums and Reddit, affected folks are frustrated. Paying top dollar only to get locked out feels rough, especially with zero notice. Some call it oversold capacity more than malice. Others point out the terms didn’t spell out the OpenClaw ban explicitly.
If you got hit, the notice seems to give a “Try to restore” button. Also check your account notifications at https://myaccount.google.com/notifications for any security flags.
Right now, sticking to official API keys looks safest. Or switch to providers that don’t mind the integration. Google says they’re working to bring eligible people back soon and will give better warnings going forward.
Featured image generated with AI


