Cloud Agent logs claude-4.5-sonnet when picker is Grok 4.6 and Claude is not enabled

Support Bug Reports
, , ,
1

Where does the bug appear (feature/product)?

Cloud Agent (GitHub, Slack, Web, Linear)

Describe the Bug

When the chat/Cloud Agent picker is Cursor Grok 4.6 (High, Fast) and Settings → Models has only Grok 4.6 and Grok 4.5 enabled, Cloud Agent runs are still recorded as claude-4.5-sonnet (cloud icon on the Usage table).

Claude is hidden by default and is not in my model list. I have never selected it. Explore Subagent Model is Default.

This is not a one-off GPT call. I did use GPT once; that is separate. I never selected Claude.

Before 2026-08-26 the Usage table showed Grok for these workflows. On 2026-08-26 Usage listed Claude Cloud Agent events, for example:

  • 06:27 UTC — claude-4.5-sonnet — cloud icon
  • 06:41 UTC — claude-4.5-sonnet — cloud icon

The parent model I start is Grok. Helper/subagent work on that Cloud Agent still shows up as Claude 4.5 Sonnet. Settings → Models does not stop this: turning models off in the IDE picker does not apply to Cloud Agent helper tasks.

Expected: Cloud Agents and their Task/subagents inherit the selected parent model (Grok 4.6) unless I explicitly pick another model.

Actual: Usage records claude-4.5-sonnet for Cloud Agent runs I started as Grok. There is no setting that pins Cloud Agent helpers to inherit.

Please treat this as a product bug: Cloud Agent / subagent model selection ignores the parent picker and ignores the enabled-models list. How can a Cloud Agent be forced to inherit Grok for all helper tasks?

Steps to Reproduce

  1. Settings → Models: enable only Cursor Grok 4.6 and Grok 4.5. Do not add Claude. Claude is not in the list.
  2. Set Explore Subagent Model to Default.
  3. Picker: Cursor Grok 4.6, Fast on, Effort High.
  4. Start a Cloud Agent from the desktop Agents window (Cloud) on a normal coding task.
  5. Open Usage. Rows with the cloud icon show claude-4.5-sonnet even though the picker was Grok.

Expected Behavior

The Cloud Agent and any Task/subagents should inherit Cursor Grok 4.6. Claude should not run unless I enable it and select it.

Screenshots / Screen Recordings

1.png
1.png905×358 16.3 KB
2.png
2.png1171×283 9.07 KB
3.png
3.png1268×852 33.8 KB

Operating System

Windows 10/11

Version Information

Version: 3.17.21 (user setup)
VS Code Extension API: 1.128.0
Commit: 8f2a112cb2845a97b75fd932ea5c470579ca4060
Date: 2026-08-25T01:05:08.089Z
Layout: Agent Window
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.291
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey, thanks for the detailed report with screenshots and the version.

What’s happening here: the Cloud Agent itself did run on Cursor Grok 4.6, like you selected. The claude-4.5-sonnet lines in Usage aren’t the main agent. They’re helper or subagent tasks the agent runs under the hood for support work like exploration or verification. Right now, some of those helpers pick a model on their own instead of inheriting the parent model.

Key detail: the list in Settings → Models only filters the model picker in the IDE. It doesn’t limit model choice for cloud subagent tasks. So even if only Grok 4.6 and 4.5 are enabled, a helper can still run on Claude. There isn’t a Pro setting yet to force all Cloud Agent helpers to use your parent model. That’s exactly what users expect, but it isn’t implemented yet.

We’re aware of this behavior, and it’s not caused by your setup. We’re tracking it and I’ve shared your report with the team. I can’t give a timeline yet, but if there’s an update I’ll reply in the thread.

7

Thanks for the clear explanation, Dean — that matches what I was seeing.

Aside from this, I’ve been happy with Cursor overall. The problem is that these helper/subagent calls still consume my limited Other Models quota even when I only want Grok. On a plan where that pool is already small, it adds up quickly.

I understand Settings → Models doesn’t control cloud helpers, and that there’s no way yet to pin them to the parent model. That’s exactly the behavior I’d hope for: if I pick Grok, helpers should follow it too (or at least stay within the same usage pool).

Appreciate you tracking this. Hope it can be fixed.

8

Thanks for coming back with that clarification, it’s an important point. You’re right, right now those helper and subagent calls use your Other Models pool even when Grok is selected for the parent agent. That’s exactly the behavior we’re tracking. The goal is for helpers to follow the model you picked, or at least stay in the same usage pool, instead of choosing a model on their own.

I can’t share a timeline yet, but this thread is tied to that work, and I’ll post here if there’s an update. Glad Cursor’s been working well for you otherwise. If you notice anything else about usage, drop it in the thread.

9

yes ! I’m experiencing the same issue!

image
image574×134 2.83 KB

image
image2022×790 47.9 KB

10

I also have the exact same issue, Cursor Grok was selected for the task, but Sonnet was used for browser screenshots and recordings. It has now rinsed through my Other usage , which I was waiting to use up at the end of the month on some more complex tasks

image
image1099×419 43.1 KB

11

Same issue here.

I planned to use “Cursor Models” (Cursor Grok and Composer) in Cloud Agents for light and simple features and use other models (Opus, Sol, etc) when I work on my computer with heavy workflows and complex features. Unfortunately, Cloud Agents has exhausted my included quota for “other models”

12

I’m seeing exactly the same issue.

I explicitly select Grok 4.5/4.6 for my Cloud Agents because I do not want to consume my Other Models quota, yet Cursor still uses Sonnet/Gemini for subagents, browser/computer-use tasks, screenshots, or other internal helpers.

This is not acceptable. If I select a model, Cursor should either respect that choice for the entire agent run or give me a setting to strictly prevent any other model from being used.

Telling the agent not to use subagents does not reliably prevent this, and disabling models in the model picker does not prevent the quota consumption either.

Please prioritize fixing this. Users should not have quota consumed from models they did not choose and explicitly do not want to use.

15

Hey @Guille, this is the same behavior we already talked about earlier in the thread. The main agent correctly runs on the Grok model you selected, but some helper or sub-agent tasks like exploration, browser or computer-use, and verification still pick a model on their own and don’t inherit the parent model. That’s why usage comes out of the Other Models pool.

The model list in Settings → Models only filters the picker in the IDE and doesn’t restrict cloud helper tasks. This isn’t something wrong with your setup.

We’re tracking this issue, and this thread is linked to it. I can’t share a timeline yet, but if there’s an update, I’ll post it here.

16

Thanks, yes, the issue is clear. What is surprising is that this doesn’t seem to be a much higher priority, as it is been going on for so long now.

There is no reliable way to disable these subagents, so Cursor can consume our Other Models quota even when we explicitly choose Grok. That means our paid usage is partly outside our control, with no workaround and currently no timeline for a fix.

For something that directly affects quota consumption, I really think this needs to be treated as a priority.