Cloud Cursor Agents spawned by Grok Bot do not fully respect the user-selected default model and speed preferences

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

I noticed a usage issue when Grok Bot delegates tasks to Cursor Cloud Agents.

I have my Cloud Agents default configured to use a non-Fast model setting, but whenever Grok Bot spawns a Cloud Agent, the resulting agent runs in Fast mode anyway. The model itself can be different; the important part is that the Cloud Agent does not respect the configured non-Fast default it seems.

Steps to Reproduce

  1. Open Cursor Cloud Agent settings.
  2. Set the default model to a non-Fast configuration (for example, Grok 4.6, Medium, non-Fast).
  3. Use Grok Bot to delegate a task that causes it to spawn a Cursor Cloud Agent.
  4. Open the resulting Cloud Agent run and check the model/speed being used.
  5. The spawned Cloud Agent is running in Fast mode despite the configured non-Fast default.

Expected Behavior

When Grok Bot spawns a Cursor Cloud Agent, the agent should use the Cloud Agent default model and speed configuration selected by the user. If the default is set to non-Fast, the spawned agent should run in non-Fast mode.

Operating System

Windows 10/11

Version Information

Grok Bot 0.29.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

7

Hey @Warexpor_ForX thanks for flagging - this isn’t on your end, it’s an issue we’re tracking where cloud agents can start Fast even with a non-Fast default.

Two quick things: in the Default Model picker, hover Cursor Grok 4.6 → Edit and make sure Fast is unchecked (the closed picker hides it and it doesn’t always stick otherwise). And if the follow-up box flips to Fast after the first reply, switch it back before sending.

If an agent still starts Fast after that, drop the agent link and rough time and I’ll dig into that run. More here: Fast mode is selected by deafult or switched on request (cloud agents)

10

Hey @Warexpor_ForX,

Quick update on this. The behavior where cloud agents could switch to Fast even with a non-Fast selection has been addressed on our side and will be rolled out soon if it hasn’t been already.

Could you give it another try and let me know if agents started by Grok Bot still come up in Fast mode? If anything still looks off, a link to the agent run would help us dig in.