抄作业 / 做成了什么 / Grok Bot

做了什么

Staff (Colin): Status “leaks” across chats are expected—each Bot has one conversation and one memory spanning its 1:1 and every group it joins; group turns are room-tagged but memories belong to the Bot, so keep Project X and Y on separate Bots (or file notes under a project folder, which is less reliable than separate Bots).

场景

安全与隐私

资料完整度

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

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

来源原文摘录

Where does the bug appear (feature/product)? Grok Bot Describe the Bug Two separate Grok Bot chats/bots are using the same underlying agent for different long-running research projects. Project A is running in one bot/chat, while Project B is running in a separate bot/chat. Both projects require regular status beats every few minutes, reporting what was found and including a link. The problem: progress from one project shows up in the other bot/chat. Because both bots share the same underlying agent, durable memory and conversation history contain information from both projects. A status beat

展开全文

for Project B keeps Project B “hot,” so the next turn in the separate bot/chat often answers with Project B findings instead of the findings for that bot’s own project. The two bots are separate conversation surfaces, but they are backed by the same agent ID. …

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

提示词

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

怎么复制

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

风险与限制

• 作者的结果不保证能复现，以原帖为准

用量预估

用金属计算器估一下