抄作业 / 警告 / Grok Bot

做了什么

Staff (kevinn): each turn re-reads the bot’s full chat history—so week-long threads burn 80–90k tokens/step; use + fresh chat per task, keep Profile/Notion state, silence ack pings between bots, and space Routines (hourly+) to cut fleet spend.

场景

未归类

资料完整度

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

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

来源原文摘录

We’re a scaling Belgian e-commerce startup (Angelo.be), with no enterprise budget. We’ve been running a Grok Bot fleet for about one week, and we’re very happy with what it does. But in that week we burned roughly $1,500 in extra usage, which is far more than we can sustain. I’m posting for two reasons: • Cursor Support: is this token usage normal, or is something going wrong (loops, retries, context bloat, agent-to-agent chatter)? • Community: what best practices do you use to keep a multi-agent setup affordable? Who we are I’m CTO and co-owner, responsible for our digital landscape, without

展开全文

a technical background. We do our own fullfilment. To run the whole fulfillment proces we’ve build and run our own WMS, including our own support system. Storefront is Shopify. Our bot setup: colleagues vs. tools We deliberately split the fleet into two groups. …

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

效果截图

提示词

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

怎么复制

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

风险与限制

• 这是一条额度/故障反馈（警告），不是可复制的作业。
• 定时运行会持续消耗额度：频率从低开始，跑稳再加
• 作者的结果不保证能复现，以原帖为准

用量预估

用金属计算器估一下