Skip to content

[Bug]: Antigravity account suspended for "violation of Terms of Service" during T3 delegation — is the T3 Antigravity driver an allowed client? #40713

Open

Description

@crakjack

Area: apps/server

What happened
A Claude agent in a T3 thread delegated a review task to the Antigravity provider (delegate_task, providerInstanceId: "antigravity", model gemini-4-neon, thought_level: high). A one-line test through the same route had succeeded minutes earlier. The review task failed with:

This service has been disabled in this account for violation of Terms of Service. Please submit an appeal to continue using this product.

The account is a paid Antigravity Pro subscription and showed 100% quota remaining.

Full context, to be fair to T3: about 5–10 minutes before this, the same agent (without the user's approval) had also sent roughly 20–25 Gemini 4 Neon requests through a local CLIProxyAPI-style proxy that holds the Antigravity login, partly via OpenCode, including bursts of 429 retries. Google staff on the Antigravity forum say third-party wrappers and proxies (they name OpenCode, Claude Code, OpenClaw) are not permitted, so that traffic is the most likely trigger. This report is not claiming T3 caused the suspension.

What I'm asking

  1. Is T3's Antigravity driver an approved client under Antigravity's terms, or could Google treat it as a "third-party wrapper"? Users get only one appeal, so this matters before reconnecting.
  2. If there is any risk, please document it in the provider settings and show a warning when enabling Antigravity.
  3. Could the driver surface this specific error clearly (account suspended → link to Google's appeal form), instead of a generic child failure?

Steps to reproduce
Not deterministic. Delegate to antigravity / gemini-4-neon from a parent agent; on an account Google has flagged, the child fails with the message above.

Expected behavior
Clear guidance on whether T3's Antigravity integration is ToS-compliant, and a specific "account suspended, appeal here" error.

Actual behavior
Generic delegated-task failure carrying Google's ToS message; no guidance in T3 about allowed usage.

Impact
Loss of a paid Antigravity subscription until an appeal (one per account) is approved.

Version: 0.1.12-nightly.20261122.5071 (desktop, macOS)

Environment: macOS (Darwin 27.2), parent agent Claude Code (Opus 5.5) in T3; child provider Antigravity, model gemini-4-neon.

Activity

  1. juliusmarminge commented on Nov 22, 2026

    @juliusmarminge
    Member

    Thanks for the careful report. T3 Code cannot speak for Google, so we cannot promise how Google will treat any client. Here is what T3's Antigravity integration does: it does not call Antigravity's backend itself and does not reuse your login token. It runs Google's own Antigravity CLI (agy) in its ACP mode on your environment. That CLI is installed from Google's own release channel (or is a binary you choose under Binary path), and you sign in through the CLI's own browser flow. Requests to Google are made by Google's CLI, not by T3 or a proxy. That is different from a third-party proxy that holds an Antigravity login and forwards requests from other tools, which is the kind of setup Google staff have said is not allowed and which, as you note, ran on your account just before the suspension. If you need certainty before reconnecting, ask Google, for example in your appeal or on the Antigravity forum, whether driving the official agy CLI over its ACP interface is permitted. The error you saw is Google's own message, passed through unchanged. A warning in provider settings and a dedicated 'account suspended, appeal here' message are reasonable feature requests, and we're tracking them as such.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions