Skip to content

[Bug][Cursor] grok-4.5-fast dropped: live wire ids use trailing -fast after effort #731

Description

@chasehuh

Summary

Cursor GetUsableModels currently returns Grok Fast as:

  • cursor-grok-4.5-low-fast
  • cursor-grok-4.5-medium-fast
  • cursor-grok-4.5-high-fast

OpenCodex still assumes the older shape grok-4.5-fast-{medium,high,xhigh} (and builds wire ids that way). As a result:

  1. Live discovery marks grok-4.5-fast unavailable even when Fast is on the account.
  2. Selecting cursor/grok-4.5-fast would send grok-4.5-fast-high, which Cursor rejects (not_found).

Reproduction

  1. Cursor account with Grok 4.5 Fast unlocked (confirmed via raw GetUsableModels).
  2. ocx login cursor + ocx sync.
  3. Observe ocx models selected cursor / catalog: only grok-4.5, not grok-4.5-fast.

Evidence (redacted)

Raw usable Grok ids from GetUsableModels:

cursor-grok-4.5-high
cursor-grok-4.5-high-fast
cursor-grok-4.5-low
cursor-grok-4.5-low-fast
cursor-grok-4.5-medium
cursor-grok-4.5-medium-fast

isCursorModelAvailableForAccount("grok-4.5-fast", liveIds) → false on current main.
After matching trailing -fast, → true.

Expected

  • Catalog exposes cursor/grok-4.5-fast when Fast wire ids are present.
  • Requests map to grok-4.5-{effort}-fast.
  • Older grok-4.5-fast-{effort} live ids still count as available for compatibility.

Area

Provider adapter (Cursor)

Related

PR: #730

Checks

Activity

  1. github-actions commented on Jul 30, 2026

    @github-actions
    Contributor

    Issue closed: use an issue template

    Thanks for taking the time to submit this issue. It was closed automatically because it was not opened with a recognized issue template (Bug report, Feature request, Documentation, or Provider compatibility). Freeform and API-opened issues cannot skip this check.

    • This looks like a bug report but it does not use the Bug report template headings (for example Description/Log entry instead of Summary).

    Please edit the issue to add:

    • Use the Bug report template, or edit this issue to include: Client or integration, Summary, Reproduction, Version, and Operating system.
    • Retitling with [Bug]: and applying the bug label alone is not enough without those section headings filled in.

    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.

  2. github-actions commented on Jul 30, 2026

    @github-actions
    Contributor

    Automated translation bookkeeping — detected language: English.

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

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions