常驻用量

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

Forum: Bot computer silently restored to Sep 28 snapshot

标题与摘要为原文,未翻译。

做了什么
Failure report: Grok Bot cloud computer rebooted overnight and restored a Sep 28 snapshot, wiping Sep 29–Oct 1 box files with no Update/Reset pressed.
场景
周报 / 简报 盯 PR / 仓库
资料完整度
  • 作者与原链接有
  • 做了什么有
  • 来源原文摘录有
  • 截图 / 媒体来源未提供
  • 步骤 / 章节来源未提供
  • 提示词 / 配置原文来源未提供
  • 结果 / 数字来源未提供
  • 风险提示有
  • 相关条目有

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

来源原文摘录
Where does the bug appear (feature/product)? Grok Bot Describe the Bug Grok Bot’s computer (the shared cloud box) rebooted at 2026-10-02 00:00:39 ET and came back with its files rolled back to about 2026-09-28 20:59 ET. Everything written Sep 29 – Oct 1 is gone. Nobody asked for a reset, restore, or update. I don’t recall pressing Update or Reset for Grok Bot’s computer overnight. What we saw on the box (checked 12:54 PM ET, Oct 2): • Uptime: booted 2026-10-02 00:00:39 ET. • Every file in one project folder (221 files) has an mtime between 2026-09-28 20:59:29 and 20:59:45 ET. That includes
展开全文 files whose names show they were made Sep 17–28. They were all rewritten within about 16 seconds, which looks like a restore from a Sep 28 ~20:59 ET snapshot. • Files and folders created Sep 29 – Oct 1 are missing: …
RongleCat/awesome-grok-bot (GitHub) · 打开原文 ↗

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

提示词

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

怎么复制
  1. 读原文:forum.cursor.com ↗
  2. 把原文里的步骤/提示词整理成一条消息交给 Bot
  3. 先手动跑一次,再决定频率
风险与限制
  • 作者的结果不保证能复现,以原帖为准
用量预估
用金属计算器估一下