Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Addressing Antigravity Bans and Reinstating Access

github.com

Post reply on HN
Print view View original

101–110 of 230 posts

Re: Addressing Antigravity Bans and Reinstating Access

#101

Post by ithkuil »

TacticalCoder wrote: post #93
koolba wrote: 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.

> The digital death sentence of losing access to your email I agree that the digital death sentence is really bad and doubly so seen that many are using single-sign on tied to their Google identity but... > with a company that notoriously has no way for the average human to contact a human is not worth the risk There's definitely phone support for paying Google Workspace users: don't tell me there's not, my wife got…

This remains a problem for the personal account though (arguably what "primary account" meant in GP)

Re: Addressing Antigravity Bans and Reinstating Access

#102

Post by ok_dad »

aliljet wrote: post #45
tjoff wrote: 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...

Just start changing addresses. Forward the rest. It takes about a year. Changing your name is way harder and tons of folks do that all the time.

Re: Addressing Antigravity Bans and Reinstating Access

#103

Post by ForHackernews »

aliljet wrote: post #45
tjoff wrote: 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...

Sign up at fastmail.com, set up forwarding, change your "reply-to" address. A year later, you'll have nothing arriving in gmail except marketing cruft.

Re: Addressing Antigravity Bans and Reinstating Access

#104

Post by hsaliak »

The 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, they are subsidizing to promote a general IDE, but I dont understand constraining the generative AI backend that Gemini CLI hits.

Finally, it's unclear what's allowed and what's not if I purchase the API access from google cloud here https://developers.google.com/gemini-code-assist/docs/overvi...

The Apache License of this product at this point is rich. Just make it closed source and close the API reference. Why have it out there?

Re: Addressing Antigravity Bans and Reinstating Access

#105

Post by wafflemaker »

calcifer wrote: post #50
aliljet wrote: post #45

Earlier quoted context omitted.

How do you even pull away from a Gmail address? I'm nearly twenty years into that service. Getting banned would be absolutely devastating...

Use your own domain to sign up for a paid email service, provided by a company that focuses on email. I use Fastmail, but there are many other options. Set up forwarding in Gmail to your new address. Then, whenever you log in to a website or app with your Gmail, take a moment to change it to your new address. In a few weeks, most of your important accounts will be covered. In a few months, almost everything you still…

For quite some time (approx 8 years) I've used an email forwarding (Blur, but any works) to avoid spam.

This looks like perfect case for change of email, since lot of these accounts can be moved out from Gmail by changing the address that email is forwarded too.

Looks like all this hassle with generating a new email for each service pays for the second time (by ease of changing the main mail), in addition to spam and privacy protection.

Re: Addressing Antigravity Bans and Reinstating Access

#106

Post by stavros »

ithkuil wrote: post #101
TacticalCoder wrote: post #93

Earlier quoted context omitted.

> The digital death sentence of losing access to your email I agree that the digital death sentence is really bad and doubly so seen that many are using single-sign on tied to their Google identity but... > with a company that notoriously has no way for the average human to contact a human is not worth the risk There's definitely phone support for paying Google Workspace users: don't tell me there's not, my wife got…

This remains a problem for the personal account though (arguably what "primary account" meant in GP)

Can that account be upgraded to Workspace just to get the support?

Re: Addressing Antigravity Bans and Reinstating Access

#108

Post by gck1 »

NewsaHackO wrote: post #91
gck1 wrote: post #78

> Using third-party software, tools, or services to harvest or piggyback on Gemini CLI's OAuth authentication to access our backend services is a direct violation of Gemini CLI’s applicable terms and policies. It's been 2 months since these bans have started, first Anthropic, then Google. And their wording is still so confusing that I can't get a simple answer to a simple question: Is piggybacking on headless 'gemini…

Have you read the website? https://platform.claude.com/docs/en/agent-sdk/overview >Unless previously approved, Anthropic does not allow third party developers to offer claude.ai login or rate limits for their products, including agents built on the Claude Agent SDK. Please use the API key authentication methods described in this document instead. Seems clear-cut to me.

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. OAuth was just faster to plug in.

So if I open source my solution that allows opencode & openclaw to go through claude cli's headless mode, is this allowed? Is this a product that allows claude.ai login?

What if I open source a 1 line bash loop (e.g. ralph loop) that does the same?

What if I build a more complex bash loop that goes through my tasks in a text file, and calls claude cli for each?

I don't know at which point this becomes "offering claude.ai login" or a "product", or "building agents".

Here's my product:

while :; do cat PROMPT.md | claude ; done

Am I blacklisted now?

Re: Addressing Antigravity Bans and Reinstating Access

#109

Post by joquarky »

fooker wrote: post #86
WarmWash wrote: post #40

Earlier quoted context omitted.

Anyone can buy the tokens via the API and do whatever they want with them. Its not evil of Google to say "Here is an allotment of steeply discounted tokens, but you can only use them with our services."

It is evil to block your email and hold your photos hostage over it though :)

I would question the judgment of anyone who thought they would maintain "don't be evil" beyond IPO.

Re: Addressing Antigravity Bans and Reinstating Access

#110

Post by NewsaHackO »

gck1 wrote: post #108
NewsaHackO wrote: post #91

Earlier quoted context omitted.

Have you read the website? https://platform.claude.com/docs/en/agent-sdk/overview >Unless previously approved, Anthropic does not allow third party developers to offer claude.ai login or rate limits for their products, including agents built on the Claude Agent SDK. Please use the API key authentication methods described in this document instead. Seems clear-cut to me.

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.
Post reply on HN