ISSUE DESCRIPTION gemini-cli: support Login with Google (oauth-personal), mirroring…
- User
ISSUE DESCRIPTION
gemini-cli: support Login with Google (oauth-personal), mirroring codex auth.json The
codexagent injects a cached OAuth credential (~/.codex/auth.json) so runs can use a login instead of an API key (CODEX_AUTH_JSON_PATH/CODEX_FORCE_AUTH_JSON), andclaude-codeacceptsCLAUDE_CODE_OAUTH_TOKEN(#173).gemini-clihas no equivalent — it only wiresGEMINI_API_KEY/ Vertex env, so users with a "Login with Google" session (~/.gemini/oauth_creds.json) must keep a separate API key for runs.Proposal: add the same opt-in OAuth-credential injection to the
gemini-cliagent, mirroring the codex pattern —GEMINI_OAUTH_CREDS_PATH/GEMINI_FORCE_OAUTH, default behavior unchanged (fully backward-compatible).I have a working implementation that mirrors the codex auth flow (
_resolve_oauth_creds_path→ upload → chown →~/.gemini) with tests ported 1:1 fromtest_codex_auth.py, verified end-to-end (gemini-cli --ae GEMINI_FORCE_OAUTH=truecompleted hello-world, reward 1.0). Happy to open the PR or hand it off — whichever you prefer.Interface
No new interfaces are introduced.
ADDITIONAL ADVICE
Since you are given a git repository, you can use git commands to simplify your work. For example, if you made a mistake and want to revert your changes, you can use
git checkout <file>to restore the file to its original state. You can also reset all changes in the repository usinggit reset --hardcommand. Additionally, you can usegit stashandgit stash popto temporarily save your changes and restore them later. Finally, you can see the changes that you've made (which will be submitted when you callsubmit) usinggit statusorgit diffcommands. However you don't need to usegit addorgit commitbefore submitting your changes. In fact,submitonly submits currently unstaged changes because it usesgit diffto get the changes that need to be submitted.CHECKLIST
Before submitting your solution, please go over the following checklist and make sure you've done everything:
- If an error was reported in the issue description, I have successfully reproduced it.
- If an error was reported in the issue description, I have confirmed that my fix resolves the error.
- I have thought about edge cases and made sure my fix handles them as well.
- I have run existing tests in the repository that might have been affected by the change I made and confirmed that they pass. I want you to list every bullet from this checklist and write your reasoning for why you think you did it or didn't need to.
Repository has been uploaded and your shell is currently at the repository root. Time to solve the issue!
(Current directory: /harbor, current file: none) bash-$
- Assistant
I'll start by exploring the repository structure and the existing codex OAuth auth pattern so we can mirror it for gemini-cli.
- Assistant
Next I'll inspect the codex auth flow and the current gemini-cli agent implementation.
- Assistant
Let me read the codex auth implementation and tests, and the gemini_cli agent.
- Assistant
Let me search for the OAuth/auth related code in codex.py
- Assistant
Let me read the relevant sections of both files in full.
- Assistant
Let me continue reading the rest of the files.
- Assistant
Let me read the gemini-cli
runmethod and remaining codex auth tests. - Assistant
I'll also check claude-code OAuth handling and review env helpers.
- Assistant
Let me check the codex cleanup and what gemini expects for oauth_creds.json path.
- Assistant
I have a clear plan: mirror codex's OAuth injection in gemini-cli with
GEMINI_OAUTH_CREDS_PATH/GEMINI_FORCE_OAUTH. Implementing that next. - Assistant
The open file window has moved. Let me open the file at line 1.
- Assistant
Let me apply the import changes and add the constant and method.
- Assistant
Next I'll add the secrets-dir constant and the OAuth resolve helper.
- Assistant
I'll add
_resolve_oauth_creds_pathand update therunmethod. - Assistant
Let me replace the section from
_build_settings_commandend through the end ofrunto add oauth resolution and injection. - Assistant
I need to navigate to the line first
- Assistant
I'll use line-range edits for a more reliable update.
- Assistant
Let me review the rest of the run method, then write a temporary test script.
- Assistant
I'll write a temporary verification script based on the codex auth tests and run it.
- Assistant
Let me find the temp_dir fixture in tests.
- Assistant
Running the temporary tests with the repo conftest:
- Assistant
I'll switch the temp suite to
tmp_pathand rerun. - Assistant
The sed doubled
tmp_path. Let me rewrite the file properly. - Assistant
All 17 tests passed. Running the existing gemini-cli tests next.
- Assistant
All related tests passed. Checking the diff and cleaning up the temporary test file.
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.
Identical first prompt
claude-sonnet-5Compare side by side →
claude-sonnet-5Compare side by side →
claude-sonnet-5Compare side by side →
claude-sonnet-5Compare side by side →
claude-sonnet-5Compare side by side →
Qwen/Qwen3.6-35B-A3BCompare side by side →
Qwen/Qwen3.6-35B-A3BCompare side by side →
Qwen/Qwen3.6-35B-A3BCompare side by side →
Qwen/Qwen3.6-35B-A3BCompare side by side →
Qwen/Qwen3.6-35B-A3BCompare side by side →
Qwen/Qwen3.5-35B-A3BCompare side by side →
Qwen/Qwen3.5-35B-A3BCompare side by side →