Hi @Herzchen,
Thank you for laying out your workflow and questions in detail.
While we cannot provide formal legal interpretations of the Terms of Service, here is how our policies apply to agy -p CI/scripting workflows and third-party coding agents on consumer plans:
- What Is Supported (
agy -pDirect Scripting & CI Workflows):- Antigravity CLI headless mode (
agy -p) (--print/--prompt) is intended for direct scripting and CI workflows (using--output-format jsonorstream-jsonand your cached single-useragylogin).
- Antigravity CLI headless mode (
- What Is Prohibited (Third-Party Coding Agent Wrappers & Account Rotation):
- Using third-party software, tools, or services to access Antigravity, wrapping
agyinside third-party coding agents or applications, or automating account rotation is not supported under consumer plans and violates the Terms of Service.
- Using third-party software, tools, or services to access Antigravity, wrapping
Addressing your specific questions (1–7):
- Distinction Between Direct CI (
B) and Wrappingagyin a Third-Party Agent (A) (Questions 1–4 & 7):- The prohibition targets Case A—where a third-party coding agent or external application wraps
agyas its execution/model backend, extracts or forwards Antigravity OAuth tokens/credentials, or orchestratesagyas an automated sub-agent. - In Case B, how a static file or commit in your repository was authored beforehand (whether typed by you or drafted with help from another assistant) does not by itself turn your own deterministic CI script into a third-party agent wrapper, provided the external assistant never invokes
agy, never accesses your Antigravity session or credentials, and is not coupled in an automated multi-agent loop.
- The prohibition targets Case A—where a third-party coding agent or external application wraps
- Human Authorization vs. Automated Closed-Loop Orchestration (Questions 5–6):
- If an external AI assistant automatically writes requests to a repository that auto-triggers
agy -p, reads the output back from GitHub, and autonomously dispatches follow-up runs, that closed-loop setup effectively usesagy -pas a backend tool for the external agent. - To keep your workflow clearly within the supported direct scripting and CI workflow boundary on a consumer plan:
- Trigger your CI verification runs explicitly (for example, via a manual
workflow_dispatchor your own commit/PR actions) rather than allowing an external AI agent to autonomously trigger and consumeagy -pruns in a loop. - Invoke only the official, unmodified
agy -pbinary using your single authenticated session (Headless mode), with no credential sharing, proxy wrappers, or account rotation. - For any workflow where a third-party agent needs to autonomously orchestrate or call models in an automated loop, use a Google AI Studio API key or Gemini Enterprise (FAQ).
- Trigger your CI verification runs explicitly (for example, via a manual
- If an external AI assistant automatically writes requests to a repository that auto-triggers