docs: note GEMINI_API_KEY requirement for the gemini backend#16
Merged
Conversation
Google is retiring the free Gemini CLI OAuth tier on June 18, 2026 (transitioning to Antigravity CLI). Update the troubleshooting note so users set GEMINI_API_KEY in the environment instead of the now-ending browser OAuth login; otherwise the gemini backend won't run. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Google is retiring the free Gemini CLI OAuth tier (Google AI Pro/Ultra/free) on June 18, 2026, transitioning users to Antigravity CLI. The previous "run
geminionce to authenticate via browser" guidance will stop working for those tiers after that date.This PR updates the README troubleshooting note only — no code changes.
Change
GEMINI_API_KEYin the environment, otherwise thegeminibackend won't run. The key is passed through to the spawned CLI via the inherited process environment, so no code change is needed.Notes
geminiis already listed last across the engine/support lists, so no reordering was needed.agy) is intentionally not adopted yet: it currently emits plain-text output only (no JSON/stream-json), which the backend integration depends on. Revisit onceagyships structured output.🤖 Generated with Claude Code