I’m writing to request written clarification before using T3 Code (an open-source coding agent by Theo / t3.gg) with my Google Antigravity account, as I want to avoid any risk of account suspension.
Context on T3 Code’s implementation
From what I understand, T3 Code does not reuse OAuth tokens from the Antigravity IDE or CLI, nor does it wrap or drive the desktop binary externally. Instead, it runs Google’s official Antigravity ACP agent, downloaded from the ACP Registry, with its own independent sign-in flow. This makes it structurally different from community MCP bridges that use agentapi to control the Antigravity desktop app from outside.
I would appreciate clear answers to the following:
Is running the official Antigravity ACP agent through T3 Code considered an approved use under the current Antigravity Terms of Service, or does it still fall under the Section 6 restriction on “third-party software, tools, or services” accessing Antigravity?
Does the statement from your team that you “don’t intend to ban people for using their Gemini subs” through T3 Code constitute an official policy position, or was it an informal/verbal assurance?
If the Antigravity team considers this permitted, could you point me to any official documentation, FAQ update, or written statement I can rely on?
If it is not permitted, what would be the recommended alternative for using my Gemini/Antigravity subscription with a third-party coding agent — for example, via Google AI Studio API key or Vertex AI?
I have no intention of bypassing rate limits, sharing credentials, or using the subscription for commercial resale or multi-user orchestration.
Thank you for your time and for any clarification you can provide. I’d greatly appreciate a written response I can reference going forward.
Yes, using T3 Code with your personal Antigravity subscription is permitted for your own single-user, interactive development, as long as it runs the official antigravity-acp binary from the ACP Registry and signs in through its native OAuth flow ("auth": { "type": "oauth-personal" }).
The restriction in Section 6 of our Terms of Service and FAQ is still actively enforced—social media posts aren’t official policy, and we do suspend accounts that extract or proxy OAuth tokens (like OpenClaw/OpenCode bridges), wrap agy -p inside third-party agent loops, or automate multi-account rotation. The reason T3 Code is fine here is architectural: it communicates over standard JSON-RPC with our unmodified antigravity-acp agent binary rather than scraping credentials or driving the desktop app externally. (Just note that outside of first-party IDE integrations, model selection in ACP clients is limited to the Gemini models included in your plan.)
While the FAQ doesn’t list individual ACP clients by name, you can reference this reply along with our official documentation on oauth-personal agent configuration in the Authentication guide and Zed ACP setup guide. If you ever use other third-party coding agents that don’t run antigravity-acp, the supported options are a Google AI Studio API key (GEMINI_API_KEY) or Gemini Enterprise.
Googles ACP runtime is currently broken on ARM systems using 39-bit memory addressing, including virtually all Pixel phones as well as most(?) other Android phones.
It can’t be installed as is. So while I’d like to follow these recommendations, it is straight up impossible.
Hopefully they patch this too. It’s a really because we’re stuck with barely any options. My Antigravity CLI runtime suggested to patch the thing—and I turned it down immediately. Better to wait for official upstream patches.