Seeking guidance: embedding Antigravity CLI locally in a third-party IDE (user's own subscription)

Google Antigravity
1

Hi,

I’m the developer of Alva Code (http/alva-codecom), a desktop IDE launching September 1, 2026, and I’d like to proactively ask for guidance before shipping anything, rather than testing the limits of the Terms of Service.

Intended integration: Alva Code would spawn the official Antigravity CLI binary, installed by the user, locally on the user’s own machine (using the documented headless mode). Authentication happens exclusively in the CLI’s own login flow — Alva Code never touches credentials, never proxies requests, and runs no server in between. Each user uses their own individual subscription at ordinary, individual usage levels.

I’m aware of the account suspensions earlier this year related to third-party agents and the “abuse/proxy” clause in Section 6 of the ToS. My goal is precisely to avoid putting my users’ Google accounts at risk. Until I hear otherwise, the Antigravity integration in Alva Code is disabled / marked experimental.

My questions:

  1. Is locally spawning the official Antigravity CLI from a third-party IDE, with the user’s own subscription and the CLI’s own auth flow, a permitted use?
  2. If not, is there a supported path (e.g. an official integration surface, ACP support, or an enterprise/partner program) you would recommend for IDE integrations?

I’m happy to adjust the architecture in whatever way makes this acceptable — or to keep the integration off entirely if that’s the answer.

Thanks for any pointers, André Schmid Developer, Alva Code — http/alva-codcom

1 Like