Official clarification requested: Is using the unmodified Antigravity CLI (agy -p) through a personal Node-RED workflow permitted?

Hello Antigravity Team,

I would appreciate an official clarification on the permitted use of the Antigravity CLI under a consumer subscription. I have read the FAQ and related community threads, but I have not found a definitive answer for my setup. User replies in related threads contradict each other, for example:

What the FAQ (FAQ | Google Antigravity Docs) says:

- “Antigravity CLI headless mode (agy -p) is intended for direct scripting and CI workflows.”

- Wrapping agy “inside third-party coding agents or applications … is not supported under consumer plans.”

My setup:

- A locally installed Node-RED instance on my personal Windows computer, listening only on 127.0.0.1 with no external access.

- A Node-RED workflow that I wrote myself launches the official, unmodified Antigravity CLI (agy -p) as a local subprocess.

- Requests are sequential, one at a time. No third-party coding agent is involved.

- I use one Google account. I do not rotate accounts, and I do not extract, copy or reuse OAuth tokens. The CLI uses its own normal sign-in.

- Tool execution is denied in every call.

- Use is personal and non-commercial, for experimentation and technical testing.

Questions:

1. Is launching agy -p from my own local Node-RED workflow considered permitted “direct scripting”, or does it fall under the restriction on wrapping agy in third-party applications under consumer plans?

2. What exactly decides the answer: that the workflow is self-written, runs locally, runs sequentially, has human approval per request, or is non-commercial? Would the answer change if I later used the same workflow for commercial work?

3. If this is not permitted on a consumer plan, the FAQ recommends a Gemini API key for third-party agents. Does that recommendation also apply to personal local automation like mine, or is a different arrangement needed?

4. Is there an official page or policy that explicitly covers this scenario?

I want to make sure my implementation complies with Google’s terms before continuing further testing. I would particularly appreciate a reply from an Antigravity team member or an authorized Google representative.

Thank you for your time.

Hi @Joseph_Koch,

Thanks for checking before continuing your testing. Here is how our consumer-plan policy applies to your setup:

  1. Personal local scripting vs. third-party wrappers: As noted in the Headless Mode documentation and the FAQ, agy -p is designed for direct local scripting and CI workflows. Launching the official, unmodified agy -p binary sequentially from your own local 127.0.0.1 Node-RED flow—using a single Google account’s native sign-in, without extracting OAuth tokens, and triggered interactively by you—is permitted as personal local scripting.
  2. What is restricted under consumer plans: Under Section 6 of the Google Antigravity Additional Terms of Service, you may not wrap agy inside a third-party coding agent (such as Claude Code or Codex), run unattended autonomous polling loops, or rotate accounts to pool quota.
  3. Unattended or commercial automation: If you want to run unattended background automations or power an external application workflow, please use Antigravity’s built-in Automations (Dynamic Workflows) or authenticate with a Gemini API key (GEMINI_API_KEY) from Google AI Studio.