抄作业 / 教程 / Grok Bot

做了什么

Community recovery runbook when Grok Bot desktop fails to start after a broken app.asar leaves empty tree-sitter dep stubs.

场景

写代码上线

资料完整度

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

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

来源原文摘录

Recover Grok Bot desktop when the main process dies on startup with:

摘自项目 README，照录原文，未翻译。

效果截图

来源里的步骤 / 要点

1. Electron main sets NODE_PATH to app.asar/dist/deps and requires tree-sitter (shell parser).
2. Native deps are shipped under app.asar.unpacked/dist/deps (real package.json + .node files).
3. A same-day app.asar rewrite left only empty directory stubs for dist/deps/* inside the archive.
4. Module resolution looked inside the broken asar path and failed, even though unpacked packages were still on disk.
5. If dist/deps/tree-sitter/package.json is already in the current app.asar with a size above zero, the script exits and leaves the file alone.
6. A backup is eligible only when its header has that same file. A larger file is not preferred just because it is larger.
7. Names containing broken are never chosen, including app.asar.broken-before-restore-*.
8. -CheckOnly prints the result and changes nothing. Exit 0 means healthy. Exit 2 means the index is missing tree-sitter.

照录来源原文，未翻译。

提示词

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

怎么复制

1. 打开仓库：github.com/Pitchfork-and-Torch/grok-bot-asar-recovery ↗
2. 读 README，把仓库链接发给你的 Bot，让它按 README 复现
3. 先在小范围跑通，再加 routine

风险与限制

• 涉及付款、下单或预订：先让 Bot 只起草，确认后再执行
• 作者的结果不保证能复现，以原帖为准

用量预估

用金属计算器估一下