Gemini CLI account suspended (403 ToS) for several months - 3-5 appeals submitted, zero response

Google Antigravity
,
1

Hi @jackwotherspoon and Gemini CLI team,

Posting here after multiple unanswered appeal form submissions, hoping for a manual look since my case seems to have fallen through the cracks of the automated reinstatement process described in Discussion #20632.

Summary:

  • Affected: Gemini CLI (confirmed via gemini -p "hello" failing with 403)
  • Suspension started: several months ago (exact date unknown)
  • Appeals submitted via the in-CLI appeal form: 3-5 times, no confirmation email, case ID, or response ever received
  • Most recent reproduction: 2026-08-29 12:58:32 GMT, endpoint cloudcode-pa.googleapis.com/v1internal:loadCodeAssist, trace ID 917739ab6c48****, error: “This service has been disabled in this account for violation of Terms of Service.”

What I’ve already done:

  • Acknowledged that I had used a third-party tool that accessed Gemini CLI/Antigravity via OAuth login, which I now understand violates the ToS
  • Revoked all third-party OAuth app connections at myaccount.google.com/permissions
  • Removed all third-party CLI wrappers/tools
  • Will only use the official gemini-cli login or an official API key going forward

Given it’s been months with the standard appeal form producing no visible response, could someone confirm whether this case is:

  1. still pending manual review,
  2. missed by the periodic automated reinstatement sync, or
  3. classified as a permanent ban

I’m happy to share my account email and any additional logs/trace IDs privately (DM) if that helps identify the case. Any guidance on how to get this actually looked at would be greatly appreciated.

Thanks!