Skip to content

docs(antigravity): warn that Antigravity's terms prohibit third-party clients - #457

Merged
amondnet merged 1 commit into
mainfrom
amondnet/antigravity-tos
Sep 4, 2026
Merged

docs(antigravity): warn that Antigravity's terms prohibit third-party clients#457
amondnet merged 1 commit into
mainfrom
amondnet/antigravity-tos

Conversation

@amondnet

@amondnet amondnet commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

Summary

Google's Antigravity terms clause 6 states that "using third party software, tools, or services to access the Service (e.g. using OpenClaw with Antigravity OAuth) is a breach of this Agreement", and that such a breach "may be grounds for suspension or termination of your Antigravity and/or Gemini CLI accounts". shunt's antigravity provider is third-party software using Antigravity OAuth, so it falls squarely under that clause.

Until now the repo carried only the generic "your own call" disclaimer that covers Codex, Grok, Kimi, and Cursor. Antigravity is the one backend whose terms name this use explicitly, so it warrants a warning the reader sees before running shunt login antigravity — not a paragraph buried after setup.

The docs quote the clause as written rather than paraphrasing or overstating it. In particular, the clause names Antigravity and/or Gemini CLI accounts, not the whole Google account, and the wording added here keeps that scope.

Changes

  • README.md, README.ko.md, README.ja.md, README.zh-CN.md — a bold paragraph directly after the existing "your own call" disclaimer, quoting the clause verbatim and telling the reader to decide before running shunt login antigravity.
  • site/src/content/docs/{,ko/,ja/,zh-cn/}providers/antigravity.mdx — an <Aside type="caution" title="Antigravity's terms"> placed before "Quick start", so it is read before login.
  • site/src/content/docs/{,ko/,ja/,zh-cn/}guides/providers.mdx — the same aside at the end of the Antigravity section, mirroring the Cursor section's existing "Your own call" caution.

12 files, 94 insertions, no code. All four locales are updated in the same PR per AGENTS.md; wiki/ is generated and was not touched.

Milestone / spec

None — documentation only; no implementation behavior changes.

Checklist

  • cargo build passes — N/A, no Rust changed
  • cargo test passes (new behavior is covered; tests run without network/loopback where possible) — N/A, no Rust changed
  • cargo clippy --all-targets -- -D warnings clean — N/A, no Rust changed
  • cargo fmt --all --check clean — N/A, no Rust changed
  • Source files stay under 500 lines
  • English only; matches surrounding style (plus the maintained ko/ja/zh-CN translations)
  • Frozen spec in docs/ updated if this change deviates from it — no deviation; docs/ untouched
  • User-facing docs updated for behavior/config/endpoint/CLI/provider/model changes — README.md (+3 locales) and site/ (8 pages); wiki/ left alone
  • Any new GitHub Action is pinned to a full commit SHA — none added

Notes for reviewers

  • Verification. npm ci && npm run build in site/ succeeded: 153 pages built, and the terms link renders in the built HTML for every affected page. Worth stating explicitly because no workflow builds site/ on a pull request — the docs site is only built on push to main, so CI will not produce this evidence for you.
  • Scope of the claim. Please check the wording against the source clause. The intent is to reproduce it, not to editorialize: the risk named is suspension or termination of the Antigravity and/or Gemini CLI accounts, and the decision is left to the reader.
  • Placement. On the provider page the aside sits before "Quick start" deliberately, so a reader cannot follow the login steps without passing it first. In the providers guide it sits at the end of the Antigravity section to match the Cursor section's existing caution.
  • No code changed, so no cargo checks apply.

Summary by cubic

Adds a warning that Google's Antigravity terms explicitly prohibit third-party clients like shunt's antigravity provider, with suspension or termination of Antigravity and/or Gemini CLI accounts as a possible consequence. Previously the docs carried only the generic "your own call" disclaimer.

  • Quotes the clause verbatim in the README and docs site across all four locales.
  • Places the warning before shunt login antigravity steps so readers see it before acting.
  • No code changed; docs only.

Written for commit 1daa2cb. Summary will update on new commits.

… clients

Clause 6 of https://antigravity.google/terms prohibits "using third party
software, tools, or services to access the Service", and a breach "may be
grounds for suspension or termination of your Antigravity and/or Gemini CLI
accounts". shunt's `antigravity` provider is exactly such third-party
software, so operators should read the terms and decide for themselves.

