hermes - 💡(How to fix) Fix google-gemini-cli provider: Gemini CLI / Code Assist sunsets for consumer tiers on 2026-06-18 [1 pull requests]

Heads-up

Google has announced that Gemini CLI is being transitioned to Antigravity CLI:

June 18, 2026 — Gemini CLI and Gemini Code Assist IDE extensions stop serving requests for free and paid consumer tiers.

Source: https://developers.googleblog.com/an-important-update-transitioning-gemini-cli-to-antigravity-cli/

Impact on hermes-agent

The google-gemini-cli provider authenticates via the Gemini-CLI-era OAuth client and routes through Code Assist (cloudcode-pa://google). Both fall under that sunset, so google-gemini-cli will stop working for free/Pro (Google One AI) users on 2026-06-18.

• Consumer tiers (free, Google AI Pro / Google One) — affected. This is the path most desktop users hit.
• Enterprise (paid Gemini Code Assist license) — the announcement says these keep Gemini CLI access, so likely unaffected.

Antigravity CLI is the successor and reportedly continues to support Google One / AI Pro subscriptions — so the access survives, but the OAuth client / endpoint / credentials hermes-agent uses may need to change to match Antigravity.

Suggested action

Before 2026-06-18, google-gemini-cli likely needs to be updated (or joined by an antigravity provider) to track whatever auth + endpoint Antigravity CLI uses for consumer plans. Worth confirming:

1. Does Antigravity CLI reuse the same cloudcode-pa Code Assist backend with a new OAuth client, or a new endpoint entirely?
2. Do existing auth.json credentials for google-gemini-cli carry over, or do users need to re-authenticate?

Filing now so it's on the radar — the window is ~4 weeks. Happy to help test against an updated flow.

Context: this surfaced while wiring the google-gemini-cli provider into Hermes Desktop (sign-in + model discovery).