抄作业 / 做成了什么 / Grok Bot
Always-on workers vs topic threads
标题与摘要为原文，未翻译。
- 做了什么
- Community consensus: a Bot is a standing coworker, not a chat tab.
- 场景
- 未归类
- 资料完整度
- 作者与原链接有
- 做了什么有
- 来源原文摘录有
- 截图 / 媒体来源未提供
- 步骤 / 章节来源未提供
- 提示词 / 配置原文来源未提供
- 结果 / 数字来源未提供
- 风险提示有
- 相关条目有
— 表示来源没有给出，本站不补写。
- 来源原文摘录
Title: Grok Bots as always-on workers vs topic threads Body: In Claude Cowork I use lots of short threads — one issue per chat — and those threads also become a record I can go back to. Grok Bots feel more like always-on coworkers than disposable topic threads. Great for ongoing work, but less clear as a place to keep / retrieve focused information. Is the idea “one Bot per role,” and keep research threads elsewhere? Or is there a better way to keep topic-scoped context in Grok Bot? Would love feedback on how people are structuring this. Steven grok-bot
RongleCat/awesome-grok-bot (GitHub) · 打开原文 ↗ 摘自论坛首帖，照录原文，未翻译。
- 提示词
来源没有给出可直接复制的提示词原文。
- 怎么复制
- 读原文：forum.cursor.com ↗
- 把原文里的步骤/提示词整理成一条消息交给 Bot
- 先手动跑一次，再决定频率
- 风险与限制
- 作者的结果不保证能复现，以原帖为准
- 用量预估
- 用金属计算器估一下