Is invoking the official `agy` CLI from a local AI coding assistant allowed on an individual Google AI account?

Google Antigravity
1

Antigravity Additional Terms §6 prohibit “using third party software, tools, or services to access the Service”. The docs describe agy -p for scripting and CI.

Our setup: a local assistant (Anthropic’s Claude Code) would launch the official agy.exe as a child process on the same Windows machine, send the prompt via stdin and read --output-format json from stdout, using the user’s cached sign-in. It would never read or reuse OAuth tokens and never call Antigravity backend endpoints directly.

  1. Is this permitted under the Terms for an individual (non-Workspace) account?
  2. Does it consume the same quota as interactive agy use?

An answer from a Google team member would be appreciated. Thanks.

2

Hi @Ivan_Valenzuela,

Welcome to the Forum,

Here are the answers to your questions:

Is invoking the unmodified agy.exe binary in headless mode from a local assistant permitted on an individual account?

Yes. Section 6 of the Antigravity Additional Terms of Service (and our FAQ regarding third-party tools) prohibits extracting, proxying, or reusing Antigravity OAuth credentials inside third-party harnesses to call Antigravity’s backend endpoints directly.

Spawning the official, unmodified agy (agy.exe) binary locally as a single-user child process on your own machine using its documented headless flags is a supported use of the CLI, provided that:

  • You do not extract, read, or forward Antigravity’s cached OAuth tokens to external tools.
  • All requests execute through the unmodified agy binary under your own local agy login session.
  • The setup is used strictly by you as an individual user on your local machine (not exposed as a shared server, multi-user relay, or unattended high-frequency polling loop).

(Tip: If you also integrate with editors or orchestrators that support the Agent Client Protocol (ACP), Google provides an official antigravity-acp (agy_acp_server) adapter in the ACP Registry, which supports personal Google accounts via oauth-personal.)

Does it consume the same quota as interactive agy use?

Yes. Headless executions use the same backend session and draw from the exact same Google AI account quota, credit pool, and rate limits (Free, Google AI Pro or Google AI Ultra) as interactive agy CLI or Antigravity IDE sessions.

Technical tips for your Windows stdin / stdout subprocess setup:

Passing the prompt via stdin vs. -p: When -p / --print is passed on the command line, agy expects the prompt as the flag’s string argument and intentionally ignores stdin (so -p never hangs on open subprocess pipes).

  • To pipe the prompt via stdin (and close stdin / send EOF), omit -p:

    agy.exe --output-format json

  • To pass the prompt as a flag argument:

    agy.exe -p "Your prompt here" --output-format json

  • To stream multiple turns over stdin and stdout as NDJSON:
    agy.exe --input-format stream-json --output-format stream-json

Reusing conversation context & conserving quota: Each fresh headless invocation initializes a full agent session (system instructions, workspace rules/skills, and tool schemas). To avoid rapidly consuming your quota window or hitting rate limits, avoid high-frequency polling loops and reuse existing sessions across follow-up turns with -c / --continue or --conversation <conversation_id> (returned in the JSON response envelope).

3

Thank you @chunduriv. One follow-up so I can rely on this: the official FAQ (antigravity.google/docs/faq) names Claude Code specifically as third-party software that can’t be used with an Antigravity login and recommends an API key instead, and the Terms forbid using the Service “in connection with products not provided by us”. Could you confirm your answer (Claude Code spawning the unmodified agy binary locally, on demand, never touching OAuth tokens) is Google’s official reading of those texts, or point me to an official page that says so?