fix(adapters/gemini-local): downgrade missing API key to info level
The Gemini CLI supports OAuth login via `gemini auth login` which stores credentials locally without setting any env vars. The previous warn-level check on missing GEMINI_API_KEY caused false alarms when CLI-based OAuth was used. The hello probe that follows is the real auth authority — if auth is actually broken, it will catch it and report appropriately. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -113,9 +113,9 @@ export async function testEnvironment(
|
|||||||
} else {
|
} else {
|
||||||
checks.push({
|
checks.push({
|
||||||
code: "gemini_api_key_missing",
|
code: "gemini_api_key_missing",
|
||||||
level: "warn",
|
level: "info",
|
||||||
message: "No Gemini API key was detected. Gemini runs may fail until auth is configured.",
|
message: "No explicit API key detected. Gemini CLI may still authenticate via `gemini auth login` (OAuth).",
|
||||||
hint: "Set GEMINI_API_KEY or GOOGLE_API_KEY in adapter env/shell, run `gemini auth` / `gemini auth login`, or set GOOGLE_GENAI_USE_GCA=true for Google account auth.",
|
hint: "If the hello probe fails with an auth error, set GEMINI_API_KEY or GOOGLE_API_KEY in adapter env, or run `gemini auth login`.",
|
||||||
});
|
});
|
||||||
}
|
}
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user