Skip to content

Antigravity discovery drops gemini-3.7-flash from the OpenCodex model catalog #1671

Closed as not planned

Description

@stkbgrhn

Client or integration

Codex CLI and Codex IDE through the OpenCodex proxy.

Provider or upstream service

Google Antigravity OAuth provider.

OpenCodex version

v2.15.0

Client versions

  • Windows Codex CLI: v0.146.0
  • Ubuntu server Codex CLI: v0.147.0

Current behaviour

Gemini 3.7 Flash is available in the Antigravity IDE, but it does not remain visible/selectable in the OpenCodex model picker.

OpenCodex recognizes the model during migration: previous Gemini Flash IDs such as google-antigravity/gemini-3.6-flash are renamed to gemini-3.7-flash. However, the provider model discovery step then removes it from the authoritative live catalog.

Relevant redacted logs

Windows:

[model-rename-migration] renamed "google-antigravity/gemini-3.6-flash" to "gemini-3.7-flash" in the saved config
[opencodex] Provider model discovery for "google-antigravity" omitted configured model ids; dropping them from the authoritative live catalog: gemini-3.7-flash.

Ubuntu server:

[opencodex] Provider model discovery for "google-antigravity" failed with HTTP 404 [urlClass=provider-models, fallback=configured].
[model-rename-migration] renamed "google-antigravity/gemini-3.6-flash" to "gemini-3.7-flash" in the saved config
[opencodex] Provider model discovery for "google-antigravity" omitted configured model ids; dropping them from the authoritative live catalog: gemini-3.7-flash.

Steps to reproduce

  1. Install OpenCodex v2.15.0.
  2. Log in to the Google Antigravity provider using OAuth.
  3. Open the model picker or run provider model sync.
  4. Observe that gemini-3.7-flash is not listed.
  5. Inspect the service log and observe that the configured model is dropped after provider discovery.

Expected behaviour

If Antigravity exposes gemini-3.7-flash to the logged-in IDE/account, OpenCodex should retain and expose the model, or at least keep a configured model when the provider discovery endpoint returns 404/omits it.

Actual behaviour

The model is recognized and migrated in the saved configuration, but it is removed from the authoritative live catalog because provider discovery returns 404 or omits the model.

Suggested implementation notes

Please consider treating provider discovery failure/partial results as non-authoritative for already configured models, or adding an explicit compatibility mapping/allowlist for google-antigravity/gemini-3.7-flash. The model is available in Antigravity IDE but is currently unusable through the OpenCodex picker.

Upstream documentation

No public Antigravity provider-model discovery specification was found. The model is confirmed available in the Antigravity IDE.

Activity

  1. coderabbitai commented on Aug 14, 2026

    @coderabbitai
    Contributor
    ⚠️ Possible Duplicate Issue(s)
    🔗 Related PRs

    #354 - fix(models): surface discovery failure status when /v1/models returns 401 (#329) [open]
    #355 - feat(google): enable Gemini inline image output [merged]
    #1178 - fix(google): discover Antigravity live models [merged]
    #1646 - feat(google-antigravity): unlock gemini-3.7-flash tier [open]
    #1658 - fix(antigravity): discover live tiered models from CCA [open]


    📝 Issue Planner

    Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.

    • Create Plan

    🧪 Issue enrichment is currently in open beta.

    To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

    issue_enrichment:
      auto_enrich:
        enabled: false

    💬 Have feedback or questions? Drop into our discord!

  2. added
    catalogModel catalog, slugs, visibility, routed entries
    providerProvider adapters, OpenAI-compat presets, upstream API quirks
    on Aug 14, 2026
  3. github-actions commented on Aug 14, 2026

    @github-actions
    Contributor

    Issue closed: insufficient detail

    Thanks for taking the time to submit this issue. It was closed automatically because the structured report is missing information needed to evaluate or reproduce it.

    • Both the request/reproduction and the actual response/error are absent.

    Please edit the issue to add:

    • Include at least a minimal redacted request or the actual error output.

    See the Contributing guide for details.

    Once the report passes the automated checks, it will be reopened automatically unless a maintainer has changed its state.

  4. mkarolczyk commented on Aug 14, 2026

    @mkarolczyk

    Additional reproduction details from macOS:

    • OpenCodex: v2.15.1
    • OS: macOS 27.0 (26A5406e)
    • Provider: Google Antigravity, connected
    • Configured default model: gemini-3.7-flash

    Commands run after the original report:

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

    The proxy remained healthy (ok=true, port=10100), but live discovery still returned only:

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

    gemini-3.7-flash was omitted. The attached redacted screenshots show the same contradiction: the provider overview is Connected and has Default model gemini-3.7-flash, while the model picker reports 1/5 visible and does not list gemini-3.7-flash.

    This confirms the issue on macOS and OpenCodex 2.15.1, after both restart and sync.

    Image Image
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

    catalogModel catalog, slugs, visibility, routed entriesproviderProvider 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