New Delhi: Paying Google AI subscribers say they got locked out of Google’s “Antigravity” access after linking their accounts to third-party tools like OpenClaw and OpenCode. The reports say the disruption started for many users in the last week or so, then turned into a louder wave of complaints around February 12 to 14, as 403 PERMISSION_DENIED errors began showing up in Google’s support forums and on Reddit.
What stung people most was the suddenness. Users, including paying $250 a month Google AI Ultra subscribers, say they saw a blunt message on their accounts: “This service has been disabled in this account for violation of Terms of Service,” and they did not get a warning email, a grace period, or a clear appeal route. As of Monday, Feb 23, the posts are still circulating.
Google might be aggressively banning users using antigravity / Gemini OAuth via third-party tools.
One of the user’s paid AI Pro accounts just got hit with:
403 PERMISSION_DENIED
“Gemini has been disabled for ToS violation.”Zero warning.
He wasn’t alone.
Multiple GitHub… pic.twitter.com/5K201uw9Qs
— Aakash (@Cryptobullaaa) February 13, 2026
What users say triggered the lockouts
Based on the reports shared online, a common pattern keeps popping up. Users were on Google AI Pro or Ultra plans. They connected those accounts through OpenClaw or similar tools. Then Google detected the usage and “disabled Antigravity access.”
People are also linking the failures to one specific setup: using Antigravity OAuth tokens inside OpenClaw. That is where the same error keeps showing up again and again, according to the forum and Reddit posts mentioned above.
We’ve been seeing a massive increase in malicious usage of the Anitgravity backend that has tremendously degraded the quality of service for our users. We needed to find a path to quickly shut off access to these users that are not using the product as intended. We understand…
— Varun Mohan (@_mohansolo) February 23, 2026
Google’s policy angle and the “malicious usage” label
The core issue, as described in the reports, is a policy violation tied to “malicious usage.” The claim is that Google’s Antigravity backend is meant for first-party services. When third-party tools route requests through private OAuth tokens, Google’s systems can flag it as abuse or as a way to get around standard API limits.
Google’s side has also surfaced publicly through a post on X. Varun Mohan said they had been “seeing a massive increase in malicious usage of the Antigravity backend that has tremendously degraded the quality of service” for legitimate users. He added they needed to “quickly shut off access to these users that are not using the product as intended.” He also said there is “a path for unaware users to potentially regain access.”
Pretty draconian from Google. Be careful out there if you use Antigravity. I guess I’ll remove support.
Even Anthropic pings me and is nice about issues. Google just… bans? https://t.co/JBq9YCB7nB
— Peter Steinberger 🦞 (@steipete) February 23, 2026
OpenClaw creator calls the ban wave “pretty draconian”
Peter Steinberger, the creator of OpenClaw, described the Google ban wave as “pretty draconian”. He said he will remove support for Antigravity from the tool and warned users to be careful if they plug it in.
That one line matters, since it hints this was not a small glitch. It reads like a hard stop, not a temporary outage.
The coding LLM war escalated after OpenAI acquired the creator of OpenClaw.
I noticed Anthropic and Google blocked OpenCode from using their Pro plan subscriptions, so I really can use Codex and open-source models there.
Only OpenAI seems generous here. pic.twitter.com/iFS3j49oIg
— Yuchen Jin (@Yuchenj_UW) February 23, 2026
What affected users can check right now
If you are trying to figure out if you are in this bucket, the reports point to a few common signs:
- A sudden “disabled for violation of Terms of Service” notice
- 403 PERMISSION_DENIED errors after linking via OpenClaw
- Antigravity OAuth tokens being used inside third-party tools
No one likes getting a ban screen after paying. Still, this looks like a policy enforcement story, not a billing error story.
What alternatives are there?
If you are an OpenClaw user leaning on Antigravity, the community’s message is simple. Stop and switch. OpenClaw’s official guidance is to stick to API keys instead of OAuth tokens. People are also sharing workarounds and plan B options. Names like MiniMax and OpenAI’s Codex keep coming up as alternatives that users see as less risky, mainly since they do not tie into Google account access in the same way.