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

做了什么

Staff (mohitjain, 2026-09-07): No one-click export yet—memory lives as plain text on the Bot computer. Per bot, ask it to make backup/<name>, copy full memory (profile + every memory-log month) to memory.md, list routines and connectors, zip and attach; ask Chief of Staff for shared-memory.md + skills-library zip; for other folders, zip/split (attachments cap 25 MB). Connector logins can’t be expo

场景

未归类

资料完整度

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

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

来源原文摘录

What is the best way to go about exporting/backing up each bot’s individual memory, as well as the shared bot memory? I’m not referring to backing up chats, I’m not interested in those. I’m looking to export all of the persistent data, or as Dean Rie put it on another thread: The bot’s durable state (profile, memory, routines, skills, connectors, files on the shared computer) I don’t have any custom skills whatsoever currently, AFAIK. I thought about having each bot create a skill.md file for each topic in its individual memory, and having the Chief of Staff create a skill.md file for each

展开全文

topic in the shared memory. I saw that it is possible to transfer a certain topic from one bot’s individual memory to another bot’s individual memory. I have done this when I created a new bot for a niche purpose. I had another bot doing that niche work before. …

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

提示词

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

怎么复制

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

风险与限制

• 用到浏览器或网页登录：最耗额度，能用 connector 就别开浏览器
• 定时运行会持续消耗额度：频率从低开始，跑稳再加
• 作者的结果不保证能复现，以原帖为准

用量预估

用金属计算器估一下