Google Restricts OpenClaw Access to Antigravity, Signaling Shift in AI Agent Ecosystems

Google has sparked controversy by restricting access to its Antigravity “vibe coding” platform for users employing the open-source autonomous AI agent, OpenClaw. The move, initiated on February 23, 2026, alleges “malicious usage” stemming from OpenClaw users accessing a disproportionate number of Gemini tokens, impacting service quality for other customers. The restrictions have led to some users losing access to their Google accounts, raising concerns about the future of open-source interoperability within the rapidly evolving AI landscape.

The Core of the Issue: Token Usage and System Strain

According to Google, users leveraging OpenClaw in conjunction with Antigravity, and those connecting OpenClaw agents to services like Gmail, were exceeding expected usage levels. Varun Mohan, a Google DeepMind engineer and former CEO of Windsurf, explained in a social media post that the company observed a “massive increase in malicious usage” that degraded service quality. Google maintains this isn’t a permanent ban on third-party platform access, but a recalibration to align with its terms of service. VentureBeat and The Register both reported on the situation.

OpenClaw’s Role and OpenAI Connection

OpenClaw gained traction as a tool enabling users to run shell commands and access local files, fulfilling a key promise of AI agents: efficient workflow automation. However, its open-source nature and rapid evolution have presented challenges regarding security and adherence to platform terms of service. The timing of Google’s action is notable, occurring just one week after OpenAI announced that OpenClaw creator Peter Steinberger had joined the company to lead its “next generation of personal agents.” This move positions OpenClaw, while remaining open-source, under the strategic guidance of Google’s primary competitor.

User Reactions and Account Bans

The restrictions have triggered a backlash from OpenClaw users. Reports on platforms like Y Combinator’s Hacker News and Reddit’s r/google_antigravity subreddit detail users losing access to their Google accounts after using OpenClaw. Some users expressed concern that the bans could extend beyond Antigravity, impacting access to Gmail, Drive, and YouTube. One user on Reddit reported emailing support and revoking third-party access without success in restoring their account.

A Broader Industry Trend: Walled Gardens and Agent Ecosystems

Google’s actions mirror a growing trend within the AI industry towards “walled garden” ecosystems. Anthropic previously throttled access to Claude Code after identifying similar abuse concerns. Both companies are prioritizing vertically integrated experiences, allowing them to control telemetry and subscription revenue. This shift represents a departure from the early days of large language model (LLM) development, which were characterized by open-source interoperability.

Implications for Enterprise Adoption

The “Antigravity Ban” highlights the risks associated with relying on third-party agent frameworks. Key takeaways for enterprise technical decision-makers include:

• Platform Fragility: Even high-paying customers have limited leverage when providers alter their “fair use” definitions.
• Local-First Governance: Prioritizing agent frameworks that can run locally or within Virtual Private Clouds (VPCs) can mitigate risk.
• Account Portability: Decoupling AI development environments from core corporate identity providers is crucial to avoid widespread disruptions.

Looking Ahead

The era of “bring your own agent” to frontier models appears to be ending. As Google and OpenAI solidify their positions, enterprises must carefully weigh the benefits of open-source flexibility against the stability and control offered by proprietary ecosystems. The future of AI agents will likely involve a balance between these approaches, with a growing emphasis on secure, governed environments and direct API contracts for scalable deployments.