TL;DR
- Antigravity OAuth tokens are exclusive to official Google interfaces — using them with OpenClaw, OpenCode, or any third-party tool is a ToS violation
- Enforcement is immediate — 403 ToS error with Antigravity access suspended, no prior warning
- Scope is limited to Antigravity — Gmail and other Google services NOT affected (per Google official statement)
- Recovery path exists — Varun Mohan confirmed “users not aware… will get a path for them to come back”
- Safe path: Official Antigravity IDE only; or use Gemini API keys (commercial) for custom tools
Scope
This page covers Google Antigravity terms as of February 2026, with focus on third-party access restrictions. It is a snapshot checklist, not legal advice.
What changed recently
- February 12-23, 2026: Mass ban wave targeting users who authenticated OpenClaw/OpenCode with Antigravity OAuth tokens. Paying AI Ultra subscribers ($250/month) were suspended without warning.
- February 22, 2026: Varun Mohan (Google DeepMind) confirmed enforcement was due to “massive increase in malicious usage” that “tremendously degraded quality of service.”
- February 23, 2026: Peter Steinberger (OpenClaw creator) announced removal of Google Antigravity support from OpenClaw.
See sources section below for full timeline and citations.
Critical ToS clauses
Section 6: Abuse Prevention (Antigravity Additional Terms)
“You must not abuse, harm, interfere with, or disrupt the Service. This includes, but is not limited to, using the Service in connection with products not provided by us.”
Interpretation for engineering teams:
| Phrase | Meaning | Consequence |
|---|---|---|
| “products not provided by us” | OpenClaw, OpenCode, custom CLI scripts, any third-party tool | Detected via User-Agent/binary signature analysis |
| “using the Service in connection with” | Routing Antigravity OAuth through non-Google software | 403 ToS error + account suspension |
| “Authorized Application” | Official Antigravity IDE or Google interfaces only | Only permitted access method |
Enforcement Rights
Per Varun Mohan (Google DeepMind engineer, X Feb 22, 2026) and Google DeepMind spokesperson (VentureBeat, Feb 23, 2026):
- No prior notice required — suspensions are immediate
- Recovery path exists — “users not aware that this was against our ToS will get a path for them to come back”
- Scope limited to Antigravity — Google confirms Gmail and other services are NOT affected
- Billing continues — users report being charged for suspended Antigravity access
Detection Method
Google detects third-party usage through:
- User-Agent analysis — identifying non-official clients
- Binary signature detection — fingerprinting the connecting software
- OAuth token usage patterns — monitoring for anomalous request patterns
- Backend load monitoring — “massive increase” in usage triggers investigation
Safe access paths
| Method | Permitted | Authentication | Notes |
|---|---|---|---|
| Official Antigravity IDE | ✅ Yes | OAuth (Google account) | Primary supported interface |
| Gemini CLI (official) | ✅ Yes | OAuth (Google account) | Google’s official command-line tool |
| OpenClaw + Antigravity OAuth | ❌ No | — | Explicit ToS violation — will result in suspension |
| OpenCode + Antigravity OAuth | ❌ No | — | Explicit ToS violation — will result in suspension |
| Custom tools + Gemini API keys | ✅ Yes | API key (Claude Console) | Commercial API usage — pay per token |
| OpenRouter + Gemini models | ✅ Yes | OpenRouter API key | Indirect access via gateway |
Terms snapshot checklist (as of Feb 2026)
Third-party access:
- OAuth tokens are personal-use only — explicitly prohibited in any third-party tool
- Even research/testing with OAuth tokens violates ToS
- Detection is automated; enforcement is immediate
- No warning system before suspension
- Recovery path exists for “unaware users” (no timeline specified)
Data handling:
- Antigravity has access to prompts and responses
- Data retention follows Google’s standard AI product policies
- Training opt-out available in account settings (verify current status)
Enterprise/commercial use:
- Gemini API via Google Cloud is the commercial path
- BAA available for healthcare use cases
- Vertex AI provides enterprise-grade access
Evidence / signals
- Official Antigravity Additional Terms of Service
- Google AI Developer Forum threads documenting ban wave
- Varun Mohan X post confirming “malicious usage” enforcement
- Multiple user reports of 403 ToS errors after OpenClaw authentication
- Google DeepMind spokesperson statement to VentureBeat
How to verify
- Read current Antigravity Terms of Service at
antigravity.google/terms - Check Google AI Developer Forum for recent policy announcements
- If unsure about a tool, assume it’s prohibited unless explicitly listed as authorized
- For custom tools, use Gemini API keys instead of OAuth
If your account was affected
- Check scope — Verify if only Antigravity is blocked or broader Google services
- Contact support — Use Google Cloud Support or
[email protected] - Document everything — Save error messages, support ticket numbers, dates
- Expect delays — Users report 1-2+ week response times
- Prepare alternative — Consider API keys or alternative providers while waiting
⚠️ Data Loss: What Happens to Your Work
Antigravity suspensions can result in lost work — here’s what you need to know.
What’s Lost When Suspended
| Data | Status | Recovery |
|---|---|---|
| Antigravity Chat History | ❌ INACCESSIBLE | No export available during suspension |
| Code Generated in IDE | ⚠️ AT RISK | Only saved if manually exported |
| Connected Project Files | ✅ SAFE | Stored in your Google Drive |
| Gmail/Calendar | ✅ UNAFFECTED | Normal access continues |
| Google Drive Files | ✅ SAFE | Separate from Antigravity |
The Critical Distinction
Good news: Google’s ban is surgical — only Antigravity is affected:
- ✅ Gmail works normally
- ✅ Google Drive is untouched
- ✅ Calendar, Docs, Sheets all functional
- ❌ Only Antigravity IDE access blocked
Bad news: Any work only in Antigravity (unsaved code, chat history) is inaccessible during suspension.
Can You Export During Suspension?
No. Once suspended:
- ❌ Cannot log into Antigravity IDE
- ❌ No self-service data export
- ❌ Chat history locked
- ✅ Project files in Drive remain accessible (if you saved them there)
Protect Your Work NOW
If you’re still using Antigravity:
Save everything to Drive
- Don’t rely on Antigravity’s workspace
- Explicitly save files to Google Drive
- Use “Export to Drive” for generated code
Screenshot critical conversations
- No chat export feature
- Copy important code blocks to local files
Switch to Gemini API keys
- Programmatic access = you control the data
- Store outputs locally, not in IDE
- See Google AI Studio
Use local version control
1 2 3 4# Commit anything important immediately git add . git commit -m "Backup work from Antigravity session" git push origin main
Recovery Timeline Reality Check
| Stage | Timeline | Your Data Status |
|---|---|---|
| Suspension | Immediate | Inaccessible |
| Appeal submitted | Day 0-1 | Still inaccessible |
| Response | 1-2 weeks | Still inaccessible |
| If restored | 2+ weeks | Access returns, history intact |
| If denied | Permanent | History lost (no export) |
Bottom line: If you have critical work in Antigravity, treat suspension as potential data loss. Save locally. Use API keys. Don’t rely on IDE persistence.
Comparison with Anthropic
| Aspect | Anthropic | |
|---|---|---|
| Enforcement | API error, account intact | Account suspension |
| Warning | None | None |
| Reversal | Accidental bans reversed | “Zero tolerance” — no reversals |
| Documentation | Published legal page | Forum posts only |
See Claude Code Terms for Anthropic’s policies.
What would invalidate this
- New Antigravity terms with different third-party language
- Official Google announcement of authorized third-party tools list
- Policy change with warning system implementation
- Any terms update with new effective date
Related links
Provider Policy Hub:
- /verify/openclaw-provider-policies/ — Complete provider policy comparison with risk ratings
- OpenClaw Provider Policy Check 2026 — Breaking news and migration guide
Risk Assessment:
- Google Antigravity OAuth Risk — Risk assessment and enforcement timeline
- Anthropic Claude Code Terms
- Anthropic Third-Party Access Risk
- OpenClaw Architecture Risk
- Verification Methodology
- Smart Spend Guide
- Free Frontier Stack
Sources
Primary Sources
- Google AI Developer Forum — Mass 403 ToS Bans thread — user reports and Google responses
- Varun Mohan (Google DeepMind) — X post — official explanation of enforcement
- OpenClaw GitHub — Issue #14203 — documentation of ban wave
News Coverage
- VentureBeat — Google clamps down on Antigravity malicious usage (Feb 23, 2026)
- The Register — Google Antigravity falls to Earth under OpenClaw-fueled compute load (Feb 23, 2026)
- Indian Express — Google bans Antigravity users over OpenClaw access (Feb 23, 2026)
Related Analysis
- OpenClaw.rocks — Google Suspended AI Users Over Third-Party Tools — detailed comparison with Anthropic
- OpenClaw.rocks — Anthropic Banned Third-Party Tools — economic analysis