Press Esc to close

Google is locking paying Antigravity users out over terms of service

Google is locking paying Antigravity users out over terms of service
Official Google Antigravity artwork for the Antigravity CLI

Image credit: Google Antigravity, official Antigravity CLI blog artwork.

Some paying users of Google Antigravity say the product has been disabled on their accounts for a Terms of Service violation, including people who say they used only Google's official tools. At the time of this writing on November 18, 2026, new reports were still appearing on X and on Google's AI developer forum. This is a different problem from the Hydrogen access error this site reported earlier. In October, this site also covered a developer who said Google warned him after a Gemini security audit prompt in Antigravity.

Users receive HTTP 403 with the reason PERMISSION_DENIED, and a notice that says, "This service has been disabled in this account for violation of Terms of Service." The block applies to Antigravity and its official command-line tool, often called agy.

Google has published specific rules on third-party access. The additional Antigravity Terms of Service bar using the service in connection with products Google did not provide. Using third party software, tools, or services to access the service, including OpenClaw with Antigravity OAuth, is a breach that may lead to suspension or termination of Antigravity or Gemini CLI accounts. The official FAQ says the same for Claude Code, OpenClaw, or OpenCode used with an Antigravity login, and recommends a Gemini Enterprise or Google AI Studio API key instead. Headless CLI mode, run as agy -p, is intended for direct scripting and CI workflows. Wrapping agy inside third-party coding agents or automating account rotation is not supported under consumer plans.

On November 17, Rody Davis, a developer relations engineer on Google's Antigravity team, told users on X that certain proxy setups and unofficial access methods are against the terms and can get Antigravity access revoked.

Still, some paying users say they were locked out while staying on official tooling. On November 18, Michael, posting as DotsonZion, said he had used the official agy MCP to connect Antigravity to an open-source project. Official replies have said these actions restrict Antigravity access rather than closing the whole Google account.

On November 16, a user posting as MOMOZHTW shared the same error and said they had used only the official CLI for local development. Jason Hreha asked Davis for help after a lockout he associated with T3 Code, which he said was supposedly allowed.

On Google's AI developer forum, a Google AI Ultra subscriber wrote that official agy CLI requests began failing with the same 403 error, and that he never connected the account to third-party tools such as OpenCode or OpenClaw. A Google AI Pro subscriber said he ran official CLI prompts through Claude Code, a use the FAQ says is not permitted. Later posts describe the same error, including people who say they used only the official client, and a user who said a third-party proxy triggered the flag.

A user posting as loaful asked Davis whether official agy ACP connections to Hermes, OpenClaw, Pi, or T3 Code would get an account suspended. No public reply was found. Google's documentation still lists official MCP and Agent Client Protocol support.

Users have also said the appeal path is unclear. Google provides an official appeal form for Antigravity, Gemini CLI, and Gemini Code Assist suspensions. Frequent forum responder Rebbanpalli Naveen has written that these 403 PERMISSION_DENIED cases cannot be reviewed or reversed on the forum, that review takes about 48 to 72 hours, and that no confirmation email is sent. Approved access is supposed to return at the next sign-in. Each account gets only a single appeal, those replies say, and a repeat violation can bring a permanent suspension. Several users say they already submitted the form and are still waiting.

On November 13, Davis said an earlier batch of access restrictions had been fixed, and wrote, "Accounts are not banned, only Antigravity access, but this has been resolved." On November 17, Cristian Garcia, posting as cgarciae88, wrote that users will not lose their Google accounts if they are suspended on Gemini or Antigravity.

At the time of this writing, official Google, Antigravity, and Google DeepMind accounts had not posted a public note on these lockouts. Davis's November 18 birthday post about a quota reset did not address them. Paying users who say they followed official tools still want clearer rules on official integrations.

Comments

Reader support

No ads. Just independent reporting.

Techcity Authority runs without advertising. Hosting, tools, and the hours behind each piece are supported by readers instead. Even a small contribution goes a long way — and every supporter is credited by name below for the month they give.

Support the site

Monthly via PayPal · cancel anytime

Secure checkout on PayPal. Your name appears here for the month you support.

This month’s supporters

    No supporters yet this month — yours could be the first name here.