Live data from Hacker News

Addressing Antigravity Bans and Reinstating Access

github.com

171–180 of 230 posts

Re: Addressing Antigravity Bans and Reinstating Access

#171
post #45
post #38

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

buy a domain.

create icloud account.

use their custom domain email setup (free btw) - https://support.apple.com/en-us/102540

Start replacing important account emails with your custom domain.

Every time you get an important email in gmail, login and update.

Bonus: icloud let's you create catch all emails, so you can create many burner emails such as hackernews@mydomain.com

Re: Addressing Antigravity Bans and Reinstating Access

#172
post #83
post #81

Earlier quoted context omitted.

I think the issue is people are using tools in an automated fashion and running up a compute bill for free when they were only meant to be used by humans in a more limited capacity (for companies to gather data on how to improve their products for humans). I think the correct way to use these models in an automated fashion is via the APIs and even then they might also worry about things like abuse/distillation type a…

> I think the issue is people are using tools in an automated fashion But that's the sole reason why all of the tools have headless modes. Headless mode is textbook definition of supporting automation. From gemini docs: [1] > Headless mode allows you to run Gemini CLI programmatically from command line scripts and automation tools without any interactive UI. And claude code: > Use the Agent SDK to run Claude Code pro…

antigravity doesn't have a headless mode and is a separate billing subscription from Gemini API.

Re: Addressing Antigravity Bans and Reinstating Access

#173
post #144

Earlier quoted context omitted.

> the link clearly says that if you are not using the harness provided by Claude for the Agent SDK (such as for making tool calls), you have to use the Client SDK But you just made this up? There's no text on the page that says this. What the linked page does is explain technical differences between Agent SDK and Client SDK, and Agent SDK and cli (Agent SDK is just a wrapper around cli anyway). Neither tab says anyth…

>And your assumption is wrong on another level. The Agent SDK specifically exists so that you can write your own harness and give it custom tools - that's its entire purpose. It's even documented in their custom tools guide [1]. Yea, you don't seem to even understand what you are writing. This in no way contradicts any statement I or Anthopic has said. >Neither tab says anything remotely like "if a third-party app pr…

> At this point, it's clear that you either have questionable reading comprehension skills, are being willfully ignorant, or are arguing in bad faith

As an onlooker to this exchange, perhaps things aren't as clear as you're making out. After reading what you wrote I remain unclear. What precise actions with headless mode risk getting me banned?

Is the idea that you are only ever permitted to feed the Agent SDK human generated prompts? That so long as the text you feed into it is 100% human generated you can use your entire quota and won't be banned? To be clear, you could take the output and make a tool call and present that to a human, and the human could go on to make further prompts, but feeding the result of the tool call (which you presented to the human) back into the context is forbidden? Am I on the right track here?

Re: Addressing Antigravity Bans and Reinstating Access

#174
post #135

What I don’t understand about policy violations is why Google never warns the user before banning. A simple alert or email would reduce so much frustration on the part of users and so much overhead for Google. ToS change frequently and it’s not really fair to assume the user knows what is and is not correct use of tokens.

I think from their end, they see a lot more malicious users (e.g. spam accounts) that it's not worth providing a gentle warning before a ban. There might've been thousands more accounts created for Chinese companies for distillation[0], that Google didn't think of/weren't able to initially distinguish genuine user accounts just using a third party tool on their Antigravity token. Like in a similar vein, Instagram som…

This is where mechanisms like ZKP + CBA built from a government ID will allow the company to distinguish, even through third parties, all without exposing actual identity.

Re: Addressing Antigravity Bans and Reinstating Access

#176
post #8

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

> Way too risky to use Google services like this tied to your primary account.

I would also avoid using the same credit card between accounts. I used a Venmo card for my chrome extension account as an extra layer of separation.

Re: Addressing Antigravity Bans and Reinstating Access

#177
post #42

All this whole thing did is ensure I never, ever use any google AI service. The fact that they didn't instantly comprehend what a total account ban means when they've got people with 20+ years worth of personal data in those accounts is incredibly concerning.

But there were no total account bans. If you got banned from antigravity you also got banned from the Gemini API.

Re: Addressing Antigravity Bans and Reinstating Access

#178
post #108

Earlier 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…

They just want people to pay more via API. Technically, your example would violate ToS, because the purpose matters. Like a license file may allow personal use and prohibit commercial use (unless you obtain a commercial license).

Also because normal usage has predictable usage patterns, which allows them to optimise and predict costs. Flat rate pricing only makes sense in that regime.

Re: Addressing Antigravity Bans and Reinstating Access

#180
post #45
post #38

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

It's really not that hard. I switched about 10 years ago. Just every time you log in with your old email, replace it with your new one. Every time you email someone, email them from your new one with a note: "this is my new email". In a few months I had migrated everything to the new email.
Post reply on HN