On Feb. 23, 2026, a mass ban targeting users of the open‑source AI agent framework OpenClaw rocked developer communities worldwide. Google abruptly restricted the accounts of many users routing Gemini and the Antigravity platform through OpenClaw, even affecting some paid AI Ultra subscribers (US$250 per month). The episode quickly escalated from a technical discussion into an industry dispute, exposing sharp tensions between "compute sharing" and "service fairness" in the current AI ecosystem.
According to public statements by Google DeepMind engineer Varun Mohan on X and multiple media reports, the bans began to emerge between Feb. 12–14 and peaked on Feb. 23. Affected users typically used OpenClaw as an intermediary proxy to make heavy calls to Gemini backend APIs, severely consuming Antigravity platform backend compute resources and degrading service quality. Google characterized this as "malicious usage", saying such behavior violated the Terms of Service (ToS) and unfairly affected regular paying users.
Scope and Actual Impact
Based on posts in the Google AI developer forum, Reddit r/google_antigravity and extensive feedback on X, the bans primarily targeted two groups of users:
- Developers calling Antigravity and Gemini models using OpenClaw OAuth credentials;
- Users who built proxies with OpenClaw and made high‑frequency Gemini token consumption.
Some users reported not only Antigravity access being blocked with 403 errors, but associated Gmail, Google Workspace and even their entire Google accounts were affected. Several AI Ultra subscribers paying US$250 monthly said they were merely "using their paid quota normally" yet were suddenly banned without prior warning or a clear appeals channel.
Google DeepMind responded that the action was not a permanent ban on third‑party tools but a rapid cut‑off of "unexpected usage patterns" to protect the experience of the majority of legitimate users. Varun Mohan stated: "We observed a large amount of malicious usage on Antigravity backends that severely impacted service quality. We understand some users may unknowingly violate the ToS and we will provide recovery paths for them, but resources are limited and we must prioritize fair experience for genuine users."
OpenClaw Founder Fires Back: Will Remove Google Support
OpenClaw founder Peter Steinberger expressed strong displeasure on X at Google's approach. He said: "Even Anthropic communicates first when problems arise; Google simply chose to ban." He then announced that OpenClaw will remove OAuth support for Google Antigravity and Gemini in the next release.
The decision is seen as an open‑source community pushback against the "walled garden" policies of major providers. OpenClaw, an open agent framework intended to give developers flexibility across models, became the target after some users allegedly used it for "compute arbitrage" — high‑frequency calls that exploit paid accounts to consume backend resources.
Notably, Anthropic had updated its terms of service around Feb. 20 to explicitly prohibit using Claude account OAuth credentials in third‑party tools like OpenClaw. Google's action is viewed by some as following Anthropic's lead in an industry‑wide effort to block such usage.
Underlying Tensions
The bans reflect a concentrated outbreak of conflict over fair allocation of compute resources in the AI ecosystem. With the rise of agentic AI, developers increasingly use third‑party proxy tools (such as OpenClaw) to batch‑call multiple model APIs and automate workflows. That behavior can directly overconsume platform backends and degrade service for ordinary users.
The hardline stance from Google and Anthropic highlights their dilemma between "openness vs. control":
- On one hand, they want broad adoption of their models to grow their ecosystems;
- On the other, high‑frequency proxy calls raise compute costs and could be used to train competitor models (so‑called "distillation attacks").
For developers, this means the permissible boundaries for AI tool usage are being redrawn. Many are shifting to self‑hosted proxies or open‑source alternatives, while some users resort to multiple small accounts or API keys to try to mitigate risk.
Industry Impact and Future Trends
The incident has accelerated industry discussions on regulating proxy tools. Likely future trends include:
- Major platforms further tightening OAuth usage rules and explicitly banning or limiting third‑party proxy tools;
- Open‑source agent frameworks accelerating decentralization to reduce dependence on single cloud providers;
- Enterprise users increasingly building private AI infrastructure to avoid similar ban risks.
For Chinese AI developers, this is an important reminder: when using mainstream international models, strictly follow providers' ToS to avoid account risks from improper proxy usage. It also underscores the importance of developing a domestic, autonomous and controllable AI ecosystem.
Conclusion
Google's mass bans of OpenClaw users are both a standard governance response to compute misuse and part of the AI ecosystem's shift from "wild growth" to "orderly regulation." The episode reminds developers that while AI tools bring efficiency, they must respect platform rules and fairness.
As agentic AI advances rapidly, balancing innovation freedom with platform governance will be a core industry challenge. The clash between OpenClaw and Google may be only the opening salvo in a broader contest.
▶️ Enjoyed this article? Creating content is hard!
Follow our YouTube channel:
AI Rosetta
Your likes, subscriptions and shares are our greatest support! 🙏
More AI news at: https://www.airosetta.com