[Bug] Cursor Muse Spark 1.3 missing from catalog despite successful live discovery #4820

Client or integration

OpenCodex dashboard

Area

Catalog / models

Summary

Muse Spark 1.3 is absent from the Cursor model list in OpenCodex 2.56.0 even though Cursor's live GetUsableModels response for the configured account includes six Muse Spark 1.3 reasoning variants.

Expected: preserve models returned by successful live discovery, including model names absent from the static catalog. Muse Spark 1.3 should appear under Cursor with its supported reasoning-effort mappings.

Actual: the dashboard and /api/models have no Cursor Muse row. Live discovery succeeds, but the configured/static Cursor catalog has no Muse entry, and discovery only filters that existing catalog.

Reproduction

1. Use OpenCodex 2.56.0 with an authenticated Cursor provider (adapter: "cursor", authMode: "oauth", baseUrl: "https://api2.cursor.sh"). Cursor model discovery is enabled.
2. Open http://localhost:10100/#models, select Cursor, and search for Muse.
3. Observe no Muse entry; /api/models likewise contains no Cursor Muse model.
4. Call the installed adapter's fetchCursorUsableModels using the configured account's resolved credential, without printing the credential. The discovery call succeeds and returns the Muse variants below.

Version

@bitkyc08/opencodex 2.56.0; bundled Bun 1.4.2.

Operating system

macOS 27.0 (26A428), arm64.

Provider and model

Cursor / Muse Spark 1.3 (muse-spark-1.3-*).

Logs or error output

Sanitized results from a direct discovery check on 2026-09-16:

{
  "ok": true,
  "count": 223,
  "muse": [
    "muse-spark-1.3-minimal",
    "muse-spark-1.3-low",
    "muse-spark-1.3-medium",
    "muse-spark-1.3-high",
    "muse-spark-1.3-xhigh",
    "muse-spark-1.3-max"
  ]
}

The running gateway's /api/selected-models reports liveModelCounts.cursor: 223, but its available Cursor list contains 40 rows and no Muse. Both the provider's configured models and CURSOR_STATIC_MODELS contain no Muse entry. The difference between 223 wire variants and 40 base rows is not itself the bug; Muse's omission is.

Screenshots and supporting files

Source trace for v2.56.0:

• provider-models.ts, Cursor discovery branch calls filterCursorConfiguredModelsByLiveDiscovery(configured, liveResult.models) on a successful discovery.
• discovery.ts, configured-model filter returns configured.filter(...), so a model missing from the seed/configuration cannot be added by live discovery.
• The Cursor catalog and effort mappings have no Muse definition in the installed version.

Requested behavior: treat successful live discovery as the source of available model names, rather than intersecting it with a static allowlist. The static catalog can enrich known models with capabilities, display names, and reasoning mappings, but an unfamiliar name alone should not cause a live-discovered model to disappear.

Grouping known reasoning variants into a base-model row is useful and should remain. For unfamiliar families, preserve the exact upstream IDs until their grouping and capabilities can be resolved, without inventing unsupported metadata. Any deliberate exclusion for a known incompatibility should be explicit and diagnosable.

Adding Muse Spark 1.3 and its wire-effort mappings would address the immediate omission, but a Muse-only catalog patch would leave the same failure mode for the next new model. Please add regression coverage showing that an unknown model returned by successful live discovery remains visible, alongside coverage for the Muse variants above.

This report verifies discovery and catalog omission only. No Muse inference request was made, so successful generation through the Cursor adapter is not claimed.

Redacted configuration

Relevant provider fields only; credentials omitted:

{
  "providers": {
    "cursor": {
      "adapter": "cursor",
      "authMode": "oauth",
      "baseUrl": "https://api2.cursor.sh"
    }
  }
}

Checks

• I searched existing issues and documentation/source comments.
• I removed secrets, tokens, account details, request credentials, and personal data.