Skip to content

fix(gemini-adapter): detect new ~/.gemini/oauth_creds.json auth path#1362

Open
abigail-atheryon wants to merge 1 commit intogarrytan:mainfrom
abigail-atheryon:fix/gemini-oauth-path
Open

fix(gemini-adapter): detect new ~/.gemini/oauth_creds.json auth path#1362
abigail-atheryon wants to merge 1 commit intogarrytan:mainfrom
abigail-atheryon:fix/gemini-oauth-path

Conversation

@abigail-atheryon
Copy link
Copy Markdown

@abigail-atheryon abigail-atheryon commented May 7, 2026

Summary

gemini-cli >=0.30 stores OAuth credentials at ~/.gemini/oauth_creds.json instead of the legacy ~/.config/gemini/ directory. The benchmark adapter's availability check still only looks at the legacy path, so users who have authenticated with a recent gemini-cli see NOT READY — No Gemini auth found even though the CLI itself works fine.

This patch accepts either path, so older and newer installs both succeed.

Repro before fix

$ gemini   # cached credentials load fine
$ ~/.claude/skills/gstack/bin/gstack-model-benchmark --prompt unused --models gemini --dry-run
  gemini: NOT READY — No Gemini auth found.

~/.config/gemini/ does not exist; ~/.gemini/oauth_creds.json does.

After fix

  gemini: OK

Verified end-to-end with a real benchmark run (gpt + gemini, 11.5s, no auth errors).

Test plan

  • Dry-run shows gemini: OK on a host with only ~/.gemini/oauth_creds.json
  • Real benchmark run completes without auth errors
  • Verify legacy ~/.config/gemini/ path still detected (unchanged code path; trusting OR semantics)

🤖 Generated with Claude Code


View in Codesmith
Need help on this PR? Tag @codesmith with what you need.

  • Let Codesmith autofix CI failures and bot reviews

gemini-cli >=0.30 stores OAuth credentials at ~/.gemini/oauth_creds.json
instead of the legacy ~/.config/gemini/ directory. The benchmark adapter's
availability check now succeeds for users on recent gemini-cli releases
who have authenticated via interactive login.

Both paths are accepted so users on older versions still work.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant