Google bans third-party Antigravity logins as a ToS violation

What we checked

• Were Antigravity blocks caused by third-party agent login, a policy violation, or a rollout error, and is there an official remediation path? confirmed. Google enforced a written third-party-access rule, not an unexplained rollout failure. Antigravity terms and the FAQ prohibit third-party software with Antigravity OAuth, and a 27 February 2026 Gemini CLI maintainer post said bans targeted third-party tools and proxies. A first-strike Google Form recertification path is official; a second flag is described as a permanent ban. [1][2][6]
• Did Pi remove Antigravity and Gemini CLI providers because those logins were getting users banned? confirmed. Yes. After a user reported a Cloud Code Assist 403 Terms-of-Service disable following Antigravity OAuth, Pi maintainer badlogic wrote on 30 April 2026 that Antigravity and Gemini CLI support had been removed on main. A Pi discussion the next day said using Pi auth with Google subscriptions can get users banned and told them to switch to a pay-as-you-go API key. [9][14]
• Is wrapping the official Antigravity CLI a policy-safe way for third-party products to reuse consumer Antigravity login? refuted. No. The Antigravity FAQ says wrapping agy headless mode in third-party agents is not supported under consumer plans. On 20 October 2026 Google staff said hosting agy in a third-party platform or relaying OAuth through a custom app is not permitted even for a private prototype and can trigger automated account suspension. [2][12]

What we found

• Antigravity Additional Terms section 6 forbids using the Service with products Google does not provide. The clause names a concrete example: using OpenClaw with Antigravity OAuth is a breach and may suspend or terminate Antigravity and/or Gemini CLI accounts. That is first-party legal text, not a forum rumor. [1]
• The Antigravity FAQ repeats the ban for third-party agents and tells users to use a Vertex or Google AI Studio API key. Gemini CLI’s FAQ and terms-privacy docs say the same for harvesting Gemini CLI OAuth. On 19 October 2026, Google staff told a VS Code extension author there is no supported way for a third-party app to use a consumer Google AI plan or Antigravity login. [2][3][4][5]
• On 27 February 2026, Gemini CLI maintainer jackwotherspoon wrote that account disruptions were Antigravity bans for third-party tools or proxies. Shared backend abuse controls also blocked Gemini CLI and Gemini Code Assist. Google ran a system-wide unban, then described email plus a Google Form recertification, restore in a day or two, and a permanent ban on a second flag. [6]
• GitHub issues match the policy. An omp user was suspended a day after Antigravity OAuth /login. Maintainer can1357 said on 27 February 2026, "You can get banned, I can't really give you any guarantee." A later comment reported a Pro account banned 20 minutes after /login. A Pi user got a Cloud Code Assist 403 ToS disable after Antigravity OAuth; Pi then removed both providers. [7][8][9]
• Consumer Gemini CLI Google login is gone for individual plans. Google’s 19 May 2026 Developers Blog and an 18 June 2026 team post said Gemini CLI stopped serving Google AI Pro, Ultra, and free individual accounts on 18 June 2026, directing those users to Antigravity CLI while enterprise licenses and paid API keys remain. That cutover is separate from the ban wave, but it removes the consumer Gemini CLI OAuth surface those agents also used. [10][11]
• Wrapping the replacement CLI is not a workaround. The Antigravity FAQ says wrapping agy -p in third-party agents is not supported on consumer plans. On 20 October 2026 Google staff said hosting agy in a third-party platform or relaying OAuth through a custom app is not permitted even for a private prototype and can trigger automated suspension. omp still exposes google-antigravity and google-gemini-cli as ordinary /login targets in an open September 2026 issue that had not landed a default-off change by mid-October comments. [2][12][13]

What it means

Treat consumer Google AI and Antigravity login as a product entitlement, not an API key. For a third-party agent, IDE plugin, or “use my Google subscription” feature, the supported paths are a user-supplied Gemini API key from Google AI Studio or Vertex AI / Gemini Enterprise credentials. Do not store, refresh, or forward Antigravity or Gemini CLI OAuth, and do not wrap agy to launder that session.

If a user is already flagged, point them at the in-product Google Form and tell them a second flag is described as permanent. omp and similar harnesses should hide the prohibited providers by default and warn anyone with leftover credentials. A working token is not evidence that Google supports the integration.

Still open

• How reliable is first-strike recertification after February 2026, given later user comments that the form did not restore access on the advertised schedule?
• Will omp disable google-antigravity and google-gemini-cli in a release, or only document the risk?
• Do Antigravity or Gemini CLI bans ever extend to the rest of a Google account? Users asked; no official guarantee was found in sources opened for this research.
• Is there any partner OAuth program for consumer Google One AI plans, or is BYOK and Vertex the only durable third-party path?