Appeal request: Antigravity CLI suspended (no third-party OAuth client)

Dear Antigravity Support Team,

I am writing to appeal the suspension of my Google account from Antigravity, Gemini CLI, and Gemini Code Assist.

  • Account: s..@gmail. com
  • Product: Antigravity CLI (agy), version 1.4.11
  • Environment: Windows 11; official agy.exe installed with the official Antigravity CLI installer
  • Restriction date: 2026-11-03 (Asia/Shanghai)
  • Message shown: “This service has been disabled in this account for violation of Terms of Service.”

WHAT I DID

I have only ever used Google’s official Antigravity CLI binary. On 2026-11-03 at 13:51 (+08:00) I ran it once in headless mode, started by another local program on my own computer:

agy --print “” --mode accept-edits --add-dir “” --output-format json --print-timeout 20m

These are documented vendor flags. Google’s official headless-mode documentation states that headless mode uses cached credentials and documents single-prompt, scripting, and CI usage:
antigravity.google/docs/cli/headless/

My local CLI log from that run shows that agy.exe itself authenticated using the credential already in its own keyring:

printmode.go:206] Print mode: starting (promptLength=2231, model=“”, conversationID=“”)
keyring.go:64] keyringAuth: loaded token … expired=false
auth.go:157] ChainedAuth: authenticated via keyring (effective: keyring)
server_oauth.go:229] OAuth: authenticated successfully as [account]

The run did not complete. From 13:54 to 14:01 the CLI’s direct connections to Google APIs timed out:

Post “daily-cloudcode-pa.googleapis.com/v1internal:loadCodeAssist”: dial tcp … connectex: A connection attempt failed because the connected party did not properly respond …
W server_oauth.go:350] Eligibility check attempt 1 failed transiently, retrying in 1s
W auth_manager.go:140] Timed out waiting for the account-eligibility verdict; sending anyway

At 14:07-14:08 the CLI began reporting “not logged into Antigravity”, and the account showed the 403 Terms-of-Service message.

On that day, before the suspension appeared, there was exactly one non-interactive prompt run and two local metadata queries (agy models, agy agents). There was no cron job, no request loop, and no parallel burst on that day. I did not use --dangerously-skip-permissions, did not override the system prompt, and did not chain multiple agents.

I should be transparent that the same official CLI had also been used normally since 2026-10-29 for personal local tasks, including summarizing publicly available videos and working with local files on my own machine. That usage was through Google’s official CLI only and was not shared with or exposed to anyone else. I have not found any warning email or prior notice about a violation.

WHAT I DID NOT DO

I have not:

  • used OpenClaw, OpenCode, Claude Code, Cursor, or any other third-party client, wrapper, gateway, or resale/relay service to access Antigravity, Gemini CLI, or Gemini Code Assist;
  • exported, copied, redirected, or shared an Antigravity/Gemini OAuth token or credential with any non-Google program or service;
  • provided my Google or Antigravity login to another person or service;
  • operated any proxy or relay for the purpose of sharing, reselling, or evading Antigravity’s usage limits;
  • harvested quotas or bypassed a system measure or usage limit.

The only automation was a local parent process starting Google’s own signed agy.exe. Authentication happened inside the official CLI’s own keyring; the token was never handed to or replayed by a non-Google client. I did not set up any reverse proxy for Antigravity.

WHY I BELIEVE THIS IS NOT THE PROHIBITED CONDUCT

The Terms of Service prohibit “using third party software, tools, or services to access the Service (e.g. using OpenClaw with Antigravity OAuth)”:
antigravity.google/terms

In my case the network requests and OAuth authentication came from Google’s own official CLI, using Google’s documented headless interface. I did not transplant the product credential into a third-party client, and I did not give anyone else access.

I relied in good faith on the official documentation, which presents headless mode as a supported way to “script agent tasks, integrate with CI pipelines, and capture machine-readable output”. I was not trying to bypass quotas or share access.

I am also aware that in Google’s official Gemini CLI issue tracker, a maintainer described headless mode and custom system prompts as valid documented features that should not by themselves result in a ban:
github.com/google-gemini/gemini-cli/issues/20813

I recognize that whether the official CLI may be invoked by another local process is not fully spelled out. I am asking for human review precisely because that boundary is ambiguous, not because I believe I can decide it myself.

REMEDIATION

  • I have stopped all non-interactive and automated Antigravity CLI invocations while this appeal is pending.
  • I will review myaccount.google.com/connections and remove any unnecessary third-party connections; I will remove anything else you identify.
  • If invoking the official CLI from an external parent process is outside the permitted use, I accept that finding. Going forward I will use the official Antigravity app/CLI interactively only, or use a paid Vertex AI / AI Studio API key for programmatic automation, and will not use a product login for third-party agent automation.
  • If this is a first restriction on this account, I ask that it be treated as such. [If not your first restriction, delete this sentence.]

REQUEST

Please manually review this account. If the flag resulted from a false positive — possibly related to the transient network timeouts and the retry/eligibility-check behavior visible in the log between 13:54 and 14:01 — please restore access.

If a specific action is considered a violation, please tell me exactly which one so I can remove it and comply going forward.

I can provide the redacted local CLI log from 2026-11-03; it contains no tokens or credentials.

Thank you for your time.

Sincerely,
Sangmanrong


Redacted local CLI log excerpt from 2026-11-03 (no tokens, no credentials, no project paths):

13:51:35 (the first and only real headless run)

I printmode.go:206] Print mode: starting (promptLength=2231, model="", conversationID="")
W keyring.go:64] keyringAuth: loaded token, expiry=2026-11-03 14:33:10 +0800 CST expired=false
I auth.go:157] ChainedAuth: authenticated via keyring (effective: keyring)
I server_oauth.go:229] OAuth: authenticated successfully as [account]

13:54:23 (direct connections to Google APIs timing out — network level, not 403)

W cache.go:146] Get "`www.googleapis.com`/oauth2/v2/userinfo": dial tcp 172.217.112.4:443:
  connectex: A connection attempt failed because the connected party did not properly respond
  after a period of time, or established connection failed because connected host has failed to respond.
E errorreport.go:224] Post "`daily-cloudcode-pa.googleapis.com`/v1internal:loadCodeAssist":
  dial tcp 172.217.116.4:443: connectex: A connection attempt failed ...

14:00:00 (transient eligibility-check failure, retrying)

E error_parsing.go:65] Error: Post "`daily-cloudcode-pa.googleapis.com`/v1internal:loadCodeAssist":
  dial tcp 172.217.119.4:443: connectex: A connection attempt failed ...
W server_oauth.go:350] Eligibility check attempt 1 failed transiently, retrying in 1s: ...
W auth_manager.go:140] Timed out waiting for the account-eligibility verdict; sending anyway

14:07-14:08 (afterwards the CLI begins reporting “not logged into Antigravity”)

W cache.go:146] Cache(loadCodeAssistResponse): Singleflight refresh failed:
  error getting token source: You are not logged into Antigravity.
I auth.go:157] ChainedAuth: authenticated via keyring (effective: keyring)

Local metadata queries (no model quota consumed)

14:05  agy models  -> Fetching available models...
14:05  agy agents  -> (no task sent)

Operations that did NOT occur (verifiable from the local logs)

  • no --dangerously-skip-permissions
  • no custom system prompt
  • no cron job / request loop / parallel burst
  • no client other than agy.exe issued any Antigravity API request