抄作业 / 警告 / Grok Bot

做了什么

Staff (kevinn, 2026-09-14): No in-place compact for a Grok Bot chat—auto-summary near the limit still lets busy threads refill. Workaround: ask the Bot to save a handoff file (responsibilities, decisions, active work, refs) → Bot actions → Duplicate (keeps profile/skills/routines/avatar; clears conversation/memory) → have the copy read the handoff → Hide the old Bot. Prefer short pointers over dum

场景

周报 / 简报

资料完整度

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

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

来源原文摘录

My main chat is my Chief of staff and I have done so much work through him that the Chat is huge. I have split things up so the different app versions speak through different bots. Problem is that the main Chat is still too fat. How do I trim it down to managable size? thanks

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

提示词

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

怎么复制

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

风险与限制

• 这是一条额度/故障反馈（警告），不是可复制的作业。
• Staff (kevinn, 2026-09-14): No in-place compact for a Grok Bot chat—auto-summary near the limit still lets busy threads refill. Workaround: ask the Bot to save a handoff file (responsibilities, decisions, active work, refs) → Bot actions → Duplicate (keeps profile/skills/routines/avatar; clears conversation/memory) → have the copy read the handoff → Hide the old Bot. Prefer short pointers over dumping long specialist handoffs into the Chief chat.
• 定时运行会持续消耗额度：频率从低开始，跑稳再加
• 作者的结果不保证能复现，以原帖为准

用量预估

用金属计算器估一下