Dear Antigravity Developer Relations, Support, and Engineering teams,
My account has been incorrectly disabled with an automated Terms of Service flag regarding Gemini CLI/Antigravity access. I am paid Google One: Google AI Pro user.
I have already submitted the official automated amnesty appeal form. Because that form only offered a restrictive checkbox with no field to add context, I also submitted a comprehensive ticket through the in-IDE “Provide Feedback” window (under “Auth and Billing”) within Antigravity. I am posting here just in case that feedback submission did not go through, as I did not receive an email confirmation that the feedback submission was submitted and was unable to attach my system logs due to the 403 restricted state blocking the upload process. (Although I did receive an on-screen popup message that the feedback was submitted; unsure what got submitted without an email receipt).
For context on my environment, I am intentionally running an older build (Antigravity Version: 1.23.2, VSCode OSS Version: 1.107.0) because I prefer the traditional, dedicated IDE setup. My local workflow runs on a Windows host utilizing a WSL Linux environment, where I manually operate native command-line interfaces, specifically the official Gemini CLI and Claude Code CLI. I operate exclusively using a Human-in-the-Loop (HITL) methodology. I have been incredibly careful from day one to adhere strictly to the Terms of Service. Throughout my installation and daily usage, I have consistently validated my local workflow directly with Gemini to ensure my HITL process remains completely compliant. If my interpretation of the ToS was incorrect in any way, I sincerely apologize; please know that I have acted in good faith and continuously consulted with Gemini to ensure I remained within the ToS. I do not use continuous automation, third-party wrappers, scraping tools, or unapproved API proxies; I believe the backend sweep simply misflagged my concurrent, manual WSL terminal activity and setup.
I am sharing a redacted text version of my terminal diagnostics to this post below, showing ‘which opencode’, ‘which openclaw’, and my proxy environment variables. This is to confirm that my local system is clean of any prohibited tools. Please refer to my internal “Provide Feedback” submission for additional context and the original terminal screenshot.
- Note: All the below returns as empty.
workspace [SSH: [username]@localhost] - Antigravity - bash
[username]@[…]:~/workspace$ which opencode
[username]@[…]:~/workspace$ which openclaw
[username]@[…]:~/workspace$ env | grep -i proxy
[username]@[…]:~/workspace$
- Could the engineering and supports team please check my submitted feedback and the submitted appeal form to confirm my compliance, and let me know the expected timeline for permanently lifting this false-positive restriction?
- Additionally, could you advise on any specific steps or configuration best practices I should follow to ensure that my HITL workflow is not incorrectly swept or flagged by your automated backend systems in the future?
Thanks so much in advance. Have a wonderful rest of the week.
NOTE: Minor edits above for clarity.