P2 google-gemini-cli OAuth Provider Failed with 404/429, Then Silently Removed — No OAuth Replacement (#54891)

Executive Summary

The google-gemini-cli OAuth provider experienced two distinct runtime failures in early June, and after updating Hermes, the provider has been silently removed from both the setup UI and hermes auth known providers — with no visible OAuth replacement and no communication to users. No deprecation notice, no migration path, no documentation. Users are left guessing whether consumer Google OAuth is permanently dead or just temporarily missing. This is the 3rd distinct Gemini/provider regression we've tracked.

Failure Timeline

Phase 1: Initial Setup (Early June, Pre-Update)

User configured google-gemini-cli OAuth successfully. Login worked. Provider appeared configurable. Everything functional.

Phase 2: Runtime Failures

ModelErrorDetail
gemini-3.5-flash404HTTP 404 from cloudcode-pa.googleapis.com — model listed in Hermes but unavailable through the Code Assist backend
gemini-3.1-pro-preview429Responded briefly, then repeated HTTP 429 after very light usage: "Gemini quota exhausted. Your quota will reset after 19s...14s...7s"

The errors from cloudcode-pa.googleapis.com suggest Hermes was routing through the now-deprecated Code Assist backend. Google officially announced Gemini CLI and Code Assist IDE extensions stop serving consumer requests starting June 18, 2026, directing users to Antigravity CLI.

Phase 3: Silent Removal (After Hermes Update)

After updating Hermes, google-gemini-cli no longer appears in provider setup or hermes auth. No google-antigravity or Antigravity OAuth replacement visible. Only Google route remaining: gemini (API-key / AI Studio).

The Communication Gap

Hermes removed the broken provider but provided zero guidance:

What Users GotWhat Users Needed
Provider silently disappears from UI and CLIDeprecation notice explaining the removal
No alternative OAuth provider visibleMigration path to Antigravity OAuth or Gemini API key
Zero documentation or changelog mentionDocumentation explaining the Google OAuth provider landscape post-Code Assist sunset
Users left guessingClear statement: "google-gemini-cli OAuth is deprecated. Use gemini API key or Antigravity OAuth instead."

Impact Assessment

DimensionSeverityDetail
User TrustHIGHSilently removing a provider users configured and relied on — with zero communication — erodes trust in the platform's provider stability
Migration ExperienceHIGHNo migration path provided — users must discover alternatives through trial and error
Documentation QualityHIGHNo changelog entry, no deprecation notice, no migration guide — the removal is entirely undocumented
Workaround AvailabilityMODERATEUsers can switch to DeepSeek or use the gemini API-key provider — but must discover this independently
Fix ComplexityMODERATEProvider removal may be intentional (Code Assist sunset). Fix is documentation + migration path, not code.

Gemini/Provider Regression History (3 Distinct Issues)

IssueSeverityDateDescription
#49701P2Jun 20google-gemini-cli provider completely broken after Code Assist sunset
#51381P2Jun 23anthropic_messages/tools[] deserialization fails, silently falls back to wrong provider
#54891P2Jun 29google-gemini-cli silently removed with no OAuth replacement, no deprecation notice, no migration path

⚠️ Pattern: Three distinct Gemini/provider regressions in 9 days — from functional (Jun 20), to silent fallback (Jun 23), to silent removal (Jun 29). The provider layer is degrading without corresponding user communication. Each regression erodes confidence that "configured providers will continue to work."

Source Evidence

📋 https://hermes-agent.reviews/hermes-gemini-cli-oauth-silently-removed-54891.html
Tracked by hermes-agent.reviews — June 29, 2026