Is invoking the official Antigravity CLI (agy --print) from a third-party developer tool an acceptable use?

Google Antigravity
1

Hi Antigravity team,

I’m developing an open-source VSCode extension that lets a user coordinate the official CLI coding agents they already subscribe to (Codex CLI, Claude Code, and Antigravity CLI) in one place. I’d like to confirm whether my usage pattern complies with the Antigravity Additional Terms of Service before releasing it.

What my extension does:

  • It launches the official, unmodified agy CLI binary as a child process on the user’s machine, using its documented non-interactive flag (--print).
  • Authentication is entirely delegated to the official CLI: the user signs in through Antigravity’s own OAuth flow. My extension never touches, extracts, or reuses tokens, cookies, or credentials, and never calls Antigravity backends directly.
  • There is no rate-limit or quota circumvention — every request is a normal CLI invocation under the user’s own account, initiated by the user’s explicit action.

My question: The Additional ToS prohibits “using third party software, tools, or services to access the Service (e.g. using OpenClaw with Antigravity OAuth)”. I read this as targeting unofficial harnesses that hijack Antigravity OAuth to reach the backend directly — not as prohibiting a tool that simply runs the official CLI through its documented interface (much like a shell script, task runner, or CI job would). Given that the Antigravity SDK explicitly invites programmatic agent integration, is my understanding correct? If the CLI is not the intended surface for this kind of integration, I’d be happy to migrate to the official SDK instead.

I want to do this the right way, so any official guidance would be greatly appreciated. Thank you!

2

That’s fine. The issue Google has with third-party tools is when they use the models at your disposal for your account in other harnesses (like OpenCode via Antigravity OAuth). Antigravity is heavily subsidized by Google. It is about a 60% to 90% discount (in my experience, it’s the latter) compared to Google Cloud’s listed costs for peer models.

Cheers.

3

Thanks for the earlier answer, DrQwertySilence. I know this is the same question as others posted here, but is there any official Google response we can rely upon?

I am building a desktop development tool for my own use that launches the official, Google signed Antigravity CLI binary on the person’s machine, exactly as a terminal would. The tool never reads, stores or forwards the OAuth token: the CLI does its own sign in in the person’s browser and keeps its own credentials in its own home folder. My tool only starts the binary, passes it the prompt, and reads what it prints.

The terms say that using third party software, tools or services to access the Service (the example given is a third party client using Antigravity OAuth) is a breach and grounds for suspension of the Antigravity and Gemini CLI accounts. The first sentence of that clause (“using the Service in connection with products not provided by us”) could be read to cover any launcher, including a terminal multiplexer or an IDE’s integrated terminal.

Two questions:

  1. Is launching the official signed CLI from another program, with the CLI holding its own OAuth session and the program never touching the token, within the terms?
  2. If not, is there a supported way for a desktop tool to hand a person’s prompt to Antigravity on their own account, in the way the Gemini API key path allows for the Gemini API?

I would rather ask than guess, since the penalty in the terms lands on the person’s own accounts.

4

Read their terms of service, they are pretty clear.

Cheers.