Can a local AI coordinator launch the official Antigravity CLI with subscription sign-in?

Google Antigravity
, , , ,
1

Hi Antigravity team,

I’m building a personal, local-only tool to coordinate coding tasks. I want to clarify whether this setup is allowed:

- Claude Code or my own coordinator launches the unmodified official agy CLI as a subprocess

- It passes a task and reads the CLI’s output

- AGY uses its own normal Google AI subscription sign-in

- No OAuth tokens are extracted or shared, no private endpoints are called, and no limits are bypassed

- This is for my own work, not a public service or shared subscription

The headless documentation supports scripts, CI pipelines and Python subprocess examples. However, section 6 of the terms restricts third-party software accessing the service.

Does my setup fall within supported headless automation, or is it prohibited third-party access? Does the answer change if I launch the same script myself instead of Claude launching it?

I specifically want to know whether this is permitted with subscription authentication. If there are additional restrictions on unattended or concurrent jobs, please point me to those as well.

Could a Google team member clarify the intended boundary and link the applicable policy? I want to follow the supported approach before enabling this integration. Thanks!

Really just trying to have all my subscriptions work together between Gemini, claude, and openai. With having one AI to use but route work around to best models for the job

2

Hi @Croixofwar,

Welcome to the Forum,

Here is the clarification on how your setup relates to the Google Antigravity Additional Terms of Service and our Headless CLI documentation:

1. Is launching the official agy CLI as a local subprocess allowed under Section 6?

Yes. Running the official, unmodified agy binary locally in headless mode (for example, agy -p "<prompt>" --output-format json or stream-json) using your own personal Google AI subscription sign-in for your own individual work is permitted.

  • What Section 6 restricts: Section 6 of the Google Antigravity Additional Terms (and the corresponding FAQ entry) prohibits extracting, intercepting, or reusing Antigravity OAuth tokens or session credentials to authenticate third-party clients, harnesses, or proxies (for example, configuring OpenClaw, OpenCode, or Claude Code to call Antigravity backend APIs directly using your Antigravity login).
  • Why your setup is compliant: As documented in our Headless CLI guide, agy -p is explicitly designed to be invoked by scripts and programmatic drivers using cached credentials from an interactive agy sign-in. Because the unmodified agy binary handles all authentication and service communication itself—and your coordinator only passes prompts and reads output over standard CLI flags/stdio—it is supported usage.

2. Does the answer change if you launch the script yourself vs. Claude Code launching it?

No. From a policy standpoint, there is no difference whether the unmodified agy subprocess is started by your own script, a local coordinator, or another local coding assistant (such as Claude Code), provided that:

  • All Antigravity service access happens exclusively through the unmodified official agy binary (or the official Antigravity Python SDK).
  • No OAuth tokens, cookies, or credentials are extracted, read, or passed to the external tool.
  • The setup is strictly for your own personal, single-user workflow and not shared, pooled, or exposed as a multi-user service.

3. Restrictions on unattended or concurrent jobs

While there is no separate hard cap on headless subprocess invocations, keep the following plan and rate-limit boundaries in mind (Plans & AI Credits Docs):

  • Shared 5-Hour & Weekly Quotas: Headless agy runs draw from the same baseline quota (refreshed every 5 hours up to your weekly rate limit on Google AI Pro/Ultra, plus any configured AI Credit Overages) as interactive IDE and CLI sessions.
  • Concurrency & Automated Bursts: Baseline rate limits are dynamically managed based on system capacity and to prevent abuse. Spawning multiple concurrent agy processes or running continuous, high-frequency unattended loops can quickly exhaust your 5-hour/weekly quota (429 RESOURCE_EXHAUSTED) or trigger automated rate/abuse protections if traffic patterns resemble automated scraping or account pooling.
  • Recommendation: Keep local coordinator runs sequential or low-concurrency for personal tasks. If your workflow scales into high-volume or continuous unattended background pipelines, we recommend using a Google AI Studio API key or Gemini Enterprise instead of a personal subscription.