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

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

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.

Hi, I’d like an official answer on this too, for a specific case.

I’m building a local desktop app (a workspace with terminal panels, similar to a terminal emulator). Users can open the official, unmodified Antigravity CLI (agy) inside one of those terminal panels, in their own project folder.

  • The user installs agy themselves with Google’s official installer.
  • The user signs in inside agy with their own Google account, exactly as in any terminal.
  • Our app never reads, copies, stores or reuses their OAuth tokens or session, and never calls Google’s APIs directly.
  • Our app shows the CLI’s output in its panel and may, in the future, read its official structured output to show a chat view. It never starts sessions in loops and limits concurrent sessions to a few.

Does item 6 of the Antigravity terms allow this? If any part of it is not allowed (for example, reading the output for a chat view), which part?

Could someone from the Google team confirm? Thank you.

i. I have a personal Google AI Pro plan. On my own Windows PC, a small script of mine starts Google’s official, unmodified agy CLI in headless mode (agy -p). The script is triggered from Claude Code. agy does its own login; my script never reads, copies or forwards any tokens, calls no private APIs, and runs one job at a time for my own projects only. No account switching.

Your FAQ says wrapping agy inside third-party coding agents “is not supported under consumer plans”. On your forum, a moderator said on 7 October that launching agy from Claude Code is permitted, but another reply on 16 October said it is not and “violates our Terms of Service”.

Which answer is current? Is my setup allowed on Google AI Pro, and could it lead to my account being suspended? A written answer would help a lot. Thank you.

Hello Google Antigravity Team,

Thank you for the clarification posted on October 7 regarding the official Antigravity CLI (agy) and personal Google AI subscriptions.

I would like to request further clarification for my specific OpenClaw integration because the October 7 response appears to conflict with the current Antigravity FAQ.

My setup:

  • Operating system: Arch Linux

  • Subscription: Personal Google AI Pro

  • OpenClaw: 2026.10.3

  • Official Antigravity CLI: 1.4.2

  • Third-party plugin: @claw0gang/antigravity v0.3.3

  • Requested model: gemini-3.8-flash-high

  • Purpose: Use Antigravity as an automatic fallback when my primary OpenClaw model is unavailable.

The plugin is installed but currently disabled.

The intended architecture is:

OpenClaw → Claw0gang plugin → Official agy CLI → Antigravity models

I want the official, unmodified Antigravity CLI to handle authentication and service communication. I do not intend to extract or reuse OAuth tokens, access undocumented endpoints, bypass rate limits, or share subscription access.

My questions:

  1. Is this specific Claw0gang integration permitted with a personal Google AI Pro subscription?

  2. Does the October 7 clarification permitting official agy subprocess execution apply to OpenClaw’s AgentHarnessV2 plugin?

  3. If permitted, may the integration consume my existing Antigravity subscription quota without a separate Gemini API key?

  4. Does using Antigravity automatically as a fallback count as prohibited third-party agent access, even when the official agy binary handles authentication?

  5. If the integration is prohibited, is there an official permission or approval process for this architecture?

I understand that separate account eligibility requirements and usage restrictions still apply.

Could an authorized Google Antigravity representative clarify which interpretation is current and provide a link to the applicable policy?

Thank you.

Following up on the answer above (Oct 7), which said launching the official CLI with a personal subscription sign-in is permitted whether the user or a local coding assistant such as Claude Code launches it.

The current FAQ (antigravity.google/docs/faq) names Claude Code in “Why can’t I use third-party software … with my Antigravity login?” and says wrapping agy inside third-party coding agents “is not supported under consumer plans”. Could Google confirm which applies to this exact setup?

  • Claude Code on my own Windows machine starts the unmodified official agy.exe (agy -p --output-format stream-json), signed in with my personal Google account, for my own repositories.
  • No MCP server, relay, shared server, token extraction or account rotation.
  • Each run is started by an explicit task handoff I request, never unattended.
  • Built-in limits: one run per repository and two on the machine at a time, at most 5 starts per repository in 10 minutes, no retries.

Is this permitted on a consumer plan (AI Pro), or does it need a Gemini API key or Gemini Enterprise?