Personal app using the official agy acp binary with Google AI Pro — permitted?

Google Antigravity
1

I’m a Google AI Pro subscriber. I built a private app for my own use on my Windows PC. It launches the official, unmodified agy acp binary as an ACP client, the same way Zed or T3 Code do, signed in with my own personal account (oauth-personal). It’s single-user and interactive, uses only the Gemini models in my plan, never runs agy -p, never touches OAuth tokens, and refuses every tool permission request.

Is this permitted under Section 6 of the Antigravity Additional Terms? Thank you.

2

Hi @Carlos_aTorres05,

Yes—based on the architecture you described, using your own private, single-user interactive client on your PC that communicates over standard JSON-RPC with the official, unmodified agy acp (antigravity-acp) binary and authenticates through its native oauth-personal flow is permitted under our Terms of Service.

As documented in our Changelog (v1.4.2), Zed ACP Extension guide, and Authentication guide, agy acp is designed to run the Antigravity CLI as an Agent Client Protocol (ACP) server over stdio so ACP-compatible clients can connect to it.

To ensure your setup remains fully compliant with Section 6 of the Google Antigravity Additional Terms of Service and our FAQ, please keep the following boundaries in mind:

  • Unmodified Official Binary & Native Auth: Always launch the unmodified agy acp binary and let it manage its own authentication ("auth": { "type": "oauth-personal" }); never extract, proxy, or reuse internal OAuth tokens outside the binary.
  • Single-User Interactive Use Only: Do not use the client for unattended background automation, multi-user serving, automated account rotation, or wrapping agy as a sub-agent inside another third-party coding agent loop.
  • Supported Models: As you noted, outside of first-party IDE integrations, ACP sessions are scoped to the Gemini models included in your Google AI Pro plan.