Google Restricting AI Pro/Ultra Subscribers Who Used OpenClaw Without Warning
Original: Google restricting Google AI Pro/Ultra subscribers for using OpenClaw View original →
Accounts Restricted Without Warning
Google has begun restricting the accounts of Google AI Pro and Ultra subscribers who accessed the service through the third-party client OpenClaw via OAuth. The issue surfaced in the Google Developer Forum as affected users reported sudden account restrictions with no prior warning.
Google's Position: ToS Violation
Google's official position is clear: the AI Pro and Ultra subscription plans are designed for use within Google's own ecosystem (referred to internally as "Antigravity"). Using OAuth tokens to power third-party tools with a subsidized monthly plan constitutes a Terms of Service violation.
In messages sent to restricted users, Google stated that the "use of your credentials within the third-party tool OpenClaw for testing purposes constitutes a violation of the Google Terms of Service."
Community Reaction: Divided Opinions
Community reaction is split. Some see Google's action as reasonable — comparing it to taking takeaway containers to an all-you-can-eat buffet. The monthly plan is designed for in-platform consumption, not API-level access, which is priced separately for good reason.
Others view the restrictions as draconian. The sudden, unannounced nature of the account restrictions has drawn sharp criticism, even from those who understand the underlying rationale. Users argue that if this type of OAuth usage was a violation, clearer documentation and warnings should have come first.
A Structural Problem in AI Subscriptions
This incident exposes a structural tension in AI subscription models. Major AI providers offer cheap monthly plans priced well below API costs, which creates an incentive for technically-savvy users to route subscription credentials through external tools to get cheap API-equivalent access. Google is essentially enforcing what was already in the terms — but doing so in a way that has caught many users off guard.
Related Articles
MCP moves to a stateless core on July 28, 2026, and GitHub MCP Server already supports the latest spec. The practical changes are fewer session dependencies, less payload inspection, and official conformance tests for agent infrastructure.
GitHub says Copilot code review now uses CLI and SDK file-exploration tools such as grep, rg, glob, and view. The change has reduced review costs by about 20% while preserving review quality in offline and online evaluation.
GitHub Desktop 3.6 moves three agent-era Git chores into the client: worktrees, Copilot-written commits, and AI-assisted merge conflict review. The bigger shift is that Desktop now treats parallel branches and model choice as everyday developer controls.