Isn't the reason companies are doing this because they're offering tokens at a discount, provided they're spent through their tooling?

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.

Oh man.

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?

No, this is hilarious: company that rams their AI down your throat at every opportunity then turns around and shuts down your account because you actually use their AI... there is no limit to the idiocy around Google's AI roll-out. I wished I could donate the AI credits that I'm paying for (thanks Google for that price increase for a product I never chose to buy) to the people that need them more.

Yikes!! This is really unfortunate, because Google's models seem very good but there's no way I'm using a google service for this kind of thing with those policies. I don't even want to run OpenClaw, but that's scary! Plus, I have my google account tied to authenticating so many things that if my account were to be suspended or something that would be a nightmare.

I haven't tried Antigravity but I remember on release it had huge UX issues. Is this product just not ready for primetime?

How about giving the user a big warning to not do that and then block the account if the user continues. This total blocks are crazy. Especially for people who use their Google account for 20+ years or something.

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?

I cannot de-Google fast enough.

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

I [ctrl+f]'d for this comment in the thread linked above, and couldn't find it. May I ask where you saw that?

Google is a copycat in AI products.

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.

Maybe the ban is overstepping but I still continue to not understand the issue. Rarely in the history of APIs has a commercial company wanted folks to use the private APIs.

I'd assume API usage through tokens vs. OAuth are rate limited differently? I don't actually see hard numbers for Antigravity model rate limits on their website so guessing this is the case.

Basically Google is saying: You can't use Gemini with OAuth on other products than Google products (Anti Gravity).

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.

cant you just wrap it though?

swap out the direct api call with a call to gemini cli?

It’s protectionism. These corporations are staying big because of anti competitive practices and capital. They don’t want to let go.

Using Google for anything other than search and email has been a poor choice for a long time.

[flagged]