Recently, we noted that Google had refreshed its Google Antigravity client, concurrently orchestrating a mass reinstatement of user privileges previously revoked due to token reverse proxying. To restore seamless functionality, users need only purge their cache or perform a clean reinstallation of the Antigravity application.
Concurrently, Google has vehemently reiterated its anti-abuse tenets, stipulating that authenticating a Google Antigravity account through third-party instruments constitutes a blatant transgression of its Terms of Service. Such unauthorized instruments encompass, but are by no means limited to, platforms such as OpenClaw and OpenCode.
During the recent wave of account suspensions, Google provoked widespread user indignation by failing to preemptively articulate that OAuth token reverse proxying was a punishable offense, thereby executing bans without forewarning. In response, Google has now underscored its commitment to elucidating the account recovery protocol moving forward; consequently, should a user face suspension for violating the terms, they will retain the avenue to submit a formal appeal for reinstatement.
Naturally, delineating a recovery process and guaranteeing a successful appeal are entirely disparate matters. Should Google conclude that a user has engaged in flagrant abuse—most notably by reverse proxying to external utilities or engaging in unauthorized commercial distribution—the Antigravity privileges may face irreversible termination. Thus, it is highly advisable that users permanently discard any intentions of funneling Antigravity through the OpenClaw AI bot.
Regarding the recent tempest of account bans, Google eventually shed light on the underlying catalysts. The epicenter of the crisis was the OpenClaw AI bot, which precipitated a catastrophic overextension of computational resources and a precipitous decline in service quality. This acute degradation undeniably compromised the experience of legitimate Antigravity users, leaving Google with no recourse but to swiftly and indiscriminately ban all proxy-wielding accounts.
At present, the sole entity officially sanctioning OAuth reverse proxying remains OpenAI Codex. Given that the progenitor of OpenClaw has recently aligned with OpenAI, users may, for the time being, safely proxy Codex into their bots without reprisal.
This privilege extends equitably to both premium and complimentary users of Codex. Should one find the allotted quota lamentably insufficient, the creation of supplementary accounts might be entertained; however, one must tread with caution, as such maneuvering risks detection and subsequent banishment by OpenAI.
Support Our Threat Intelligence
If you find our CVE report and cybersecurity news helpful, consider supporting our work.