常驻用量

抄作业 / 警告 / Grok Bot

Weekly allowance lasts longer: fresh chats, space routines, cloud-agent manager

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

做了什么
Staff (mohitjain, 2026-09-10): Grok Bot bills for work done (tools, browser, subagents, re-reading history each turn)—not message count; long threads with high cache-reads get pricey. Biggest wins: start a fresh conversation per task; space routines (avoid every-few-minutes; prefer hourly / dedicated bot); delegate heavy implementation to Cursor cloud agents (manager pattern) so execution burns Cu
场景
周报 / 简报
资料完整度
  • 作者与原链接有
  • 做了什么有
  • 来源原文摘录有
  • 截图 / 媒体来源未提供
  • 步骤 / 章节来源未提供
  • 提示词 / 配置原文来源未提供
  • 结果 / 数字来源未提供
  • 风险提示有
  • 相关条目有

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

来源原文摘录
Hi everyone, I’ve used Cursor for years, and I’m really excited about Grok Bot. It’s the kind of tool I want to build my daily workflow around. But my first experience with Ultra’s usage limits has left me frustrated and wondering what I’m doing wrong. I upgraded to Ultra at $200/month, and most of my Grok Bot weekly allowance disappeared on the first day. I noticed how quickly it was dropping and reduced my usage, but it still reached 99% by the end of the third day, leaving me waiting several days for the reset. Support checked my account and gave me this breakdown: • Day 1: 65% of the
展开全文 weekly allowance used • Day 2: 84% used • Day 3: 99% used They confirmed that the upgrade applied correctly and said the usage came from activity after the upgrade. Most came from Grok Bot Default, with a smaller share from automations. …
RongleCat/awesome-grok-bot (GitHub) · 打开原文 ↗

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

提示词

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

怎么复制
  1. 读原文:forum.cursor.com ↗
  2. 把原文里的步骤/提示词整理成一条消息交给 Bot
  3. 先手动跑一次,再决定频率
风险与限制
  • 这是一条额度/故障反馈(警告),不是可复制的作业。
  • Staff (mohitjain, 2026-09-10): Grok Bot bills for work done (tools, browser, subagents, re-reading history each turn)—not message count; long threads with high cache-reads get pricey. Biggest wins: start a fresh conversation per task; space routines (avoid every-few-minutes; prefer hourly / dedicated bot); delegate heavy implementation to Cursor cloud agents (manager pattern) so execution burns Cursor plan, not the weekly Bot pool; scope tightly and check the meter.
  • 用到浏览器或网页登录:最耗额度,能用 connector 就别开浏览器
  • 定时运行会持续消耗额度:频率从低开始,跑稳再加
  • 作者的结果不保证能复现,以原帖为准
用量预估
用金属计算器估一下