Selecting any model still fails with Invalid parameters for registry model: "grok-4.7"

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

In Cursor IDE Agent chat, after Grok 4.7 is selected once, switching the model picker to any other model still fails immediately. The toast is always:

AI Model Not Found
Invalid parameters for registry model: “grok-4.7”

This happens even when the picker shows a different model (Grok 4.5, GLM, etc.). Local logs show model_intent changes (glm-5p3, grok-4.5, grok-4.7) but buildRequestedModel still uses catalogModelId=grok-4.7 / selectedModelIds=grok-4.7 from selectedModels[0]. The server then returns ERROR_BAD_MODEL_NAME with actionRequired=config, isRetryable=false.

Related SDK thread (500k context param): Grok-4.7 run rejects advertised context 500k
This report is Cursor IDE Agent, and the picker switch does not actually change the requested registry model.

Steps to Reproduce

  1. Open Cursor IDE 3.22.12 on macOS (unified Agent layout).
  2. In Agent chat, select Grok 4.7 and send any message.
  3. Observe toast: AI Model Not Found / Invalid parameters for registry model: “grok-4.7”.
  4. Switch the picker to Grok 4.5 or GLM and send another message.
  5. The same toast still appears. Agent does not run.
  6. Repeat with a new chat: same error as long as selectedModels[0] stays grok-4.7.

Expected Behavior

Selecting Grok 4.7 should either run with a valid registry parameter set, or the picker should not offer an invalid combination. Switching to another model should send that model, not keep grok-4.7 from selectedModels[0].

Operating System

MacOS

Version Information

Version: 3.22.12
VSCode Version: 1.128.0
Commit: 3a92974361033b2051526321308c2740fe5912c0
Date: 2026-09-26T04:55:12.125Z
Electron: 42.10.0
OS: Darwin arm64 24.6.0 (macOS 15.7.9)
Layout: unifiedAgent
Channel: stable
Region: ap-southeast-1

For AI issues: which model did you use?

Picker tried: Grok 4.7, Grok 4.5, GLM (glm-5p3).
Actual requested registry model stayed grok-4.7 (selectedModels[0]).

For AI issues: add Request ID with privacy disabled

d6a946b1-93e9-43e7-b463-e6015ca8dc46 (model_intent glm-5p3, still rejected as grok-4.7)
5edf8b27-d28f-4ce9-923e-43798ee0e2dc (model_intent grok-4.5)
3f2b874b-6a02-4a23-b4a1-607285161cd4 (model_intent grok-4.5)
a3345534-3bdd-476c-84fb-13402e327bcc (model_intent grok-4.5)
6144e6a0-75d2-484a-8cd5-915cca9bf80f (model_intent grok-4.7)

Time: 2026-09-29 13:13 CST / 05:13 UTC
Privacy mode: not changed for this report; IDs taken from local Cursor logs.

Additional Information

Server error:
ERROR_BAD_MODEL_NAME
title: AI Model Not Found
detail: Invalid parameters for registry model: “grok-4.7”
actionRequired: config
isRetryable: false
showRequestId: false
service: agent.v1.AgentService / Run

Client log sample:
[buildRequestedModel] catalogModelId=grok-4.7 idSource=selectedModels[0] composerModelName=grok-4.7 selectedModelIds=grok-4.7 matchingSelectedModel=true resolvedParams=3

Workaround that worked in a later chat: start a new Agent conversation after the selected model is no longer grok-4.7 (this report chat is running on Cursor Grok 4.6). Switching the picker alone is not enough while selectedModels[0] remains grok-4.7.

Does this stop you from using Cursor

Yes - Cursor is unusable

image
image1836×204 8.45 KB

6

Hey @ccc_ccc, thanks for the detailed report! This isn’t anything you misconfigured, and it’s an issue we’re tracking.

Quickest fix: start a new Agent chat and pick another model to keep working (Grok 4.6 is running normally on your account). To stay on Grok 4.7, open its options in the model picker and set the context length back to the standard 256K before sending.

One heads-up that matches what you saw: switching models inside that same stuck chat won’t clear it, so a fresh chat is the reliable reset. Let me know if that gets you going again.