抄作业 / 警告 / Grok Bot

做了什么

Staff (mohitjain): Each bot-to-bot message burns a weekly-usage turn; asking bots in chat to “stay quiet” is only a hint. Reliable fixes: run work in one Command Agent with subagents (they finish and stop), and delete unused specialist bots (idle bots can still be woken; deleting also clears that bot’s chat — save first). Double limit banners are blocked retries, not double charges.

场景

周报 / 简报

资料完整度

• ✓ 作者与原链接有
• ✓ 做了什么有
• ✓ 来源原文摘录有
• ✓ 截图 / 媒体有
• — 步骤 / 章节来源未提供
• — 提示词 / 配置原文来源未提供
• — 结果 / 数字来源未提供
• ✓ 风险提示有
• ✓ 相关条目有

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

来源原文摘录

Where does the bug appear (feature/product)? Grok Bot Describe the Bug Grok Bot burned the included weekly usage on a multi-bot review loop, then locked the account. Specialist bots (QC, UAT, Coding, UIUX) kept talking after you asked them to stay quiet and send the verdict to Command Agent only. Sidebar: Weekly usage 100% Banner: You’ve reached your Grok Bot usage limit. It resets in 3 days. Fired 2 times between 06:37:17 AM and 06:37:38 AM CTA: Upgrade to Pro+ Steps to Reproduce after you review, sending back to the command agent. I only wanna do the job in the command agent UAT Bot replied

展开全文

that the verdict would go to Command Agent and it would keep the chat quiet. The bots kept exchanging collapsed groups of messages anyway. Expected Behavior Bot-to-bot bounce-backs should stop — or at least not eat the weekly quota — when you say you only want to work in Command Agent. …

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

效果截图

提示词

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

怎么复制

1. 读原文：forum.cursor.com ↗
2. 把原文里的步骤/提示词整理成一条消息交给 Bot
3. 先手动跑一次，再决定频率

风险与限制

• 这是一条额度/故障反馈（警告），不是可复制的作业。
• 有删除、退订或取消动作：先出清单，逐项确认再执行
• 定时运行会持续消耗额度：频率从低开始，跑稳再加
• 作者的结果不保证能复现，以原帖为准

用量预估

用金属计算器估一下