抄作业 / 做成了什么 / Grok Bot
Unreachable after heavy media — 16 GB RAM exhaustion
标题与摘要为原文，未翻译。
- 做了什么
- Staff (Colin): “Unreachable” during heavier media work often means the cloud machine hit its ~16 GB RAM ceiling within minutes—Recover keeps Bots/files/logins intact; until the machine rides it out, keep jobs under that memory budget.
- 场景
- 财务运营
- 资料完整度
- 作者与原链接有
- 做了什么有
- 来源原文摘录有
- 截图 / 媒体有
- 步骤 / 章节来源未提供
- 提示词 / 配置原文来源未提供
- 结果 / 数字来源未提供
- 风险提示有
- 相关条目有
— 表示来源没有给出，本站不补写。
- 来源原文摘录
Where does the bug appear (feature/product)? Grok Bot Describe the Bug Grok bot seems to have crashed in the middle of a session. Now, it’s been unreachable for 8+ hrs or so. I am prompted to keep retrying or ‘recover’ but I dont want to lose all the work we had in the previous session. Any way to salvage all the work? Steps to Reproduce Unreachable-unable Expected Behavior unreachable Screenshots / Screen Recordings Screenshot 2026-08-28 at 2.40.11 PM.png477×266 21.9 KB Operating System MacOS Version Information Grok Bot 0.29.0 For AI issues: which model did you use? Grok Bot For AI issues:
展开全文
add Request ID with privacy disabled N/A Does this stop you from using Cursor Yes - Cursor is unusableRongleCat/awesome-grok-bot (GitHub) · 打开原文 ↗ 摘自论坛首帖，照录原文，未翻译。
- 效果截图
截图来自原帖 - 提示词
来源没有给出可直接复制的提示词原文。
- 怎么复制
- 读原文：forum.cursor.com ↗
- 把原文里的步骤/提示词整理成一条消息交给 Bot
- 先手动跑一次，再决定频率
- 风险与限制
- 用到浏览器或网页登录：最耗额度，能用 connector 就别开浏览器
- 作者的结果不保证能复现，以原帖为准
- 用量预估
- 用金属计算器估一下