gemini-cli - 💡(How to fix) Fix [Auth] Gemini CLI OAuth disabled for Gemini Pro subscriber — no third-party tools used ([email protected]) [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
google-gemini/gemini-cli#25685Fetched 2026-04-20 12:15:25
View on GitHub
Comments
1
Participants
2
Timeline
2
Reactions
0
Timeline (top)
commented ×1labeled ×1

Error Message

I am a Gemini Pro subscriber facing a "Service Disabled" error when attempting to sign in to the official Gemini CLI via Google OAuth. Error message:

  • #19501, #18999, #20045 — same error, open

Root Cause

This was not caused by any actual ToS violation on my part.

Code Example

Failed to sign in. Message: This service has been disabled in this account for violation of Terms of Service.
RAW_BUFFERClick to expand / collapse

URL of the page with the issue

https://geminicli.com/

What is the problem?

I am a Gemini Pro subscriber facing a "Service Disabled" error when attempting to sign in to the official Gemini CLI via Google OAuth.

Error message:

Failed to sign in. Message: This service has been disabled in this account for violation of Terms of Service.

Affected account: [email protected] Subscription: Gemini Pro (active, via Google One AI Premium, 5 TB) Consumer Gemini at gemini.google.com: working normally Gemini API via AI Studio / Vertex keys: working normally Only the CLI OAuth sign-in is blocked.

Background & honest usage disclosure

To help triage, here is my complete usage history with Google AI products on this account:

  1. Gemini Web — regular paying-subscriber use.
  2. Gemini API via AI Studio / Vertex API keys — personal development.
  3. Official Antigravity (google.com product) — tried twice briefly, stopped before exhausting free trial.
  4. Gemini CLI — official google-gemini/gemini-cli only.

I have never used any third-party software, tool, plugin, or coding agent with Google product OAuth (no OpenClaw, no unauthorized CLI, no non-Google IDE integration). I am aware this would be a ToS violation per the official appeal form text quoted in #20813.

Verification: my myaccount.google.com/connections page shows only three connections with Cloud-related scopes, all of which are Google's own official products: "Gemini Code Assist and Gemini CLI", "Google Antigravity", and "Google Cloud SDK". No unauthorized third-party coding agent is connected.

Likely cause

I access Google services from Asia through a VPN/proxy for legitimate network reasons. I believe (a) brief Antigravity usage from a region where Antigravity is not broadly available, combined with (b) variable outbound IPs due to proxy routing, triggered an automated region/IP-based abuse-detection flag.

This was not caused by any actual ToS violation on my part.

What I'm requesting

Please forward this to the team with the ability to review and lift the OAuth suspension on my account. I have also emailed [email protected] with full details.

Related reports (for deduplication)

  • #25648 — near-identical case, Google Cloud Support routed user to antigravity.google/support
  • #20813 — official appeal form text and policy quoted
  • #19566 — similar case, closed / resolved (precedent that manual review can resolve this)
  • #19501, #18999, #20045 — same error, open

What did you expect to happen?

Official Gemini CLI OAuth sign-in to succeed for a legitimate paying Gemini Pro subscriber who has never used any third-party tools against Gemini OAuth.

Client information

<details> <summary>Client Information</summary>
  • OS: macOS 14.2.1 (Darwin 23.2.0)
  • Gemini CLI: latest (installed via npm/brew)
  • Auth method attempted: Sign in with Google
  • Network: Tokyo/Japan via VPN
</details>

Additional context

No response

extent analysis

TL;DR

The "Service Disabled" error on Gemini CLI OAuth sign-in is likely due to automated region/IP-based abuse-detection flags triggered by brief Antigravity usage from a restricted region and variable outbound IPs, and can be resolved by manual review and lifting the OAuth suspension.

Guidance

  • Verify that the account has no unauthorized third-party connections by checking the myaccount.google.com/connections page, as the user has already done.
  • Check the official appeal form text and policy quoted in #20813 to understand the Terms of Service violation detection criteria.
  • Since the user has already emailed [email protected] with full details, wait for the team's review and response to lift the OAuth suspension.
  • Consider providing additional context or information to support the manual review process, such as proof of legitimate usage and VPN/proxy configuration.

Notes

The issue seems to be related to automated abuse-detection flags, and manual review is required to resolve the issue. The user has already taken steps to verify their account connections and has reached out to the support team.

Recommendation

Apply workaround: Wait for the team's review and response to lift the OAuth suspension, as manual review can resolve this issue, as seen in #19566.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING