> to address violations of the Antigravity Terms of Service (ToS), specifically the use of 3rd party tools or proxies to access Antigravity resources and quotas
Translation: Google doesn’t want you using Gemini oauth with openclaw
Addressing Antigravity Bans and Reinstating Access
121–130 of 230 posts
Re: Addressing Antigravity Bans and Reinstating Access
#122Earlier quoted context omitted.
This wasn't due to some random Gemini request. Users were using sketchy antigravity auth plugins to use their antigravity tokens on things like OpenClaw, clearly against ToS. It's great that Google is giving these users a second chance.
The concern is not losing access to some new IDE for operating outside the terms of service. The concern is when you lose access to the IDE, you also lose access to your 20 year old Gmail account. A general problem for Google products is that everything is mixed together.
But that's not what happened.
Re: Addressing Antigravity Bans and Reinstating Access
#123Earlier quoted context omitted.
>I still kinda wish that the subscriptions would just allow you to use the tokens however you wish. I get that they rely on people not using all of their quota. But e.g. with open code it doesn't really matter if I use antigravity or gemini-cli the usage should be about the same. This is almost as realistic as "I wish netflix or youtube allowed me to use VLC to watch their content".
This is almost as realistic as "I wish OpenAI supports using OpenCode with ChatGPT subscription account." Oh, except they do[0]. [0]: https://x.com/thsottiaux/status/2009742187484065881
Yea, there are the last to the party (have they even arrived?), so they are going to have to make some concessions. I wonder if they at rollout will have a third-party subscription token service in addition to their first-party one.
Re: Addressing Antigravity Bans and Reinstating Access
#124Way too risky to use Google services like this tied to your primary account. There’s too much risk of cross damage. Imagine losing access to your Gmail because some Gemini request flags you as an undesirable. The digital death sentence of losing access to your email with a company that notoriously has no way for the average human to contact a human is not worth the risk.
[deleted]
Re: Addressing Antigravity Bans and Reinstating Access
#125The Gemini-CLI situation is poor. They did not communicate that AI Pro or AI Ultra accounts cannot be used with this API broadly earlier. I specifically remember searching for this info. Seeing this made me wonder if I had missed it. Turns out it was added to the TOS 2 days ago - diff https://github.com/google-gemini/gemini-cli/pull/20488/chang... . I'd be happy to stand corrected here. Anti Gravity I understand, the…
I have a Code Assist Standard license to evaluate gemini-cli (and the new models)
To this day I cannot coax the gemini-cli to allow me to use the models they claim you have access to. Enabled all the preview stuff in cloud etc etc.
Still I mostly get 2.5 and rarely get 3 or 3.1 offered.
The gemini-cli repo is a shit show.
I can seem to access the new models using opencode, but am 429 rate limited almost immediately such that its like 5 minutes between calls.
Re: Addressing Antigravity Bans and Reinstating Access
#126Earlier quoted context omitted.
Yes, I have. And it's obvious that restriction was put there for a reason. The most obvious possible reason is that snatching OAuth made it possible for third party tools to utilize subscription to the fullest - like OpenClaw. But these tools, including openclaw, didn't have to snatch the OAuth tokens, they could have used claude code built in headless stdio and consequences for Anthropic would be exactly the same. O…
Before I use time responding, I want to ask again: Did you actually read the website, especially the "Compare the Agent SDK to other Claude tools" section? It answers your question pretty thoroughly.
For the second time, yes. And it's still not clear at what point does a wrapper around claude cli running in headless mode become a 'product' that is going to get my account banned.
My guess is, and others have said this as well in the thread: "when you start utilizing your weekly quotas fully".
But obviously, they can't put "you can't use your weekly allocated quota fully". That would be way too honest and we can't accept that.
Re: Addressing Antigravity Bans and Reinstating Access
#127The Gemini-CLI situation is poor. They did not communicate that AI Pro or AI Ultra accounts cannot be used with this API broadly earlier. I specifically remember searching for this info. Seeing this made me wonder if I had missed it. Turns out it was added to the TOS 2 days ago - diff https://github.com/google-gemini/gemini-cli/pull/20488/chang... . I'd be happy to stand corrected here. Anti Gravity I understand, the…
I have a Code Assist Standard license to evaluate gemini-cli (and the new models) To this day I cannot coax the gemini-cli to allow me to use the models they claim you have access to. Enabled all the preview stuff in cloud etc etc. Still I mostly get 2.5 and rarely get 3 or 3.1 offered. The gemini-cli repo is a shit show. I can seem to access the new models using opencode, but am 429 rate limited almost immediately s…
It takes your query, computes the complexity of the request, and tries to route it to the appropriate model. There is a /manual command i think, to pick the right model.
They mask the 429s well in Gemini-Cli - if an endpoint is rate limited, they try another, or route to another model, etc to keep service availability up.
Your experience on the 429s is consistent with mine - the 429s is the first thing they need to fix. Fix that and they have a solid model at a good price point.
I use my own coding agent (https://github.com/hsaliak/std_slop) and not being able to bring my (now cancelled) AI account with Google to it is a bummer.
I'd still use it with the Code Assist Standard license if the google cloud API subscription allows for it but I have no clarification.
Re: Addressing Antigravity Bans and Reinstating Access
#128Way too risky to use Google services like this tied to your primary account. There’s too much risk of cross damage. Imagine losing access to your Gmail because some Gemini request flags you as an undesirable. The digital death sentence of losing access to your email with a company that notoriously has no way for the average human to contact a human is not worth the risk.
Here’s an idea: run your digital life away from a corporate shitbucket like Google. Don’t run your email there. Plenty of good other options.
Re: Addressing Antigravity Bans and Reinstating Access
#129Earlier quoted context omitted.
This is almost as realistic as "I wish OpenAI supports using OpenCode with ChatGPT subscription account." Oh, except they do[0]. [0]: https://x.com/thsottiaux/status/2009742187484065881
Yea, there are the last to the party (have they even arrived?), so they are going to have to make some concessions. I wonder if they at rollout will have a third-party subscription token service in addition to their first-party one.
> there are the last to the party
Anecdotally, I'm having a very hard time imagining there are more Gemini Cli users than Codex users.
Re: Addressing Antigravity Bans and Reinstating Access
#130Earlier quoted context omitted.
Use a custom domain and don't use google for email. And if you do use your gmail address just forward it and start to transition to something else. With time everything of importance has been transferred.
How do you even pull away from a Gmail address? I'm nearly twenty years into that service. Getting banned would be absolutely devastating...
I just went through all accounts in my password manager, logged in and changed my email. It takes a little while but not that much.