Skip to content

OAuth personal on 0.46.0 fails with UNSUPPORTED_CLIENT and Antigravity migration #28846

Description

@henrymodisett

What happened

The current Homebrew release of Gemini CLI exits before model execution when using an existing oauth-personal login:

reasonCode: UNSUPPORTED_CLIENT
reasonMessage: This client is no longer supported for Gemini Code Assist for individuals. To continue using Gemini, please migrate to the Antigravity suite of products

Some attempts then return rateLimitExceeded during _doSetupUser instead. The CLI cannot be used headlessly with the cached login.

Reproduction

Environment:

  • Gemini CLI 0.46.0 (current Homebrew stable)
  • macOS
  • security.auth.selectedType = oauth-personal
  • no GEMINI_API_KEY, Vertex credential, or Cloud project environment variables

Command:

gemini --prompt "Reply only READY" --model pro --output-format text --approval-mode yolo --skip-trust

The process exits 1 before any model response.

Expected

The documented personal Google login works with the current CLI, including headless use when credentials are already cached, or the CLI provides a supported non-destructive migration/reauthentication instruction that keeps the CLI usable.

Impact

This blocks a versioned cross-driver steering evaluation from collecting required live Gemini evidence. The harness correctly fails fast and does not treat the provider failure as a passing or quota-skipped trial. Offline transport tests cannot substitute for the required live model run.

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions