Like, a corporation had a weakness you could exploit to get free/cheap thing. Fair game.
Then someone shares the exploit with a bunch of script kiddies, they exploit it to the Nth degree, and the company immediately notices and shuts everyone down.
Like, my dudes, what did you think was going to happen?
You treasure these little tricks, use them cautiously, and only share them sparingly. They can last for years if you carefully fly under the radar, before they're fixed by accident when another system is changed. THEN you share tales of your exploits for fame and internet points.
And instead, you integrate your exploit into hip new thing, share it at scale, write blog posts and short form video content about it, basically launch a DDoS against the service you're exploiting, and then are shocked when the exploit gets patched and whine about your free thing getting taken away?
Like, what did you expect was going to happen?
> Like, a corporation had a weakness you could exploit to get free/cheap thing. Fair game.
From a pure hacker perspective, I'm surprised there are people calling a legitimate usage a "weakness you could exploit"?
What weakness? What exploit? People have been using it in a way that was technically possible. And they paid for it, many purchased the product specifically because of it.
Then Google unilaterally changed the TOS of a product people already purchased and started pulling the rug. And again, there are people who call themselves hackers who approve of that? Even worse, they call people calling out Google for their monopolistic behavior whining.
It's the same with vulnerabilities in slot machines. Damn rare but they exist - in 2014, when I worked in that industry, one gang made a big bang: in a single night, casinos across Germany had to say goodbye to probably 10 million € [1]. Of course, that vulnerability made massive waves... but from what I heard back then, it had been circulating for many months beforehand. Of course, 10 million € is nothing to sneeze at, but keeping a low profile could have made everyone in the know far more profit.
[1] https://www.t-online.de/digital/aktuelles/id_68982394/softwa...
(See Napster.)
* User uses Google oauth to integrate their open claw
* user gets banned from using Google AI services with no warning
* user still gets charged
If you go backwards, getting charged for services you can't access is rough. I feel sorry for those who are deeply integrated into Google services or getting banned on their main accounts. It's not a great situation.
Also, getting banned without warning is rough as well. I wonder if the situation will be different for business accounts as opposed what seems like personal accounts?
The ban itself seems fair though, google is allowed to restrict usage of their services. Even though it's probably not developer friendly, it's within their rights to do so.
I guess there's some level of post mortem to do on the openclaw side too.
* Why did openclaw allow Google anti gravity logins?
* The plugin is literally called "google-antigravity-auth", why didn't that give the signal to the maintainers?
* Why don't the maintainers, for an integration project, do due diligence checks on the terms of service of everything you're integrating with?
OpenClaw went from virtually unheard of to a sensation in a couple weeks. There was intense commit activity and the main author bragged about not even reading the code himself. It was all heavily AI driven and moving at an extreme rate. Everyone was competing to get their commits in because they wanted to be a part of it.
The entire project was a fast and furious experiment. Nobody was stopping to think if something was a good idea or not when someone published a plugin for using this endpoint. People just thought “cool!” and installed it.
But I guess it's only ok when you work on regular joe facing projects, where the consequences of bugs are on powerless users. If the consequences are on Google, well, that's not acceptable now is it?
Agreed. The lesson is: do not become dependent on Google. Ever.
(Unfortunately I still use youtube and a chromium-based browser. Long-term I hope to find alternatives to both problems. Google search I no longer need because Google already ruined it a few years ago; the quality now is just horrible. I can not find anything useful with it anymore.)
> Hoping for some transparency, I left a single, polite comment asking for clarification on why the update was removed. Surprisingly, my forum account was banned shortly after posting that question.
I could see a problem with logging into Antigravity then exfiltrating the tokens to use somewhere else... But that doesn't sound like what happened. (And then how would they know?)
I haven't used Open Claw, so what else am missing to make this make sense?
When I first tried OpenClaw and chose Google Sign-In, I noticed the window appeared saying "Sign into Google Antigravity" with a Google official mark, and a warning it shouldn't be used to sign into anything besides official Google apps. I closed it immediately and uninstalled OpenClaw as this was suspicious to me, and it was a relatively new project then.
It amazes me that the maintainer(s) allowed something like this...
2. Did a human create the plugin?
3. Are the maintainers human?
By human I mean an animal that is intelligent enough to understand the agreements and what code they are writing.
I feel that sometimes corporations have all 3 montesquieu powers. Google can define eulas, decide if you should be punished, and apply a ban.
Can a shop decide who to serve? I may be wrong, but big tech should not be able to 'just close' accounts, or demonetize accounts on their whim.
There's a good chance the plugin was written by gemini, why did it allow that?
"We’ve been seeing a massive increase in malicious usage of the Anitgravity backend that has tremendously degraded the quality of service for our users. We needed to find a path to quickly shut off access to these users that are not using the product as intended. We understand that a subset of these users were not aware that this was against our ToS and will get a path for them to come back on but we have limited capacity and want to be fair to our actual users."
It feels like a good default for this would be something similar to video game bans: where you get a "vacation" from the service with a clear reason for why that is, but can return to using it later. Given how much people depend on cloud services, permanent bans for what could be honest mistakes or not knowing stuff would be insane.
Good on them that they want to provide a way to bring back customers on board that were burned / surprised by their move.
BUT: The industry is missing a significant long term revenue opportunity here. There obviously is latent demand and Claws have a great product market fit. Why on earth would you deactivate customers that show high usage? Inform them that you have another product (API keys) for them and maybe threaten with throttling. But don't throw them overboard! Find a solution that makes commercial sense for both sides (security from API bill shock for the customer / predictable token usage for the provider).
What we're seeing right now is the complete opposite. Ban customers that might even rely on their account. Feels like the accountants have won this round - but did not expect the PR backlash and possible Streisand effect...
It's not hard to define a quota system and enforce it. If the quota is too high then reduce the quota. If people are abusing the quota with automated requests then detect that and rate limit those users.
If I'm paying $200+ a month I should be able to saturate Google with requests. It's up to Google to enforce their policies via backpressure so that they don't get overloaded.
Then again this is the same company that suspended people's gmail because they sent too many emotes in YouTube chat. Sadge.
Antigravity has very low daily and weekly quotas unless you pay for their most expensive plan, so it means these people drop $200+ a month to run these bots, insanity
Are they though? Another comment (https://news.ycombinator.com/item?id=47116205) seems to indicate these people are all indefinitely suspended with no path to unsuspend them:
> [...] I must be transparent and inform you that, in accordance with Google’s policy, this situation falls under a zero tolerance policy, and we are unable to reverse the suspension. [...]
There is a (pretty generous and imo reasonable) request quota that reset every 24h
The whole concept of service "abusers" is made up bullshit by companies that over promise, over sell and under deliver.
That's not what support has been telling their $250 a month customers.
we are unable to reverse the suspension [1]
I get the need to move fast to stabilise the service but similar to an outage it doesn't take much to put a banner on the support page to let customers know bans are temporary until they can come up with a better way of educating customers. Further more it doesn't much to instruct ban appeal teams to tell customers all bans are under review no matter what the reason is to buy them time to separate Claw bans from legitimate abuse bans that need to be upheld.
The fact that users are paying $250 for a service they can't use for at least the last 11 days kills any sympathy I had that Google needed "quickly shut off access", it's like they just sat on their hands until the social media storm hit flash-point.
After 11 days there still isn't even an official statement, just a panicked tweet from a dev likely also getting hammered on socials, goodness knows how long before accounts are restored and credits issued.
Even the original Google employee in the forum thread just ghosted everyone there after the initial "we're looking into it".
> Our investigation specifically confirmed that the use of your credentials within the third-party tool “open claw” for testing purposes constitutes a violation of the Google Terms of Service [1]. This is due to the use of Antigravity servers to power a non-Antigravity product. I must be transparent and inform you that, in accordance with Google’s policy, this situation falls under a zero tolerance policy, and we are unable to reverse the suspension. I am truly sorry to share this difficult news with you.
Considering the tremendous amount of tokens OpenClaw can burn for something that has nothing to do with sofware development, I think it's reasonable for Google to not allow using tokens reserved for Antigravity. I don't think there's such a restriction if you pay for the API out of pocket.
Then maybe they should charge for that instead of banning accounts?
Google decided on their own business plan without any guns to their backs. If they decide to create a plan that is subsidized that's entirely on them.
How can Claws users miss this?
What Google could have done better: obviously implement rate throttling on API calls authenticated through the Gemini AI Pro $20/month accounts. (I thought they did this, buy apparently not?) Google tries hard to get people to get API keys, which is what I do, and there seems to be a very large free tier on API calls before my credit card gets hit every month.
What a wonderful way to stop people from using your LLM.
All these AI companies trying to get everyone to be locked into their toolchains is just hilariously short sighted. Particularly for dev tools. It's the sure path to get devs to hate your product.
And for what? The devs are already paying a pretty penny to use your LLM. Why do you also need to force them to using your toolkit?
This isn't a sudden change, either: they were always up-front that subscriptions are for their own clients/apps, and API is for external clients. They don't document the internal client API/auth (people extracted it).
I think a more valid complaint might be "The API costs too much" if you prefer alternative clients. But all providers are quite short on compute at the moment from what I hear, and they're likely prioritising what they subsidise.
Not saying it's right. But it's also not exactly a secret that they are all taking VERY heavy losses even with pricey subscriptions.
It's okay to be annoyed at being caught, but honestly the deer in the headlights bit is a bit ridiculous.
If you want to use an API, pay for the API option. Or run your own models.
Because of their large footprint in so many areas, it is wise to greatly (re)consider expansion in the ways that you rely on them.
Next I tried using the Antigravity Gemini plan through OpenCode (I guess also a bannable offense?) and the first request used up my limit for the week.
What the hell do you expect? To get paid for using other people's tools on Google's servers?
I haven't tried Antigravity but I remember on release it had huge UX issues. Is this product just not ready for primetime?
BTW, I tend to only use Google for services I pay for (YouTube+, APIs, Gemini Plus, sometimes GCP).
This "zero tolerance" policy is just absurdly mega-goliath out of touch with the world. The sort of soulless brain dead corporatism that absolutely does not think for even a single millisecond about its decisions, that doesn't care about anything other than reducing customer support or complexity, no matter what the cost.
Kicking people off their accounts for this is Google being willing to cause enormous untoward damage. With basically not even the faintest willingness to try to correct. Gobsmacking vicious indifference, ok with suffering.
You are doing groundbreaking new and untested stuff with Claw? Do not use your main account. You want to access your main account's data? Sure, allow it via OAUTH/whatever possible way.
Have separate accounts, people. You don't want one product groups decision in those large SaaS corps to impact everything else.
Getting through to customer support was impossible.
5 years later I tried to get my account opened up, filled out some forms, and by some miracle it was.
My biggest takeaway from this (other than enabling 2FA) was that it is probably easier to get ahold of the scammers that control your account, than to get ahold of actual human customer support at google / alphabet.
1) Open Claw has a Google OAuth client id that users are signing in with. (This seems unlikely because why would Google have approved the client or not banned it)
2) Users are creating their own OAuth client id for signing themselves into Open Claw. (Again, why would these clients be able to use APIs Google doesn't want them to?)
3) Users are taking a token minted with the Antigravity client and using it in Open Claw to call "private" APIs.
Assuming it's #3, how is that physically accomplished? And then how does Google figure out it happened?
Everything just guesswork, but I don't think it is too hard to figure out whether it is Antigravity calling the APIs or any Claw.
So if I ask Google's AI studio the wrong question, I might get my G-drive, Gmail, API access, Play store, YouTube channel, "login with Google" tokens, and more all ripped away instantly with no recourse?
No thanks
As a consumer, you're better served by using services from companies earlier in that lifecycle, where value accrues to you, and that's not Google, and likely not many other big providers.
When those newer companies turn, you switch. Do not allow yourself to get locked into an ecosystem. It's hard work, but it will pay dividends in the long run.
Gemini Chat: ChatGPT
Gemini CLI: Claude Code
Antigravity: Cursor
Nano banana: Midjourney
Subscription API ban: copied Anthropic
NotebookLM seems to be the only exception, or it could be an acquisition.
Subscription API ban could be part of a larger strategy because of OpenClaw’s association with OpenAI and Google will not be able to copy OpenClaw Personal Assistant model due to the security implications.
Pay as you go through API pricing is one of the easiest ways to drastically reduce mass adoption of a product. Pay per month works on consumption patterns where 80% of the users will barely use the product to compensate for the other 10 or 20% power users.
I mean it's fair, just should have been documented properly and the possibility to use Gemini through OAuth restricted with proper scope instead of saying you broke the ToS we ban your 350$/ month account.
Either stick to first party products or pay for API use.
The apparent shock around this sort of thing always feels like cope for the fact that we (myself included) understand the power imbalance between Google and its customers but don't want to admit it.
There's plenty of evidence at this point, and I feel like we should be using that emotional energy to actually do something about it (like switching providers for critical personal services, for example).
That said, I assume that (1) their long-term goal is to create cheaper-to-serve models that fit within their pricing targets, and use the (temporarily) subsidized subscriptions to find the features and costs that best serve the market. Maybe even while capturing more margin on the API in comparison (eg keep API prices high while lowering cost to serve a token). I've largely stopped using Opus, and sometimes even chose to use Haiku, because the cheaper models are fast and usually serves my needs. It's very possible to work all-day and barely hit the usage limits with Haiku on the $20/mo option. Long term, that could be profitable outright.
And (2) subscriptions with lower SLOs than API calls have the potential to provide "infill" usage for high fixed-cost GPUs as an alternative to idling, similar to their batch APIs. I'd believe that overnight usage limits could/should be higher than during California work-hours. I assume most big providers have pre-paid fixed cost servers, so pumping more tokens through an otherwise idle GPU is "free". They can also do a lot more cost-optimization behind the scenes, such as prompt caching, to reduce the cost of tokens.
I feel like this game is just a hot potato, can you get retail to hold the bag game
Kimi K2.5 is the best one, but it's still not at the level of what Anthropic released with opus 4.5.
You say this, but I guarantee that when they do offer a plan similar to Google/Anthropic's dedicated coding "unlimited" subscription, they will do the exact same thing. Maybe they will let OpenClaw in as a first party because of their partnership with the creator.
Race to burn as much cash as possible in hopes that the other goes bankrupt first?
These models aren't profitable at the fixed subscription tiers.
Regardless, I thought it was pretty obvious that things like OpenClaw require an API account, and not a subsidized monthly plan.
API usage can get very high for automatic operations, especially with apps like Kilo/Roo/Cline, and now with OpenCode/OpenClaw. I often blast through $10-20 in a single day of just regular OpenCode usage through OpenRouter
If I could pay a subscription and get near unlimited use (with rate limits), of course I'd do that, but not like this. I'm pretty sure Antigravity has ToU somewhere that indicates it's only allowed for use in Antigravity and nowhere else, since I've seen other threads on this happening: https://github.com/jenslys/opencode-gemini-auth/issues/50
But they're not near unlimited though. They're just hidden limits.
Edit: maybe it's not the whole account? https://news.ycombinator.com/item?id=47116330
I analyzed 6k HTTP requests on the Pro account, 23% of those were hit with 429s. (Though not from Gemini-CLI, but from my own agent using code assist). The gemini-cli has a default retry backoff of 5s. That's verifiable in code, and it's a lot.
I dont touch the anti-gravity endpoint, unlike code-assist, it's clear that they are subsidizing that for user acquisition on that tool. So perhaps it's ok for them to ban users form it.
I like their models, but they also degrade. It's quite easy to see when the models are 'smart' and capacity is available, and when they are 'stupid'. They likely clamp thinking when they are capacity strapped.
Yes the models are smart, but you really cant "build things" despite the marketing if you actively beat back your users for trying. I spent a decade at Google, and it's sad to see how they are executing here, despite having solid models in gemini-3-flash and gemini-3.1
I think this is the most important takeaway from this thread and at some point, this will end up biting Google and Anthropic back.
OpenAI seems to have realized this and is actively trying to do the opposite. They welcomed OpenCode the same day Anthropic banned them, X is full of tweets of people saying codex $20 plan is more generous than Anthropic's $200 etc.
If you told me this story a year ago without naming companies, I would tell you it's OpenAI banning people and Google burning cash to win the race.
And it's not like their models are winning any awards in the community either.
They also actively employ dark strategies in cooperation with CIA and who knows when they will pull the rug under you again.
Do you really trust a foundational rotten group of people who avoid accountability?
The OpenCode plugin (8.7k stars btw!) even advertises "Multi-account support — add multiple Google accounts, auto-rotates when rate-limited"[1]
[1] https://github.com/NoeFabris/opencode-antigravity-auth/blob/...
I had buyers remorse when the first hour or two I kept getting rate limited on GLM5, but since then i've not had a single rate limit and I am using it very heavily.
Suddenly instead of writing the code you asked for it would give some generic bullet points telling you to find a library to do what you asked for and read the documentation.
In this case, a the difference in context cache hit rate between openclaw and antigravity.
For example if openclaw starts every message with the current time hh:mm:ss at the top of the context window, followed by the full convo history, it would have a cache hit rate if ~0. Simply moving the updated time to each new message incrementally would increase hit rate to over 90%. Idk if openclaw does this but there’s many many optimizations like this. And worse, thrashing the cache has non linear effects on the server as more and more users’ cached contexts get evicted from cache due to high cardinality. The cost to serve difference could be >10x.
Google is the furthest behind on coding agent adoption and has all the incentives to allow off policy use to grow demand. But it would probably be better to design their own optimized openclaw and serve that for free than let any unoptimized requests in.
While it's sort of the same thing, I think it's much more a symptom of not enough compute vs some 'dump cheap tokens' on the market strategy.
One related thought I had was that given OpenAI is the only one _not_ doing this of the big3, it probably indicates they have a lot more spare compute.
It doesn't make sense to me that given the absolutely brutal competition any of these companies would block use of 3rd party apps unless they had to. They clearly have enough cash, so I don't think it's about money - I think it's that an indicator that Google and Anthropic are really struggling with keeping up with demand. Given Anthropics reliability issues last week this does not surprise me.
I would add though that many are also being caught up in antispam efforts.
I.e. that for every legimate OpenClaw user doing something trivial with their account misusing the sub. There is probably 10x using it to send spam emails and spam comments.
I suspect from googles perspective some of these people are just a rounding error.
That said I use API where I should and the sub in the first party apps. Perhaps I'm too much of a goody two shoes but AI already feels such an overwhelming value prop for me I don't care.
That said I think you're right in that money matters here but I think the subs as they intend people to use them is hugely profitable i.e. the people doing 10 chats per work day and a few in the evening but paying £20 per month.
Or, pessimistically, it could indicate they’re burning cash hoping the subsidized access will eventually result in someone giving them a product idea they can build and resell at a profit.
If they let *claw (or third party coding agents, or whatever) run for six more months and in those months figure out how to sell a safe substitute and then cut off access, maybe it will have been worth it.
Running software has always had a variable cost.
Why should I be surprised if [cloud provider] were upset that I were running a thousand free tier servers? Or utilizing any paid plan at all to somehow effect utilizations far exceeding the clearly documented limitations of my plan?
Using the torrent network protocol on a VPN that doesn't support it, or fork bombing an email server, or using that one popular free video hosting service to host nigh unlimitted arbritrary data, or hosting content that is illegal to the server operator regardless of its legality to me, etc, etc, etc
It's all the same thing: TOS violation.
No one is being forced to use these products without reading and signing the terms of service. In this particular instance, you can even use the free version of the provided service to analyze the terms of service for the paid plan if you were really so lazy.
I really am genuinely confounded as to why people are so regularly surprised that they can't just do whatever they please with proprietary solutions. Like "oh what do you mean I can't lie about the date of my injury in order to get it covered by insurance?".
It's almost like people just assume that everything ever works exactly as they would deam it to (in their benefit), rather than the much more sane assumption that every company is going to be naturally inclined to cater to their own benefit before the users'.
No one would think this is unreasonable. You're not paying for unlimited food forever, you're paying for all you can eat in the restaurant right there.
They all have amounts defined in their service agreements of how much you can eat and in what intervals.
A buffet is saying "pay $X to eat food one plate at a time [up to 100 lbs of food]", and you show up and start shoveling the food into your bag. Does not really matter if we remove the 100lbs part.
Could you technically eat the same amount of food one plate a time? Sure. But if everyone does this, $X needs to be significantly more: even for the people who eat one plate at a time.
-
You could also argue they're playing a mean trick and deceiving people because technically someone could eat the same amount of food 1 plate at a time...
But they priced $X based on how much the average person can eat, not how much food they can carry in their arms. If the limits are so high that people don't leave hungry eating 1 plate at a time, it still seems like a fair deal.
I'm not exactly the type to jump for joy at siding with a corporation, but I really don't get why people are in a hurry to ruin a good thing.
Seems like you're okay with honoring the terms of service, then? Because the client you can use is also in the terms of service.
gemini-cli, claude-code, codex etc, they ALL have a -p flag or equivalent, which is non-interactive IO interface for their LLM inference.
If I wire my tooling (or openclaw) to use the -p flag (or equivalents), is that allowed?
Okay, maybe they get rid of the -p flag and I have to use an interactive session. I can then just use OS IO tooling to wire OpenClaw with their cli. Is that allowed?
How does sending requests directly to the endpoints that their CLI is communicating with suddenly make their subsidized plans expensive? Is it because now I can actually use my 100% quota? If that's so, does it mean their products are such that their profitability stands on people not using them?
What is even going on?
Specifically all optimize caching.
The indirect answer is for everyone using third party tools to play about there are 10x using it to spam or malicious use cases hammering their backend far cheaper than if it was by API.
These people are the false positives in this situation, but whether Google or Claude care is unlikely. They're happy to ban you and expect you to sign up for the API.
This has always been a worry when you use a service like Google.
if i understand correctly, they even have a wrapper around it to make it easier to use: the Claude Agent SDK
the thing that's disallowed is pretending you're the claude binary, logging in through OAuth
in other words, if you use some product thats not Claude Code, and your browser opens asking you to "give Claude Code access to your account", you're in hot water
as for how they detect it: they say they use heuristics and usage patterns. if something falls wildly out of the distribution it's a ban.
my take is that the problem is not the means of detection. that's fine and seems to work well. the problem is that its an instant outright ban. they should give you a couple warning emails, then a timeout, etc.
cache hit rate alone would stand out
Reasonable progression: warning email → quota throttle → AI Pro subscription suspended → Google account suspended.
They skipped to step 4 on a first offense, paid account, no appeal. That's not a terms enforcement system, that's a hostage situation. "Comply or lose your digital life."
The real lesson isn't "don't use OpenClaw." It's: never let one company own your primary identity infrastructure.
If it makes you feel any better, some google employees have their personal accounts banned too (only Gemini access, not the whole account) for running opeclaw, and also have a hard time getting their account reinstated.
The financial costs would clearly be ruinous.
Comments section here and on related news from Anthropic seems to be centered around the idea that the reason for these bans is that it burns tokens quickly, while their plans are subsidized. What changes with the -p flag? You're just using cli instead of HTTP.
Are the metrics from their cli more valuable than the treasure trove of prompt data that passes through to them either way that justifies this PR?
It's embarrassingly trivial, IMO - compare what antigravity reports for token to what the backend reports for token usage for that user.
Are they banning their core offering? Are Ralph' loops also banned for building software? Because I can drain my quota with a simple bash loop faster than any OpenClaw instance.
What an awful way to lose trust, locking out their users but billing them all the same.
[1] https://blog.google/innovation-and-ai/technology/developers-...
A while back I made completely separate Google accounts for YouTube and Maps just so my longstanding Gmail account wouldn't get banned if the system somehow detected that my Youtube account for example breached Google's TOS.
I bet you that if they ban one they ban the other too
the only safe way is to get your important data out of Google entirely
after manifest v3's announcement, I de-googled: gmail, chrome, search, google cloud, photos, family on android phones
2 years later, it's all gone, except youtube
and if they ban that I don't care
Related: I've had a suspicion that, if you have an Apple or Google app developer account through a company (in your name and recovery phone number, but company email address)... and you leave the company... you'd better hope that someone at the company doesn't then use the account to do something sketchy or rule-breaking.
Someone inheriting the account is a very real possibility, given motive (people can be lazy about figuring out how to set up the account for another developer, or not want to pay another fee), and opportunity (professionalism norm is to preserve all passwords/secrets in a way that is accessible to the company).
Other ways of linking an account, such as having both logged in on the same phone, don't put you at risk.
It’s free so I’m not going to complain, but for something as vital as an e-mail, I’m willing to pay for a service to have some peace of mind.
Source: I actually read them. Yes, personally. I didn't even have an LLM summarize them. I know, I'm practically a luddite.
My "new" mail provider fetches messages from Gmail to create a unified inbox, which helped with the transition. Today, I'm thinking of shutting this off given the volume of misaddressed e-mail and spam that arrives via Gmail.
https://github.com/jenslys/opencode-gemini-auth/issues/50
https://github.com/NoeFabris/opencode-antigravity-auth/issue...
https://github.com/jenslys/opencode-gemini-auth/issues/50
Some additional discussion on Reddit: https://old.reddit.com/r/google_antigravity/comments/1r2hnn8...
Their API usage isn't included in these plans, although under the hood open-gravity uses the API.
People have been using the API auth credential intended for anti-gravity with open claw, presumably causing a significant amount of use and have been caught.
The Google admin tools and process haven’t quite been able to cope with this situation and people have been overly banned with poor information sent to the them.
I don’t think either OpenAI or Anthropic any API use in their ‘pro’ plans either?
This reminds me of the customers of “unlimited broadband” of yesteryear getting throttled or banned for running Tor servers.
I can’t recall any success story of Google’s support team or process coping with a consumer’s situation, many have been posted here. this isn’t a new outcome, just a new cause
I do want to understand what’s happening with the $250/mo fees of users caught in this. will it be automatically cancelled at some point?
it seems like the main problem with OpenCode and OpenClaw is that they call the API directly bypassing the website
my approach is browser automation, its technically against the ToS too but there's default mechanisms to avoid unintentional mass spam.
I think what pissed off Google and Anthropic was that people were running through multiple accounts from OpenCode and ruined it for everybody else
Sounds like the same here. Are they against to ToS in either case?
The main point still stands, google is part of a duopoly that runs the world. You can't be a functional member of society without them. They're like a public utility and plays too big of a role in people's life to take decisions based on unknown internal policies. They're long overdue for a government intervention or for splitting up.
Usually they'll try to hide the monopoly/tying to avoid this. What's interesting is that they don't seem to be trying.
It's not the same thing but it does remind me of [1].
[1] https://en.wikipedia.org/wiki/United_States_v._Microsoft_Cor....
Can we start saying it in unison to legislators and the press? Please?
If you're in the EU, do your part too.
This company taxes the URL bar. It owns 92% of them and turns trademarks they don't own into forced bidding wars. There's no way to access any brand without paying Google extortion fees.
This company removed AdBlock.
This company controls 50% of mobile - the most important device category and devices we own and pay for - and now they're removing our ability to use them as we please. More taxation, more Google services, every app and search through the Google troll toll. You can't even order from a restaurant anymore without one of these things and Google lords over it.
They own your digital life. They own infrastructure. They own discovery. They own every touch point.
They are too big.
Anthropic and OpenAI are having to pay out the nose for 60% of users to even access them, meanwhile Google sings "lalalala" and forced their AI products onto users at no cost.
Break them up now.
Do it horizontally, not vertically: instead of splitting off Chrome and Search and YouTube, create Google A, Google B, Google C ... Make them split all the same pieces and make them all compete with each other.
That is fair for the consumer. That is fair for competition.
That is the most capitalistic friendly thing to do. Because right now Google is an invasive species in every market destroying the entire competitive ecology.
I have read several blog posts from people describing how frustrating it is to have an account locked. Because Google, like many large companies, provides little to no effective support, the only thing that seemed to work was getting a post to trend on Hacker News so that someone inside Google noticed and intervened to resolve it.
No bank closes your checking account because you used your debit card at a competitor's ATM.
The offense and the penalty are in completely different weight classes. That's what makes this indefensible regardless of whether the policy itself is legitimate.
But that's still not enough. I can't easily reconstruct this data in a way that will be usable to me, not without having something like Gemini build a UI for me. Oh wait.
They got rid of their "Don't be evil" motto for a reason, after all.
could you elaborate on why this is true? I can't think of any.
>Can you begin to imagine losing access to all your emails, accounts, every photo you ever took? Because what they didn't like how you used one unrelated product tied to your account?
What are you talking about? He didn't lose access to Google, in fact, he is using his Google account to make the post. He lost access to the service they are claiming that he is misusing.
Luckily, it sounds like reality was his Gemini account was banned. Much more reasonable.
Just the 1000th instance of disgusting behavior by US big tech.
For example, basically every first party agent harness aggressively caches the input tokens to optimise inference, something that third party harnesses often disgregard, or are fundamentally incompatible with as they switch agents for subtasks and the like.
To extend this use case though, how much do poeple expect to be able to use the internal API's of the apps they subscribe to?
If I buy an Uber One subscription, am I then justified reverse engineering the gazeteer API from the app and reusing it in other apps I use? What about the speech to text API MS Teams must use for transcribing meetings as part of a business standard subscription?
I think these are obvious and emphatic breaches that no reasonable person would expect to be justified in, maybe miffed if your clever hack gets banned, but being banned would be considered fair play.
I fail to see the distinction.
For example the EU DNA (entirely not enough but in the right direction).
We should have the right to use our accounts as we wish.
It's the right-to-repair applied to software.
Abuse is something else entirely.
I just assumed it was a warning about security breaches, not business plan breaches.
https://github.com/google-gemini/gemini-cli/issues/19532
They are not serious. I only keep the "AI Pro" sub because it comes with a couple terabytes of Drive storage for the family.
Anyways, Google, nobody wants to use your bad VSCode fork. I want to use my own tools, and use your model where it makes sense as part of my own workflow.
YouTube is also full of huge content creators, people who make Google tons of money, that complain about the Byzantine and opaque rules they have to dance around to maintain their livelihood and fan base
Google fears their giant userbases so they act with zero regard for communication and transparency because of the small chance it’d help the abusers
When people grab OAuth tokens for replay in OpenClaw, they are essentially doing at the user level what malicious skills do at the agent level — bypassing intended access controls because the system has no way to distinguish legitimate from illegitimate use.
This is the same pattern showing up everywhere: - 312,000 instances on Shodan with no auth (CyberSecurityNews) - 40,000+ exposed instances (SecurityScorecard this week) - 824+ malicious skills in ClawHub - Infostealers now grabbing entire agent identities (Hudson Rock)
The common thread: agents operate with broad, undifferentiated access. No permission tiers, no credential isolation, no audit trail.
Until the ecosystem adds proper trust layers at both the platform level (what Google is clumsily trying to do here) and the host level (monitoring what agents actually do with their access), this cat-and-mouse will continue.
No worries, the AI companites thought ahead - by sending GPU, RAM, and now even harddrive prices through the roof, you won't have a computer to run a local model.
Maybe if you have the tens of thousands worth of hardware required to run models like DeepSeek, GLM or Kimi locally. Most people don't, though.
And as far as I understand, the main contingent of HN is engineers, programmers, and even me, who works in a country (Russia) where the salary of an engineer is just tiny compared to Europe or the United States, it was not difficult to buy powerful enough equipment to run most large local models, train lora, then programmers who earn income in six-digit dollars it's even easier to do this.
https://news.ycombinator.com/item?id=47073097
I'd like to add, that's "priceless" for "them" and not for you.
The real issue is that we're building entire development workflows on subsidized inference that was never priced to be used this way.
OpenClaw burns tokens at a rate these $200/month plans were never designed for.
The fix isn't nicer ban policies, it's either honest API pricing or local models good enough for the job.
The 0.5B-3B parameter range is already surprisingly capable for code analysis tasks.
That's where this is heading whether Google likes it or not.
1. Can a company change their ToS to clarify that you can't "hack" their Oauth for other tools -- Yes, no question
2. Should they enforce the ToS, absolutely
The elephant in the room is Google has no support infrastructure and setup no notice drip campaign before they started banning out-right.
They could've easily rate-limited or even blocked requests authed from apps outside Anti-gravity, but banning entire accounts is pretty ridiculous. It'll just lose them very eager AI enthusiasts who are the audience they NEED to grow their new experiments.
It's bad business and not in their best long-term interests. Big fail. This is the way a startup may act because they're going broke on traffic -- not Google.
all hosted by companies so huge they consider your $200/month to be an annoyance
rather than something valuable
I bet Google is thankful that anthropic took one for the team by going first.
Also if it wasn’t for Chinese providers we’d basically already be in triopoly.
Perplexity had a ban wave this weekend too
They're literally all just a single open source model away from effectively becoming trillion dollar paperweights.
Meanwhile the rising popularity of Claws creates a yet untapped new market segment where users spend significant tokens.
A „soft“ migration of users by explaining to them how the API works, how to pay and how to change from OAuth would be way smarter.
The way this plays out right now is that current Claws users are massively penalized by being suspended indefinitely and new users will think twice. And we can expect a solid PR disaster / Streisand effect for the „poor“ model providers like OpenAI or Anthropic.
Commercially choosing the soft route by warning and throttling will be way smarter and possibly generate more long term revenue
Google's response is to restrict access — a blunt instrument that punishes legitimate users because they have no way to verify which agents were behaving correctly and which weren't.
The real fix isn't restrictions, but cryptographic behavioral commitments — agents declare what they'll do before execution, and any third party can verify compliance after. We don't need gatekeepers. We need verification.
I've been building this: https://github.com/agbusiness195/NOBULEX
For almost a trillion-dollar company, this is the worst customer experience I've ever seen. Departments sending poor guy to each other like a hot potato. Huge aura loss.
The GH issue trackers were full of people bitching and moaning about it. I think it might be a worse thing to alienate your users who use your product in the intended way - through Google's tooling.
But I agree the 0 strike rule seems really excessive.
It is also a possible scenario that a single individual sets up 10+ AI Pro subscriptions to blast through tokens like crazy - not sure how the economics of the daily allowances compare to the API pricing here.
He was right.
The only reason the subs are worth it to them, is to get you into their toolchain. It sucks but inevitable
They could have easily just blocked the Gemini / Antigravity use and and/or sent a "final warning" kind of email beforehand.
It looks like its been found. The irony is, these model providers are now saying : "not like that!"
1) Switching between LLM API:s is incredibly easy if you are not concerned with differences in personality. As the models get better, it is less important to pick the best one.
2) The products built to bundle the API with a user experience are difficult to build on a level that outclasses open source alternatives.
3) Building an understanding of the user to increase the product value over time and create stickiness is effective, but imho less effective over time as time passes and the user changes. For example, I suspect that these adaptations have a hard time to unlearn things that are no longer true. Learning about the user opaquely is less useful to the user and doing it overtly makes it easier to take the learnings and go. (Besides, it is probably not legal under the GDPR to not let the user export the learnings and take them to another provider.)
Taken together, the moat becomes quite shallow. I see why they aggressively ban any tools demonstrating when open alternatives are in fact better than their own walled gardens.
edit: readability.
Obviously not with Napster, but they will close your account for piracy.
I've been a pay-as-you-go API user from the beginning, carefully managing my context and usage while also leveraging cheaper, open alternatives to those overpriced "SOTA" models. I'm paying ~6 USD a month and I'm using it quite a lot.
lol, funny that this time they can't say "malicious users from china!"
Don't want to risk losing access to your Google Photos, Drive, Gmail, etc.
Although from a brief read, it seems the user still has access to other Google services.
Don't want to risk loosing access to your Google Photos, Drives, Gmail, etc.
Although at a brief read, it seems the user still have access to other Google services.
Exactly my kind of humor.
I would highly encourage you to not only stop using Antigravity oAuth for OpenClaw, but to use Antigravity with a side account or stop using it altogether. Is using Antigravity worth losing your main account or getting it banned for using paid services (for extra storage, YouTube premium, etc). Even side accounts are risky since in the post thread people are saying Google applied the ban to all their accounts.
People accounts shouldn't be used by bots. That's what service accounts are for.
Who in their right might thinks it's a good idea to use something they pay a NAMED SUBCRIPTION FOR as a secondary engine in another tool?
Like, it's hilarious some of you guys think it's OC's fault for this.
It's open source software, with extensive documentation that anything you do with it being at your own risk.
It's no one's fault but the people plugging their oauth into this thing like complete MORONS lol
I just use Gemini 3.1 Pro (High) on Antigravity.
GPT-5.3-Codex is the best on OpenClaw.
Sonnet 4.6 uses 50x more session tokens than GPT-5.3-Codex on OpenClaw.
It feels like a classic “drug dealer” model to me. Get everyone hooked with cheap access, then raise prices later. Unless there’s a major breakthrough in the underlying technology, I don’t see how a significant price increase isn’t inevitable once adoption is locked in.
Given the API prices for open weights models of similar size are 5-10x less than the frontier models the APIs are very profitable on a pure unit economics approach. I strongly suspect they make money off their monthly plans as well.
Yes, AI can do some incredible things. But we’re also running full speed into an ecosystem controlled by 2 or 3 major companies. Running at a loss. A reality check is coming.
It’s not a technology problem. It’s an economic problem. People are too busy looking at the tech to notice.
Yes there is mad dash by Google, Oracle, Microsoft, Meta, and China not to cede their position to each other - it actually isn't about who will buy or pay for the service its more of a Business Strategic position to obtain critical mass in a new market using their massive reserve of cash. The users right now are insignificant to their goal - they probably aren't even given a second thought.
We aren't, though. They think we are :-/
The reality is that tokens are the second-lowest value link in the AI value-chain (the lowest-value item being electricity).
These providers are operating low down in the value chain; they are trying to sell a fungible, easy replaceable and (if hardware price trends is any indication) easily self-hostable.
They have no secret sauce, no moat. If they jack up the prices, their users will simply move to the next provider, and repeat ad nauseum as long as VCs want to subsidise in the hope of a landgrab.
1) Stand up a service 2) ??? 3) Profit
??? - worry about any substantial support later
What later? You still can't get support from Google beyond their "community forum" with their condescending volunteer "diamond product experts" who have no power to help with anything account related.
Normally there would be a normal, well adjusted person in the room to remind them that "zero tolerance" policies for situations that can happen by mistake is silly
If you want to real use these things get an API key and pay the true marginal cost of your compute like a grown up.
Oh, maybe not, they did it in the name of "terms of service abuse" and "risk assessment".
Thus it would be far better if we can just have SOTA open weight model to run OpenClaw/Clawdbot/Molt at least we are under control. And as you see the two Chinese models I mentioned are indeed open weight, albeit taking atrocious amount of resource to really self host, and you probably need to have abliterations to remove their political guardrails.
Sigh. We can't have great things with those big tech corpos and CCP politics. Big question: Why has this world gone to shit lately.
I hate when companies say "unable" when they mean "unwilling". Google's statement is a lie because it's neither impossible nor illegal for them to change or rescind their policy, or give users an exception to it.
Effectively.
This basically makes it a deal breaker to use google ai stuff because you can be royally fucked by one ban.
Price out competitors. Abuse your newfound dominance.
It's the big tech playbook.
I don't think it's going to work this time.
Tools like OpenClaw are an existential threat precisely because it allows the user control over their experience. The value in it cannot be captured by a monopoly.
LLMs don't seem to be a very good moat. At the same time, the software moat is eroding due to those same LLMs.
Telecom tech killed telecom dominance.
With some luck, Google tech will kill Google dominance.
Are they betting on their software, not their LLM deciding if they survive or not if competitive open source model is dropped? Oh boy, the market is going to have some fun times when realization hits.
TIL it's "unfair" to sell a product for a particular purpose and offer subsidised rates to build a customer base. Different planet.
These companies keep telling you that you own nothing, they change their TOS without informing you, they collect everything they can from you and yet, you spend $249/mo for their service.
I mean......
You really think Google wants to subsidize compute so that you can organize your freaking calendar you morons? Sounds like a great use of a data center where you could just click accept invite. Oh, you can't reply to text messages, so you trust AI to do it now. Wow! You must be the laziest piece of s** on the planet. Oh email's too much for you? Let me tell you what inbox zero as a mandatory process looks like when you wake up with 150 emails on average every single day over a a 7-year period and you handle every single one every single day before you leave the office with zero unread and zero pending reply. You get really good at making sure every single customer is handled. When customer service is not optional and your service level agreement is that you answer customers 24/7 365 you do it immediately without question and everything is solved before the lights are turned off and if something goes wrong at any time of the day that phone's getting picked up ring one and the problem is being solved before the line is hung up or there's an escalation to management and it is handled on the spot. Some of you are a little soft and don't actually believe in putting in the work or putting yourself in positions that will leave you slightly inconvenienced because it would be way too much to ask for you to stay 3 hours after work if that's what it takes to build a billion dollar company. I really hope you enjoy dinner with your family every single night at 4:59 p.m. Sharp while you get smoked by people that are actually staying at the office. So now that the only two options you think you have are paying someone for their large language model because you are poorly researched and don't know how to build your own system taking thousands of dollars and buying something with over a terabyte of RAM that spits out a hundred tokens a second. Maybe you can do that 10 times to get a thousand tokens a second if you really want to drop 100 Grand on new macbooks. That's about a quarter of the speed of meta which offers infinite free compute if you cleared their wait list as a developer(6+ month waitlist for consideration).If you don't have free compute from meta, I feel bad for you because they were giving 3,000 requests per minute until openclaw came out and that's only 10 requests per a minute because they got real tired real quick of these 24/7 agents taken up all the compute to do. Jack diddly s** I will tell you that. Claude grok meta Google and almost any frontier model you haven't heard of will give you infinite free compute if you are building products that have never been seen before. I'm not sure what Peter was doing spending 20,000 a month on compute. Does anyone have a figure on how many credits he burned? Cuz I'm in the tens of billions and my compute spend is $0 over 18 months. It's really interesting what happens to your account when you feed it, new data, new solutions and try to build theoretical software that is not currently possible with what is available today and then you come back when the new model comes out. They welcome you with open arms and they don't charge you to use it and they do a lot of heavy lifting without much of a cap. The point of this is to you mention that you do not need millions, probably even hundreds of thousands of parameters for your basic tasks that you are too lazy to handle yourself. I honestly am not so sure what any of you are doing with open claw when cursor builds much better software. In my professional opinion, the most effective way to utilize open claw is by building your own decision tree or something similar that has a pretty rigid process and follows exactly what it should do without thinking. You guys would be amazed to know that you can build a fully functional model that does everything you need and completes every task a customer will ask for with a 12 KB file it runs with less than 15% of your total compute on four cores and takes less than 2 GB of RAM on a web server. It provides instant response with no processing delay. It knows exactly what the customer is asking and matches it up with the correct response. It is able to process images using data sets which are also very lightweight because they are specific to your business. So next time you try to set up openclaw, ask whatever AI you're using just to rip out the apis that comes with and build your own model which you will host on your local system server. You might need to ask it to refactor for firebase or whoever else you're going to be hosting with. Go ahead and keep paying digitalocean $6 a month for the worst VM I've ever seen. That's a great investment and their current best practices go against the current best practices that open claw recommends, so I would not recommend any third party providers, even if they are worth $5 billion because they do not maintain as fast as openclaw ships. Any questions I'm available but I probably don't want to help you unless you're paying me a lot of money because I and I'm kind of a big deal in case you can't tell.
It is imperative that open source wins this battle. Not these evil megacorps and their substandard tools.
Are Google engineers so inept as to not be able to integrate technical measures against oc use? Do they think people using these plugins know the mechanisms used? And after all that they have the nerve to ban you from using their own products (AG). Ridiculous company.
At the end of the day we know that these tools are massively subsidised and they do not reflect the real cost of usage. It is a fair-use model at best and the goal is to capture as market share as possible.
I am a no defender of Google and I've been burned many times by Google as well but I kind of get it?
That being said, you don't really need to use your gemini subscription in openclaw. You can use gemini directly the way it was intended and rip the benefits of the subsidised plan.
I developed an open source tool called Pantalk which sits as a background daemon and exposes many of the communication channels you want as a standard CLI which gemini can use directly. All you need is just some SKILL.md files to describe where things are at and you are good to go. You have openclaw without openclaw and still within TOS.
The project is hosted at: https://github.com/pantalk/pantalk
Or Microsoft banning you from O365 for not using their browser, or the correct monitor, or the correct mouse or.....
Are you telling me a bunch of people on Twitter and HN are full of shit?
But state of the art models are not free. GLM 5 and Kimi K2.5 are both open-source and they are much better models than the ones we used to pay for a year ago. Now we get them for free. This is certainly having an effect on all model providers which either need to adjust to new market realities or risk to loose market share and we know which thing they are not going to do.
This is a critical question because the answer is different for Google vs. Anthropic, and getting it wrong with Anthropic can actually get your account banned.
Here is the reality of the situation based on current Terms of Service and recent community reports.
1. Google (Gemini Ultra + gemini-cli)
Verdict: Safe (Authorized Feature)
Google explicitly built the gemini-cli bridge to allow Ultra subscribers to use their plan programmatically. This is not a "hack" or a gray-area wrapper; it is an official feature.
• Why it's okay: You are authenticating via gcloud or the official CLI login flow. Google tracks this usage against your specific "Agent" quotas (currently ~200 agent requests/day for Ultra users).
• The Limit: As long as you are using the official gemini-cli as the bridge, you are compliant.
• The Risk: If you use a different unofficial script that scrapes the gemini.google.com web interface (simulating a browser) rather than using the official CLI, you risk a ban for "scraping." But since you are using gemini-cli, you are in the clear.In some sense, hallucinations as a problem have been solved already - their rate of occurrence seems much lower than that of people failing to read what is written instead of what they hoped it would be.