Skip to content

[Bug]: v2.15.1 drops gemini-3.7-flash from Antigravity live discovery on macOS #1683

Description

@mkarolczyk

Client or integration

Codex CLI

Provider or upstream service

Google Antigravity

OpenCodex version

2.15.1

Endpoint or capability

model discovery / live catalog for google-antigravity

Current behaviour

On macOS, Google Antigravity is connected and configured with default model gemini-3.7-flash, but OpenCodex v2.15.1 drops the model from the authoritative live catalog and Codex model picker. The picker reports 1/5 visible and exposes gemini-3.1-pro, but not gemini-3.7-flash. Restarting the proxy and syncing the catalog do not change the result.

Expected behaviour

OpenCodex should retain and expose gemini-3.7-flash when it is configured and available in the connected Antigravity IDE/account. If live discovery returns 404 or a partial catalog, the proxy should surface that diagnostic and preserve configured models instead of silently removing them.

Minimal redacted request or reproduction

Environment: macOS 27.0 (26A5406e), OpenCodex 2.15.1, Google Antigravity OAuth provider.

1. Configure provider google-antigravity with base URL https://daily-cloudcode-pa.googleapis.com and default model gemini-3.7-flash.
2. Confirm the provider UI reports Connected.
3. Run:

    ocx restart
    ocx sync
    ocx health --json
    ocx models live --provider google-antigravity --json

4. Open the Codex model picker and inspect Google Antigravity models. The account identifier is redacted in the screenshots.

Actual response or error

ocx health --json: {ok:true, port:10100}.

Live discovery returns only:

    claude-opus-4-6-thinking
    claude-sonnet-4-6
    gemini-3.1-flash-image
    gemini-3.1-pro
    gpt-oss-120b-medium

The configured gemini-3.7-flash model is omitted. The provider overview simultaneously shows Connected and Default model gemini-3.7-flash. The issue reproduces after both restart and sync.

Upstream documentation

https://ai.google.dev/gemini-api/docs/latest-model

Suggested mapping or implementation notes

Related work: #1646 adds the 3.7 tier mapping; #1658 adds live tiered-model discovery and was merged after the v2.15.1 release tag. Please confirm whether the fix is included in the next release and whether partial/404 discovery should preserve configured models.

Additional context and attachments

Related reports: #1654 and #1671 were closed before complete reproduction details were supplied. This report intentionally includes the exact commands and actual live catalog output. Attached screenshots are redacted; they show the 1/5 visible picker and the connected provider with Default model gemini-3.7-flash.

Image Image

Checks

  • I searched existing provider and compatibility issues.
  • The request and response were redacted.
  • The expected behaviour is based on an upstream specification or a concrete client requirement.

Metadata

Metadata

Assignees

No one assigned

    Labels

    account-poolOAuth, credentials, Codex pool, quota, failover, plansbugSomething isn't workingplatformOS/service/tray/ACL (Windows-heavy, not Windows-only)providerProvider adapters, OpenAI-compat presets, upstream API quirksprovider-compatibilityProvider compatibility reports

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions