docs: warn that personal Google login is blocked on the Gemini CLI path

Google now rejects personal Google accounts on the Gemini CLI OAuth login
("This client is no longer supported for Gemini Code Assist for individuals").
The setup docs previously sent every user down "Sign in with Google" with no
warning. Note the block, recommend GEMINI_AUTH=apikey for personal accounts,
and clarify that real-time search fail-opens to DDG/Brave/Wikipedia regardless.

Docs only; no runtime default change.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This commit is contained in:
javis-bot
2026-06-22 19:44:12 +09:00
parent 5b6a67963a
commit da27c5a306
2 changed files with 14 additions and 2 deletions

View File

@@ -102,8 +102,15 @@ STREAM_BROWSER=true
# oauth = use the Gemini CLI with a Google-account login (no API key).
# Install once: npm i -g @google/gemini-cli ; then run `gemini` and
# "Sign in with Google". Uses the CLI's built-in web-search grounding.
# apikey = legacy REST path; needs GEMINI_API_KEY below
# (get one at https://aistudio.google.com/app/apikey).
# NOTE (2026-06): Google is blocking personal Google accounts on this
# path ("This client is no longer supported for Gemini Code Assist for
# individuals"). Workspace/org accounts may still work; personal
# accounts should use apikey below instead.
# apikey = REST path; needs GEMINI_API_KEY below
# (get one at https://aistudio.google.com/app/apikey). Recommended for
# personal Google accounts now that individual OAuth login is blocked.
# Either way, real-time search fail-opens to DDG/Brave/Wikipedia if Gemini is
# unavailable, so this is optional, not required.
GEMINI_AUTH=oauth
GEMINI_API_KEY=
GEMINI_MODEL=gemini-2.0-flash