常驻用量

抄作业 / 做成了什么 / Grok Bot

Grok-spawned Cloud Agents can ignore your non-Fast default

标题与摘要为原文,未翻译。

做了什么
Staff: Grok-spawned Cursor Cloud Agents can start in Fast even when your default is not; hover Cursor Grok 4.6 → Edit and uncheck Fast, and switch the follow-up box back if it flips.
场景
未归类
资料完整度
  • 作者与原链接有
  • 做了什么有
  • 来源原文摘录有
  • 截图 / 媒体来源未提供
  • 步骤 / 章节来源未提供
  • 提示词 / 配置原文来源未提供
  • 结果 / 数字来源未提供
  • 风险提示有
  • 相关条目有

— 表示来源没有给出,本站不补写。

来源原文摘录
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 • Open Cursor Cloud Agent settings. • Set the default model to a non-Fast configuration (for example, Grok 4.6, Medium, non-Fast).
展开全文 • Use Grok Bot to delegate a task that causes it to spawn a Cursor Cloud Agent. • Open the resulting Cloud Agent run and check the model/speed being used. • The spawned Cloud Agent is running in Fast mode despite the configured non-Fast default. Expected Behavior …
RongleCat/awesome-grok-bot (GitHub) · 打开原文 ↗

摘自论坛首帖,照录原文,未翻译。

提示词

来源没有给出可直接复制的提示词原文。

怎么复制
  1. 读原文:forum.cursor.com ↗
  2. 把原文里的步骤/提示词整理成一条消息交给 Bot
  3. 先手动跑一次,再决定频率
风险与限制
  • 作者的结果不保证能复现,以原帖为准
用量预估
用金属计算器估一下