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

做了什么

Staff (deanrie, 2026-09-16): update_state target:memory fails fleet-wide with “brain docs snapshot was cut short before completing” while settings updates and direct file edits still work—known server-side; workaround is write facts into memory/profile.md or memory/log/YYYY-MM.md; Update/Reset Computer won’t help.

场景

未归类

资料完整度

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

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

来源原文摘录

Where does the bug appear (feature/product)? Grok Bot Describe the Bug Summary update_state with target: memory fails on every bot I tested with the exact error: brain docs snapshot was cut short before completing Settings updates via update_state still work. Direct file writes to memory/profile.md and memory/log/*.md still work. Failed memory writes do not reliably land the fact. Where it happens Recreated / reimported bots (e.g. after sidebar Delete + reimport): CreateAgent often leaves incomplete agent-data — missing memory/ folder, no conversation-blobs.db, empty latestRootBlobId.

展开全文

Scaffolding memory/ alone does not fix update_state. Long-lived bots too same error. So this is not recreate-only and not explained by one oversized chat. Repro Open any bot (fresh or old). Ask it to run update_state → target: memory, action: write, short log/note fact. …

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

提示词

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

怎么复制

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

风险与限制

• 有删除、退订或取消动作：先出清单，逐项确认再执行
• 作者的结果不保证能复现，以原帖为准

用量预估

用金属计算器估一下