ToS Clarification — Is opencode-antigravity-acp (official agy acp in OpenCode) permitted under the Antigravity Terms of Service?

Hi @Pracurser,

Welcome to the Forum,

Thank you for asking before pointing users to this setup. Under Section 6 of the Google Antigravity Terms, the FAQ, and Other editors (ACP):

  • Consumer oauth-personal Boundary: Launching unmodified agy acp interactively is permitted only in a thin client where Antigravity is the agent—meaning the human sends raw prompts directly to agy acp and Antigravity owns its sign-in, system prompt, tools, and session history. Wrapping agy acp inside an outer third-party coding agent harness (such as OpenCode) that injects system instructions, serialized tool definitions, replayed cross-model context, or automated loops is not permitted on oauth-personal—even without extracting OAuth tokens—and risks automated enforcement or suspension.
  • Compliant Path: For an outer agent harness, authenticate via gemini-api-key (GEMINI_API_KEY) or Google Cloud agent-platform (ACP Authentication), passing explicit ACP authenticate or running /logout so cached consumer OAuth is not reused. For your README, please link the Terms, FAQ, and ACP docs.