Skip to content
TheChatArchiveThe Chat Archive
Claudeclaude-sonnet-5· anthropicHugging Face ibragim-bad/swe_rebench_07_2026_trajectories

ISSUE DESCRIPTION gemini-cli: support Login with Google (oauth-personal), mirroring…

  1. User

    ISSUE DESCRIPTION

    gemini-cli: support Login with Google (oauth-personal), mirroring codex auth.json The codex agent 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), and claude-code accepts CLAUDE_CODE_OAUTH_TOKEN (#173). gemini-cli has no equivalent — it only wires GEMINI_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-cli agent, 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 from test_codex_auth.py, verified end-to-end (gemini-cli --ae GEMINI_FORCE_OAUTH=true completed 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 using git reset --hard command. Additionally, you can use git stash and git stash pop to temporarily save your changes and restore them later. Finally, you can see the changes that you've made (which will be submitted when you call submit) using git status or git diff commands. However you don't need to use git add or git commit before submitting your changes. In fact, submit only submits currently unstaged changes because it uses git diff to 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-$

  2. Claude Assistant

    Now let's look at gemini_cli.py agent.

  3. Claude Assistant

    Now let's look at the _get_env method in base.py and check gemini's oauth_creds.json format, then implement analog logic.

  4. Claude Assistant

    Let's check EnvironmentPaths usage in gemini_cli.py (it uses hardcoded /logs/agent) and PurePosixPath import for consistency with codex.

  5. Claude Assistant

    Now add the parse_bool_env_value import (from harbor.utils.env), right after the trajectories import block.

  6. Claude Assistant

    Now add the class-level constants for remote secrets dir, mirroring codex.

  7. Claude Assistant

    Now add the _resolve_oauth_creds_path method. Let's place it right before _build_settings_command or near _build_register_skills_command.

  8. Claude Assistant

    Now update _build_settings_command to accept and forward use_oauth:

  9. Claude Assistant

    Now let's add cleanup for the secrets dir in the finally block, mirroring codex's best-effort cleanup.

  10. Claude Assistant

    Now let's view the complete run() function to double-check correctness.

  11. Claude Assistant

    This looks good. Now let's verify by checking python syntax/compile:

  12. Claude Assistant

    Now let's check existing tests pass:

  13. Claude Assistant

    All pass. Now let's write a temporary reproduce/test script mirroring test_codex_auth.py tests to verify the new logic works correctly.

  14. Claude Assistant

    Good, temp_dir fixture exists. Let's create a temp test script to validate the new oauth logic (will delete after).

  15. Claude Assistant

    All 16 pass. Now clean up temp test file and rerun the full gemini test suite plus codex tests to ensure nothing broken.

  16. Claude Assistant

    All pass. Let's run the entire agents installed unit test suite for good measure, plus check for lint/type issues (ruff/mypy if configured).

  17. Claude Assistant

    All 695 tests pass. Let's check for ruff/lint configuration to keep code style consistent.

  18. Claude Assistant

    Let's view the final diff to confirm everything is clean and well formatted.

  19. Claude Assistant

    This diff looks clean and complete. Now let's check for documentation mentions (README or docs) referencing codex auth env vars that might need mirroring for gemini too.

  20. Claude Assistant

    No documentation references these env vars, so nothing to update there. Let's also check ENV_VARS mechanism used elsewhere in base.py (used by some agents) to see if this should be registered as an EnvVar descriptor instead of manual _get_env. Codex doesn't use it either, so we're consistent.

  21. Claude Assistant

    Neither uses ENV_VARS, consistent with codex's manual approach. Let's run full test suite one more time broadly to be safe, and check git status/diff summary.

  22. Claude Assistant

    All 2503 unit tests pass (1 skipped, unrelated). Let's view final git diff/status.

  23. Claude Assistant

    Only the intended file changed, no test files added/modified. Let's do a final review of the complete run method for correctness (particularly ensure the env dict passed into settings command doesn't accidentally leak API key vars when oauth used, and mkdir command ordering is right).

  24. Claude Assistant

    This all looks correct and mirrors the codex pattern well. Let's also double check install() still creates ~/.gemini/settings.json with experimental.skills at install-time — our run-time overwrite with use_oauth will replace that file entirely, but it already includes "experimental": {"skills": True} at the end of _build_settings_config, so that's preserved.

  25. Claude Assistant

    Good, confirmed. Now let's finalize and go through the checklist.

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.