Repository navigation
feat(plugin): warn about Antigravity ToS account risk - #225
Merged
Merged
Conversation
Google terms now ban third-party clients using Antigravity logins. Show a startup console warning and red toast, plus README notice. Assisted-by: Claude Opus 5.5
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
README Warning
Add a prominent warning under the badges stating that Google's current Antigravity terms prohibit third-party tools such as OpenCode from using an Antigravity login.
Document the exact account-disabled error, link the appeal form, and point users to the supported
googleandgoogle-vertexproviders.Rename the "Traffic Simulation" feature line to "Background Session Requests" to describe what it does without the evasion framing.
Startup Warning
Emit the same warning once per process on plugin startup for both OpenCode v1 and v2, with no opt-out given the risk of account suspension.
OpenCode v1 also shows a red error toast, while v2 logs to the console only because its plugin context exposes no toast API.
Tests
Cover the once-per-process guard, the toast variant, the missing-TUI path, and both synchronous and asynchronous toast failures.