Is invoking the official Antigravity CLI from Codex allowed?

Google Antigravity
1

I would like to clarify Section 6 of the Antigravity Terms of Service.

On my Windows PC, OpenAI Codex invokes Google’s official agy.exe as a local process. It passes text I select through stdin and reads the revised text from stdout, using the documented headless mode.

Authentication stays entirely within the official Antigravity CLI. Codex does not extract or reuse OAuth tokens, call Google’s backend directly, or bypass usage limits.

Is this use permitted with a personal Google AI Pro subscription, or does Section 6 prohibit it because Codex launches the CLI?

Please clarify whether the third-party access restriction also applies to this use of the official CLI.

2

Hi @Hossy,

Welcome to the Google AI Developer Forum.

Yes, the workflow you described is completely fine to use with your personal Google AI Pro subscription. Here are a few helpful details on how this aligns with our policies:

  • Section 6 & Official CLI Usage: Section 6 of the Google Antigravity Additional Terms of Service and our Third-Party Software FAQ are specifically intended to prevent third-party harnesses from extracting, proxying, or reusing Antigravity OAuth credentials to call private backend endpoints directly. 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.
  • Personal Google AI Pro Quota: Per our Plans documentation, headless CLI runs use the exact same Google AI Pro quota and rate limits as interactive sessions, as long as the setup runs locally for your own individual use (and is not shared as a multi-user relay or run in a rapid polling loop).
  • Helpful Tip for stdin / stdout: As noted in the CLI Headless Mode documentation, passing the -p / --print flag expects the prompt as a command-line argument and ignores stdin. If Codex pipes your selected text over stdin, we recommend either passing the text via -p "..." or using --input-format stream-json --output-format stream-json (Stream prompts from stdin).

Please let us know if you have any other questions , we are happy to help.