I’m a paying Google AI Pro subscriber, and I want a clear answer on this.
My whole AI workflow runs through a self-hosted personal agent (OpenClaw) on my own machine at home. One user, me. No resale, no shared access, no multi-account tricks. Claude and OpenAI both let me use my subscription there through their own official CLIs (Claude Code, Codex). Google is the only one that doesn’t.
The FAQ says wrapping agy inside third-party agents or applications is not supported on consumer plans, and recommends an API key instead. That leaves me paying for a subscription I can’t use where I actually work, plus pay-per-token on top. That’s not a reasonable deal for a personal user.
So, plainly:
Is there any supported way for a single subscriber to use their Gemini subscription quota from a personal third-party agent, through the official unmodified agy CLI, with no token handling on our side?
If not today, is it on the roadmap?
I’m not upgrading my plan until this changes. My workflow lives in external tools, and a subscription locked to Google’s own apps isn’t worth more to me. Other providers already support this; I’d like Google to as well.
While we cannot provide formal legal interpretations of the Terms of Service, here are direct answers to your two questions based on our supported features and policies:
Using a Consumer Subscription Quota from a Personal Third-Party Agent (OpenClaw) via the Unmodified agy CLI:
No — under consumer plans (including Google AI Pro and Google AI Ultra), there is currently no supported way to invoke, wrap, or orchestrate the official, unmodified agy CLI from inside a third-party coding agent such as OpenClaw, even in a single-user local setup where agy manages its own authentication with no token handling on your side (Can I use Antigravity CLI headless mode in third-party coding agents or automate account switching?).
Where Your Google AI Pro Subscription Quota Is Supported Today:
Interactive Antigravity App, Antigravity IDE, and Antigravity CLI (agy) sessions, as well as Headless mode (agy -p) for your own direct scripts and CI workflows.
For OpenClaw or other third-party coding agents, the supported path remains using a Google AI Studio or Gemini Enterprise API key rather than a consumer Antigravity login.
Roadmap & Product Feedback:
We do not have a public roadmap or timeline to share regarding third-party agent support under consumer subscriptions at this time. Any future updates to plan policies or supported integrations will be announced in our Changelog and Plans overview.
Thank you again for sharing your perspective with us. Please let us know if you have any further questions, and we will be happy to assist you.
Hi @Rebbanpalli_Naveen, Your response here seems to contradict your answer from 20 days ago: Is invoking the official Antigravity CLI from Codex allowed? Where you wrote - “Having Codex invoke the official, unmodified agy.exe binary as a local process on your Windows PC—while authentication (agy auth login) and all backend communication stay strictly inside agy.exe—is a supported use of CLI Headless Mode.” So its a yes for Codex but no for OpenClaw to do the same thing? Above you wrote: "No — under consumer plans (including Google AI Pro and Google AI Ultra), there is currently no supported way to invoke, wrap, or orchestrate the official, unmodified agy CLI from inside a third-party coding agent such as OpenClaw…". What do you mean by “inside” in this context? If Codex calls agy.exe - does that mean that agy.exe was called from “inside” Codex? If @eliavb directs OpenClaw to call agy.exe how is that any different than what the other poster wanted to do with Codex in the question posed from 20 days ago?
Thank you for pointing out that earlier thread and asking for clarification.
Here is how those two responses relate and how the current policy applies to both Codex and OpenClaw:
Codex vs. OpenClaw & Why the Earlier Reply (#186952) Differs:
There is no difference between Codex and OpenClaw , having either tool invoke agy / agy.exe is not supported under a consumer Google Account login.
After that October 5 reply in #186952 was posted, the policy on using Antigravity CLI headless mode in third-party coding agents was updated to explicitly clarify that wrapping agy inside third-party coding agents or applications is not supported under consumer plans. This updated policy supersedes the earlier guidance in #186952 and applies equally to Codex, OpenClaw, Claude Code, and OpenCode.
What Calling agy “From Inside” (or “Wrapping”) a Third-Party Agent Means:
In this context, invoking agy “from inside” or “wrapping” agy in a third-party agent means having an external coding agent or harness (such as Codex or OpenClaw) spawn agy / agy.exe -p as a child subprocess to delegate prompts, tool calls, or automated agent loops.
By contrast, Headless mode (agy -p "<prompt>" --output-format json) under a consumer subscription is intended only for your own direct scripting and CI workflows (for example, a standalone shell script, Makefile target, or CI job that you invoke directly without another coding agent acting as the orchestrator).
Running agy with a Gemini API Key (Without a Consumer Account Session):
If you want to run agy in headless workflows without establishing a consumer Google Account session, you can configure agy to use a Gemini API key from Google AI Studio by setting "modelProvider": "gemini" in ~/.gemini/antigravity-cli/settings.json and exporting GEMINI_API_KEY="your-api-key". In this mode, requests go directly to the Gemini API rather than through a consumer subscription session.
Please let us know if you need any additional information.
@Rebbanpalli_naveen Thank you for your reply. You wrote “After that October 5 reply in #186952 was posted, the policy on using Antigravity CLI headless mode in third-party coding agents was updated” - Can you please point me to the evidence of this? I am unable to find any evidence of a policy update after October 5th. The link only directs me to a frequently asked questions page. The most recent terms of service updates I am able to find are from September.
I have the same question, and I’d like to ask for a definitive answer from a Google team member, because the guidance currently conflicts.
On 2026-10-07 (topic #186246), a team reply said that launching the official, unmodified agy binary as a local subprocess in headless mode is permitted on a personal plan, and that it makes no policy difference whether a script or another local coding assistant (e.g. Claude Code) starts it, as long as no OAuth tokens or cookies are extracted.
The current FAQ says: “Wrapping agy inside third-party coding agents or applications, or automating account rotation, is not supported under consumer plans.” Replies in this topic (2026-10-23 and 2026-10-26, from a community member rather than the team) say a later policy update supersedes the earlier team reply, but no changelog entry or dated policy change has been linked.
The CLI docs also describe an API-key mode (modelProvider: "gemini" plus GEMINI_API_KEY), where “the CLI never establishes an account session”.
Could someone from the Antigravity team confirm:
a. Which of 1) and 2) is current for consumer plans (Google AI Pro / Ultra), and when the FAQ wording changed?
b. Whether the restriction in 2) applies only to account-session (subscription) sign-in, so that a third-party agent invoking agy in API-key mode is fine?
c. Whether a thin local wrapper script that only execs the unmodified agy binary and adds default flags (model, project), without touching credentials, changes the answer?
d. Whether “not supported” means “may be subject to enforcement” or only “no support is provided”?
Why I’m asking for a clear yes/no rather than a case-by-case answer:
Working with agents is moving toward orchestration: one agent delegates sub-tasks to agents from other vendors, in sequential, unattended runs, because each model has different strengths. The whole point is to remove the human who manually relays prompts and reviews every intermediate result. That is a shared direction across the industry, not a niche setup.
At the same time, the cost of misreading the boundary is severe. The enforcement described in gemini-cli discussion #20632 blocked access across Antigravity, Gemini CLI and Code Assist, and a second flagged violation means a permanent ban. When a misreading can cost someone their account, “not supported” is too ambiguous to plan around.
I’m not asking Google to change the policy here. I’m asking for a written, dated boundary that says what is allowed and under which sign-in mode, so users can build workflows on the right side of the line instead of guessing. Thank you.
To clarify the timeline for @b_w and answer @Tora39’s question (a): the Google Antigravity Terms of Service themselves were not modified after September; rather, the Official FAQ was updated in mid-October 2026 to add the section “Can I use Antigravity CLI headless mode in third-party coding agents or automate account switching?” That FAQ entry reflects the current policy for consumer plans (Free, Plus, Pro, and Ultra): “Wrapping agy inside third-party coding agents or applications, or automating account rotation, is not supported under consumer plans.” Earlier forum replies in #186246 and #186952 gave an overly broad interpretation before that FAQ entry was published.
Here are direct answers to @Tora39’s remaining questions (b)–(d):
(b) API-Key Mode (modelProvider: "gemini" + GEMINI_API_KEY):Yes. As documented under Using a Gemini API Key, when agy is configured with "modelProvider": "gemini" and GEMINI_API_KEY, requests go directly to the Gemini API under standard pay-as-you-go API terms and “the CLI never establishes an account session.” Consumer subscription restrictions do not apply in API-key mode.
(c) Thin Local Wrapper Scripts: Running your own local shell alias or wrapper script that passes default flags (such as --model) to agy for your own direct terminal or CI use is fine (Headless CLI), whereas having a third-party coding agent (like Claude Code, Codex, or OpenClaw) invoke that wrapper script using your consumer account session is still treated as wrapping agy inside a third-party coding agent.
(d) Meaning of “Not Supported”: Under a consumer login, wrapping agy in third-party coding agents can trigger automated Terms of Service enforcement and account suspension, as noted in the FAQ. We have also passed your feedback requesting dated policy changelog entries and a clearer written boundary in the official docs to our product and policy teams.
I’d like to share that while I understand the current product ToS as they lay, I would love to become a Google AI subscriber but I see no reason to. While I would like to use Gemini models, agy is not a great harness (I don’t even think Claude Code or Codex are great harness (Codex is decent)), and I would love to use Google models with third party harnesses while retaining the benefits of a Google Pro subscription but at this point I see zero value in paying for a Google Pro subscription if I’m locked into agy as my agentic harness.