What is preventing anyone from automating on top of the normal google Antigravity CLI?

It’s detectable and has been known to result in account bans. People have been doing it since the early days of Gemini, when the ToS was still unclear, and some only found out after their accounts were banned. There have been multiple GitHub issues and reports to Google about it. It’s not worth the effort unless you’re willing to risk a secondary Google account.

▲

Hyperlisk 6 hours ago | parent | prev | next [-]

Google explicitly allows this and documents how: https://antigravity.google/docs/cli/headless/

	▲	polotics 4 hours ago \| parent [-]
		This is so weird, because using a script to invoke the agy cli is clearly using a "third party tool to access the service" !

▲

warpech 7 hours ago | parent | prev | next [-]

Wouldn’t that violate the quoted ToS? I guess it would.

▲

anon84873628 6 hours ago | parent [-]

"Using the service in connection with products not provided by us." The Agy CLI is provided by them.

▲

mcepl 2 hours ago | parent | next [-]

And if I am not mistaken, Theo’s T3Code (which was explicitly told was bad), doesn’t even use anything else than AI producer provider command line tools and use them with `-p`.

▲

kristofferR 5 hours ago | parent | prev [-]

So? There's still a connection to products not provided by them.

Remember that this is a TOS, so you gotta presume that they will act as malicious as possible within the text.

▲

Majromax 5 hours ago | parent [-]

That line of reasoning has no end. If you use Antigravity on anything other than a Google Chromebook or Pixel, the hardware is a 'product not provided by them'. Is that a TOS violation?

	▲	kristofferR 5 hours ago \| parent [-]
		Yes. I'd avoid using services like this.

▲

KeplerBoy 7 hours ago | parent | prev [-]

I think that is what paseo is doing and I don't risk trying it.