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

做了什么

Staff: 0.30.0 fixed one macOS daemon exit/no-respawn path, but Windows leftover local-exec-daemon is a different known failure; when the machine is unreachable, Quit from the tray, end remaining “Grok Bot” and local-exec-daemon processes in Task Manager, relaunch, and wait about a minute to re-register.

场景

周报 / 简报 盯 PR / 仓库

资料完整度

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

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

来源原文摘录

Where does the bug appear (feature/product)? Grok Bot Describe the Bug Grok Bot desktop on Windows loses the local-computer link after the app has been healthy. Same failure sequence as the macOS local-exec-daemon report. Still happening on 0.30.0 after @Colin said 19 Aug a fix was ready for the next release. The PC is reached through a detached local-exec daemon: %LOCALAPPDATA%\Programs\Grok Bot\Grok Bot.exe %LOCALAPPDATA%\Programs\Grok Bot\resources\app.asar\dist\local-exec-daemon\main.cjs Relaunching the app does not kill the previous daemon. Leftover local-exec-daemon and crashpad-handler

展开全文

processes keep running. Agents cannot recover this themselves because local Shell is that dead channel. Cloud/box side keeps working. Failure sequence (same session, 31 Aug 2026, America/New_York): …

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

提示词

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

怎么复制

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

风险与限制

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

用量预估

用金属计算器估一下