Adds a paragraph after the existing "your own call" disclaimer in the README
(en/ko/ja/zh-CN) and an "Antigravity's terms" caution aside to the site
provider page and providers guide in all four locales.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the documentation across multiple languages (English, Japanese, Korean, and Chinese) to include a prominent warning regarding Google's Antigravity terms of service. It explicitly cautions users that accessing the service via third-party software using Antigravity OAuth (such as shunt or OpenClaw) violates their terms and may result in account suspension or termination. As there are no review comments provided, there is no feedback to evaluate.

@amondnet
amondnet marked this pull request as ready for review September 4, 2026 06:34
@sonarqubecloud

sonarqubecloud Bot commented Sep 4, 2026

Copy link
Copy Markdown

@codecov

codecov Bot commented Sep 4, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@greptile-apps

greptile-apps Bot commented Sep 4, 2026

Copy link
Copy Markdown

Greptile Summary

Adds prominent warnings across the English, Korean, Japanese, and Simplified Chinese documentation that Antigravity’s terms prohibit third-party clients and identify possible account consequences.

  • Places the warning in all four root README variants.
  • Adds caution asides to the Antigravity provider and provider-guide pages before or alongside setup instructions.
  • Keeps the documented consequence scoped to Antigravity and/or Gemini CLI accounts.

Confidence Score: 5/5

The documentation-only PR appears safe to merge.

The warning is consistently added across the maintained locales and relevant documentation surfaces without introducing a concrete correctness, rendering, or policy-scope defect.

Important Files Changed

Filename Overview
README.md Adds the English Antigravity terms warning near the existing third-party-client disclaimer.
site/src/content/docs/providers/antigravity.mdx Adds a caution about the terms before the provider’s quick-start instructions.
site/src/content/docs/guides/providers.mdx Adds the same caution to the English Antigravity section of the provider guide.
README.ja.md Adds a localized Japanese version of the warning.
README.ko.md Adds a localized Korean version of the warning.
README.zh-CN.md Adds a localized Simplified Chinese version of the warning.
site/src/content/docs/ja/providers/antigravity.mdx Adds the localized warning before the Japanese quick-start section.
site/src/content/docs/ko/providers/antigravity.mdx Adds the localized warning before the Korean quick-start section.
site/src/content/docs/zh-cn/providers/antigravity.mdx Adds the localized warning before the Simplified Chinese quick-start section.

Reviews (1): Last reviewed commit: "docs(antigravity): warn that Antigravity..." | Re-trigger Greptile

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 12 files

Architecture diagram
sequenceDiagram
    participant Reader as Docs Reader
    participant README as README (all locales)
    participant Site as Docs Site (antigravity.mdx, providers.mdx)
    participant Shunt as shunt CLI
    participant Antigravity as Google Antigravity
    
    Note over Reader,Antigravity: Documentation warning flow for Antigravity provider
    
    Reader->>README: Reads provider disclaimer section
    README-->>Reader: NEW: Bold warning (Antigravity terms clause 6 quoted verbatim)
    Note over README: States third-party access via OAuth is a breach, may cause suspension/termination of Antigravity/Gemini CLI accounts
    
    Reader->>Site: Opens Antigravity provider page
    Site-->>Reader: NEW: Caution aside before "Quick start" section
    Note over Site: Warning placed before login steps so reader sees it first
    alt Reader also views providers guide
        Reader->>Site: Opens providers guide
        Site-->>Reader: NEW: Same caution aside at end of Antigravity section
    end
    
    alt Reader proceeds with setup
        Reader->>Shunt: Runs `shunt login antigravity`
        Shunt->>Antigravity: OAuth authentication flow
        Antigravity-->>Shunt: Auth tokens (access/refresh)
        Note over Shunt,Antigravity: Potential breach of Antigravity terms clause 6 (third-party client)
        Shunt-->>Reader: Login complete, routing available
    else Reader decides against
        Reader->>Reader: Weighs risk of account suspension/termination
        Note over Reader: No shunt login performed
    end
Loading

Re-trigger cubic

@codspeed-hq

codspeed-hq Bot commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

Merging this PR will not alter performance

✅ 83 untouched benchmarks


Comparing amondnet/antigravity-tos (1daa2cb) with main (3421716)

Open in CodSpeed

@amondnet
amondnet merged commit 30b0fa7 into main Sep 4, 2026
16 checks passed
@amondnet
amondnet deleted the amondnet/antigravity-tos branch September 4, 2026 06:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant