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

做了什么

Bug report: a persistent computer running since Sep 17 was recreated on Oct 5 without Update, Recover or Reset, the old and new contexts ran side by side, and the new one lacked recent files; staff confirmed an unfinished automatic recreate and advised not to press Update, Recover or Reset and to back up from the old endpoint while reachable.

场景

周报 / 简报 盯 PR / 仓库

资料完整度

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

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

来源原文摘录

Where does the bug appear (feature/product)? Grok Bot Describe the Bug I already have support ticket T-G64842 open for this issue. My Grok Bot persistent computer appears to have been reprovisioned into a new computer context without me initiating Update, Recover, or Reset. The original computer had been running since Sep 17. On Oct 5, a second context appeared with a different boot ID and different filesystem/runtime state. For several hours, the old Sep 17 context and the new Oct 5 context appeared to coexist through different access paths. During that overlap, work and filesystem changes

展开全文

were still occurring on the older context. Over time, Grok Bot sessions converged on the newer Oct 5 context. The older Sep 17 context then became unreachable through its previously working SSH/Tailscale path. …

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

提示词

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

怎么复制

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

风险与限制

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

用量预估

用金属计算器估一下