Hi Antigravity team,
I’m developing an open-source VSCode extension that lets a user coordinate the official CLI coding agents they already subscribe to (Codex CLI, Claude Code, and Antigravity CLI) in one place. I’d like to confirm whether my usage pattern complies with the Antigravity Additional Terms of Service before releasing it.
What my extension does:
- It launches the official, unmodified
agyCLI binary as a child process on the user’s machine, using its documented non-interactive flag (--print). - Authentication is entirely delegated to the official CLI: the user signs in through Antigravity’s own OAuth flow. My extension never touches, extracts, or reuses tokens, cookies, or credentials, and never calls Antigravity backends directly.
- There is no rate-limit or quota circumvention — every request is a normal CLI invocation under the user’s own account, initiated by the user’s explicit action.
My question: The Additional ToS prohibits “using third party software, tools, or services to access the Service (e.g. using OpenClaw with Antigravity OAuth)”. I read this as targeting unofficial harnesses that hijack Antigravity OAuth to reach the backend directly — not as prohibiting a tool that simply runs the official CLI through its documented interface (much like a shell script, task runner, or CI job would). Given that the Antigravity SDK explicitly invites programmatic agent integration, is my understanding correct? If the CLI is not the intended surface for this kind of integration, I’d be happy to migrate to the official SDK instead.
I want to do this the right way, so any official guidance would be greatly appreciated. Thank you!