Skip to content

Migrate Gemini CLI provider integration to Antigravity with multi-account support #17345

Open

Description

@AmethystLiang

Summary

Orca still presents and depends on the deprecated Gemini CLI provider in parts of Agent Settings and AI Provider Account Settings. Google has moved this workflow to Antigravity CLI, so Orca should migrate the user-facing provider and integration accordingly.

Requested changes

  • Rename Gemini model/provider references in Agent Settings and AI Provider Account Settings to Antigravity.
  • Support adding, selecting, and persisting multiple Antigravity accounts.
  • Replace the legacy Gemini CLI OAuth extraction and setup copy with Antigravity CLI support.
  • Remove or deprecate remaining Gemini CLI code and references.
  • Add a pull request for the Gemini CLI deprecation work and credit the original relevant code contribution to GitHub user @siddqamar.

Reference

Expected result

Antigravity should be the supported Google CLI provider throughout Orca, with real quota/account handling and no dependency on the discontinued Gemini CLI.

Activity

  1. pullfrog commented on Aug 30, 2026

    @pullfrog
    Contributor
  2. added theissue type on Sep 19, 2026
  3. nwparker commented on Sep 19, 2026

    @nwparker
    Contributor

    Verification and merge review, 2026-09-20. All 22 PR check rollups are green; no PR was merged or promoted. Heads are unchanged from the previous audit, plus new #21770 at b4e4c264e95.

    These are stacked PRs. “Approve” below is my recommendation for that scoped diff, not an independent merge instruction or a GitHub approval. Merge in dependency order; #21660 is held, so its descendants need restacking to merge without it. #21657 needs #21770 for the demonstrated slow-Windows-startup case. No human review approval is recorded. GitHub reports all 22 comparisons MERGEABLE after #21606 finished recomputing.

    PR User-facing change Verification Scoped verdict
    #21606 Current models and configured defaults for source-control generation Actual commit-message, branch-name and PR-text generation on macOS + Windows; compatibility regressions Approve
    #21613 Wait for the actual empty agy composer Captured-screen regressions; live trust/draft/ready checks, Windows reload Approve
    #21628 Report missing hook scripts accurately 54 tests; rendered hook-health states Approve
    #21634 Bound abandoned POSIX hook input Real-process tests; seven real payloads replayed byte-for-byte Approve; live replacement POSIX hook loading unverified
    #21635 Launch POSIX hooks through an explicit shell 41 tests, executable/path cases Approve wrapper fix; ACP recovery unverified
    #21636 Avoid falsely marking agy done on Escape 63 renderer/host tests; four regressions failed before fix Approve
    #21638 Match CLI history by conversation ID Real CLI history and parser regressions Approve CLI scope; IDE sample pending
    #21640 Resolve folder-workspace history and resume targets 67 tests; real folder navigation Approve; path aliases remain separate
    #21647 Discover native agy skills 47 tests and real local discovery Approve
    #21650 Install skills into native agy locations 107 tests, real local folder install, old-host refusal Approve; live remote install unverified
    #21653 Configure custom agy commands; update setup docs Real custom-path launch; 86 tests; rendered docs Approve
    #21654 Read native quota independently of Gemini OAuth 201 tests; actual populated quota rendered Approve with #21678
    #21655 Address Antigravity orchestration groups 72 tests; live group enqueue Approve; group consumption not independently proven
    #21656 Offer the official installer during onboarding 96 tests; actual macOS UI; fresh WSL installer/checksum passed Approve installer scope; WSL auth blocked
    #21657 Deliver continuation after composer readiness 107 tests; actual successful macOS and Windows dialog flows at fixed stack head Approve only with #21770
    #21660 Render agy sessions in experimental Chat 139 tests; real Windows hooks, composer reply and post-tool completion HOLD: command approval invisible in Chat
    #21664 Accept the agy worker alias 34 tests; successful authenticated worker Approve after restacking around held Chat
    #21666 Exercise real Windows hook launcher processes Windows CI: 477 passed/22 skipped; both new agy cases ran; native awin suite passed Approve after restacking
    #21672 Preserve worker model and effort choices 77 tests; real model/high-effort worker settled successfully Approve after restacking
    #21678 Honor configured quota executable and visibility Resolver/UI tests; actual two-bucket Usage menu Approve after restacking
    #21682 Prefer agy and label Gemini setup as legacy 218 tests; rendered settings; legacy preferences/resume preserved Approve scoped deprecation after restacking
    #21770 Retain continuation through slow Windows PTY startup Before failure at 8307 ms; fixed real dialog passed at 8330 ms; 60 tests on macOS + Windows Approve with #21657 after restacking

    New live evidence:

    Remaining outside these scoped approvals: multi-account Accounts implementation, IDE history (dedicated IDE profile still needs Google sign-in), authenticated WSL execution, direct-SSH Chat support, and the overnight Windows/Tailscale freeze. CLI API-key auth on native Windows works after refreshing the process environment. WSL confirms key presence but still requests Google sign-in; no credentials or OAuth URLs are published. A brief renderer reload is not an overnight reconnect test.

    The temporary Windows Chat terminal/app are stopped. Hook before/after script snapshots match and original global hook config is unchanged. Installed user Orca and dedicated IDE profile are preserved. No issues should be closed as “migration complete.”

  4. nwparker commented on Sep 19, 2026

    @nwparker
    Contributor

    Draft #21682 now addresses the setup-deprecation portion of this issue, with the requested acknowledgment to @siddqamar.

    Gemini CLI is labeled legacy in Agents and Accounts; the Accounts explanation points new sessions toward Antigravity and makes clear that Gemini credentials do not sign users into agy. Automatic selection prefers Antigravity when both Google CLIs are available, while explicit Gemini choices, history, and resume support remain intact.

    218 focused tests, full typecheck and changed-code quality passed. The draft includes actual hidden Electron before/after screenshots. It deliberately retains legacy compatibility rather than adopting #12789’s session/usage removal. This does not implement Antigravity account sign-in or multi-account switching, and does not establish authenticated generation; those requirements remain open. CI is pending.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions