ToS clarification: May a local Codex MCP bridge use agentapi with Antigravity?

Google Antigravity
, , ,
1

Hello Antigravity Team,

I am a Google AI Pro subscriber requesting written clarification about a local, single-user integration I built between OpenAI Codex and the Antigravity desktop application.

I contacted Google One support first, but they explained that they currently have no way to contact the Antigravity division directly and suggested using the official community.

What I built

The local architecture is:

Codex → local MCP server → local Antigravity agentapi → Antigravity desktop conversation

The connector:

  • Runs only on my Windows computer.
  • Sends instructions to existing Antigravity conversations using agentapi send-message.
  • Reads local conversation status and transcript information to determine when work is complete.
  • Does not extract, copy, expose, or forward Google OAuth credentials.
  • Does not call Antigravity backend endpoints directly.
  • Does not modify the official Antigravity executable.
  • Is not hosted, distributed, resold, shared between users, or used to pool accounts.
  • Does not attempt to bypass quotas or rate limits.
  • Operates only under my own account and supervision.

I added idempotency protection, strict project-to-conversation routing, local-only access, output redaction, and duplicate-request prevention.

Why I am uncertain

Section 6 of the Antigravity Additional Terms states that using third-party software, tools, or services to access Antigravity is a breach of the agreement.

However, the official Antigravity Sidecars documentation says Sidecars can use the agentapi CLI to interact with Antigravity programmatically, including:

  • agentapi new-conversation <prompt>
  • agentapi send-message <conversation_id> <prompt>

My connector currently runs as an external local MCP process rather than as an Antigravity-managed Sidecar.

I also found a related community discussion suggesting that orchestrating the unmodified official agy CLI through local stdio may be permitted. My architecture is different because it uses the documented Sidecar agentapi interface.

Questions

  1. Is this external local MCP-to-agentapi architecture permitted under Section 6?
  2. Would it become permitted if the connector were installed and launched as an explicitly enabled Antigravity Sidecar?
  3. May an external coding agent prepare instructions and review filesystem changes while the official Antigravity application performs the implementation and authentication?
  4. Is read-only monitoring of locally stored Antigravity status and transcripts permitted?
  5. If agentapi is restricted to Antigravity-managed Sidecars, is orchestrating the documented agy headless CLI the supported alternative?
  6. Can an approved local orchestration workflow use the Antigravity allowance included with Google AI Pro, or must it use a Vertex AI or Google AI Studio API key?

I have paused further live connector use while awaiting clarification.

Because Section 6 mentions possible account suspension, I would appreciate confirmation from a Google or Antigravity team member rather than community interpretation alone.

Thank you.

2

Hi @Michael_Gatica,

According to the official Google Antigravity FAQ ( FAQ | Google Antigravity Docs ), using third-party software or external bridges with your personal Antigravity subscription credentials violates the Terms of Service. Below are direct answers to your specific questions:

  • External MCP-to-agentapi Bridge: Using third-party software, external scripts, or local MCP bridges (e.g., connecting OpenAI Codex to Antigravity) under your personal Google Account or Google AI Pro subscription allowance is not permitted under Section 6. Operating external wrappers with subscription logins can trigger automated abuse detection and result in account suspension.
  • Antigravity-managed Sidecars: Sidecars must be installed and executed natively within the official Antigravity application lifecycle. They cannot be used as external RPC bridges to route instructions from third-party non-Google agents.
  • External Coding Agents: Driving Antigravity sessions using external agent tools while authenticated with subscription seat credentials is prohibited. Programmatic multi-agent workflows should be built using official APIs.
  • Read-Only Transcript & Status Monitoring: Automated extraction, scraping, or polling of local conversation state and transcripts by external third-party tools is restricted under Section 6.
  • Supported Programmatic Alternative: Programmatic orchestration should be conducted via Google AI Studio API keys (https://aistudio.google.com/) or Vertex AI APIs rather than orchestrating local desktop binaries or the `agy` CLI with external tools.
  • Allowance vs API Keys: Subscription allowances included with Google AI Pro or personal Antigravity seats cannot be used for third-party or custom programmatic orchestration. Custom integrations must use a Google AI Studio API key or Vertex AI project.