Live data from Hacker News

Google restricting Google AI Pro/Ultra subscribers for using OpenClaw

discuss.ai.google.dev

331–340 of 752 posts

Re: Google restricting Google AI Pro/Ultra subscribers for using OpenClaw

#331
post #149

I don't understand how this can be enforced without ridiculous levels of false positives. I'm truly baffled. The same with Claude Code situation. 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 h…

claude -p is allowed as far as I'm aware. 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 th…

Is OpenClaw a product though? It's more like a system/framework.

Re: Google restricting Google AI Pro/Ultra subscribers for using OpenClaw

#333

Earlier quoted context omitted.

This obviously cannot be true, otherwise Costco would have been sued to oblivion for “dumping” their rotisserie chickens.

Costco gets to sidestep a lot of regulations because they technically are a private club with paid membership. The US anti-monopoly laws are also unusually weak. In other countries, selling a $7 chicken if it's subsidized by the sale of other goods can indeed be illegal.

[deleted]

Re: Google restricting Google AI Pro/Ultra subscribers for using OpenClaw

#334

So the timeline is basically * 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…

I don't understand step 1. OAuth client applications have to be registered in GCP, right? They have to request specific scopes for specific APIs, and there is a review process before they can be used by the public. Did none of that happen for the Open Claw client? How is it the users' fault for clicking a "Sign in with Google" button? And if there was a mistake, why not ban the whole client?

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?

Re: Google restricting Google AI Pro/Ultra subscribers for using OpenClaw

#337

Earlier quoted context omitted.

[flagged]

Terms of Service that span multiple pages of legalese and require an attorney to parse, for something that is either 'free' or a few $ per month, and can result in loss of service across multiple product lines, AND has binding lopsided arbitration requirements, is not only draconian, it is unconscionable . Look at how messed up this is: Google Attorneys, paid hundreds of $/hour, spending hours and hours putting toget…

This is how I feel when reading my 100 page home owners insurance policy.

Re: Google restricting Google AI Pro/Ultra subscribers for using OpenClaw

#338
post #309

Google's Pro service (no idea about ultra and I have no intention to find out) is riddled with 429s. They have generous quotas for sure, but they really give you very low priority. For example, I still dont have access to Gemini 3.1 from that endpoint. It's completely uncharacteristic of Google. I analyzed 6k HTTP requests on the Pro account, 23% of those were hit with 429s. (Though not from Gemini-CLI, but from my o…

I’ve often suspected these models of getting dumber when the service is under high load. But I’ve never seen actually measured results or proof. Anybody know of real published data here?

Not exactly what you're looking for but https://news.ycombinator.com/item?id=46810282

Re: Google restricting Google AI Pro/Ultra subscribers for using OpenClaw

#339

So the timeline is basically * 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…

It doesn't seem fair at all; though I'm glad to see it's not as bad as I feared (yet?).

> 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.

Re: Google restricting Google AI Pro/Ultra subscribers for using OpenClaw

#340

This is draconian. > 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…

Can you help me understand which of these happened?

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?

Post reply on HN