Hi Antigravity Team and Community,
I am planning to develop an complementary client application (similar in concept to OpenClaw) utilizing the newly released Antigravity SDK, for my own. However, I want to ensure absolute compliance with the Antigravity Terms of Service, specifically regarding Section 6.
Section 6 states that users/developers cannot leverage large language models by connecting to Antigravity services via OAuth authentication within a third-party application.
To avoid any infringement, my intended architecture follows a strict “Bring Your Own Key” (BYOK) / Local-Only approach:
- The application will be an closed-source local tool ONLY to fulfill my own needs.
- It will NOT bundle or share any global OAuth credentials or API keys. only use local go harness backend.
Given this architecture, the application acts purely as a local client or orchestration interface for the user’s personal Antigravity subscription (e.g., Google AI Ultra or personal preview quotas), without any commercial resale or centralized pooling of backend resources.
Could you please clarify whether developing or maybe distributing such tool violates Section 6 of the ToS? If this pattern is restricted, what is the recommended way to build custom agent UIs or extensions on top of the Antigravity SDK for the community?
Thank you for your time and for the amazing work on the SDK!