Cloud agents default model setting switches to fast mode

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

i use grok 4.7 for cloud agents, and sometimes i notice it switches to fast mode, why this happens ?

Steps to Reproduce

i dont know

Expected Behavior

if i choose a default model, it shouldn’t change and agent should respect to that if i didn’t choose another model

Operating System

MacOS

Version Information

Version: 3.28.7
VS Code Extension API: 1.128.0
Commit: 25b52e7d03ebf2d5608914158e119f7992432a30
Date: 2026-11-03T02:20:44.943Z
Layout: Agent Window
Build Type: Stable
Release Track: Default
Electron: 42.11.16
Chromium: 148.0.7778.280
Node.js: 24.19.0
V8: 14.8.178.38-electron.0
xterm.js: 6.1.0-beta.291
OS: Darwin arm64 25.6.0

For AI issues: which model did you use?

grok 4.7

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hi @vibeprompter, the most common cause we’ve seen for this is the Cursor app on iPhone. When it loads its model list, it can overwrite your saved Cloud Agent default with Grok 4.7 High Fast, and agents started afterwards run on Fast. Grok 4.7’s standard default has Fast on, so the Fast variant is what you get whenever your saved choice is lost.

If you use the iPhone app, for now you can re-save your default and check it again after you next open the app:

  1. Go to cursor.com/dashboard/cloud-agents and scroll to Default Model.
  2. Hover Grok 4.7, click Edit, and uncheck Fast.
  3. Save, then reload the page and confirm Fast is still off.

If you don’t use the iPhone app, could you share the link (bc-…) of an agent that ran on Fast? That lets us check what model the launch actually asked for.

7

I’m using the iOS app and updated the cloud agent defaults. I’ll check if it uses Fast again

8

I did change default today and now i saw its fast again and i changed again

9

Ok it seems that default change not working, when i open ios app, https://cursor.com/dashboard/cloud-agents setting opens fast back this is bug

Dont need to open new chat or anything, just opening ios app makes it fast

11

Thanks for checking, @vibeprompter. That confirms it: opening the iPhone app rewrites your saved Cloud Agent default to Grok 4.7 High Fast. Re-saving on the dashboard only lasts until the app loads its model list again. This is a known issue the team is aware of.

In the meantime, setting the default from inside the iPhone app should stick, because the app keeps a choice it made itself:

  1. In the iPhone app, start a new agent and tap the model name to open the Model list.
  2. Pick Grok 4.7, set effort to High and turn Fast off.
  3. Fully close and reopen the app, then reload cursor.com/dashboard/cloud-agents and check that Default Model still shows Fast off.

If it flips back to Fast after that, let me know here.

13

ok configuring in iphone make sense, its working with that way

14

this got me as well overnight. following the iphone app instructions from @Colin seems to have worked. will confirm on my next cloud agent run.

will there be a usage recalculation for impacted users? this ate up a little bit of mine after I just got reset last night.

15

There still seems to be a bug. I have the default set for all cloud agents to be 256k High with Fast OFF. Opening the iPhone app again reset my cloud agent default to 500k High with Fast ON.

19

Hi @firstbloom, the revert came from saving the default on the dashboard after setting it in the app. A dashboard save stores Grok 4.7 in a form the iPhone app doesn’t recognize, so the next time the app loads its model list it swaps it back to 500K High with Fast on. It’s the same known issue the team is aware of.

For now, this order should keep it:

  1. In the iPhone app, start a new agent, tap the model name, pick Grok 4.7, set High and turn Fast off.
  2. After that, don’t save Default Model on cursor.com/dashboard/cloud-agents. Looking at it there is fine, but saving it brings the problem back.
  3. Agents that were already started on Fast keep Fast for their follow-ups, so switch the model in those chats or start a new agent.

One caveat: the app’s setting may not carry your 256K context choice through to agents, so check the context size on your next run.

@vibeprompter, the same applies to you: once it’s set in the app, avoid re-saving it on the dashboard.