抄作业 / 警告 / Grok Bot

做了什么

Feature request for Grok Bot/agents: context compaction, clone-and-replace hung chats, and per-bot usage telemetry instead of opaque shared quotas.

场景

未归类

资料完整度

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

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

来源原文摘录

Feature request for product/service Cloud Agent (GitHub, Slack, Linear,…) Describe the request Feature request for product/service Grok Bot / multi-agent fleet (Blessed Bits ops) Problem We run a fleet of long-lived Grok Bot agents. Usage is climbing faster than expected. Today the only practical way to clear a bloated / hung long-running chat context is to clone the bot and delete the old one (we just did this for Ezra). That is disruptive: easy to lose continuity, rewiring teammates, and it does not teach us which bot is burning tokens or why. Requests 1. Context / memory efficiency •

展开全文

Stronger compaction / summary of long threads without a full clone. • Clearer split between durable memory vs transcript weight. • User option to archive or reset conversation context while keeping profile, routines, skills, and durable memory. 2. User-driven clone & replace for hung bots …

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

提示词

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

怎么复制

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

风险与限制

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

用量预估

用金属计算器估一下