Supported automation into an existing Antigravity conversation on a consumer plan

Google Antigravity
1

Please clarify the supported approach for a user’s existing Antigravity desktop conversation to cooperate with that same user’s Codex and Claude conversations on one Windows computer.

We understand that the consumer-plan FAQ excludes wrapping agy inside third-party coding agents, and that a managed sidecar exposes agentapi send-message. We have not deployed an external bridge or reused authentication tokens.

Is owner-authorized computer-use automation of the normal Antigravity desktop interface permitted to submit a bounded technical task into the user’s exact existing conversation? If not, is any supported integration available for that conversation on the existing consumer plan, without account migration or paid API substitution? Please distinguish ordinary GUI operation from external API/OAuth/CLI wrappers, and native internal sidecar events from relaying another provider’s prompts.

The required result is actual work and a useful response in the same existing conversation, not a new CLI worker or clone. We need a documented supported route or explicit clarification, not a way around restrictions. No account identifiers, local paths, private conversations or logs are included in this question.

2

Hi @Vlad_Cube_Tiling_Bat,

While we cannot provide custom legal interpretations beyond our published terms, here is how our Terms of Service, FAQ, and Sidecars documentation apply to your questions:

  1. Automated Access from Third-Party Tools (Including GUI / Computer-Use Automation):

    • Section 6 of the Google Antigravity Additional Terms of Service prohibits “using the Service in connection with products not provided by us” and states that “using third party software, tools, or services to access the Service… is a breach of this Agreement.”
    • Because the restriction applies to using third-party software, tools, or services to access or drive Antigravity under a consumer login, using external computer-use or GUI automation to submit tasks from third-party coding agents (such as Codex or Claude) into an Antigravity desktop conversation is not supported and can result in account suspension or termination.

  2. Native Sidecars vs. Third-Party Agent Integration:

    • Sidecars (sidecar.json) are background processes managed by Antigravity intended for persistent local background scripts, scheduled recurring tasks (schedule), and reacting to local events.
    • Sidecars and local CLI modes (headless mode agy -p) are intended for your own direct scripting, CI workflows, and local event tasks—not for relaying prompts from or wrapping Antigravity inside third-party coding agents under a consumer plan (FAQ).

  3. Supported Options:

    • On your existing consumer plan (without API billing): There is no supported automated integration for third-party coding agents to inject prompts into an existing consumer-plan Antigravity conversation. You can use Antigravity, Codex, and Claude independently on the same local project workspace, and manually interact with your existing Antigravity conversation directly through the desktop GUI.
    • For third-party coding agent integrations: To connect third-party coding agents with Gemini programmatically, we recommend using a Gemini Enterprise or Google AI Studio API key instead of an Antigravity consumer login (FAQ).