抄作业 / 做成了什么 / Grok Bot
Connected but “temporarily unreachable” — local-exec slower than 10s wait
标题与摘要为原文，未翻译。
- 做了什么
- Staff (deanrie, 2026-09-05): On 0.43 Windows, ListMachines can show connected while Shell fails with temporarily unreachable when the PC answers ~11s but the agent stops waiting at 10s—commands did run; renaming the PC / toggling Local execution won’t help; share local-exec-daemon.log and check AV, OneDrive/AppData redirect, VPN/proxy.
- 场景
- 写代码上线
- 资料完整度
- 作者与原链接有
- 做了什么有
- 来源原文摘录有
- 截图 / 媒体来源未提供
- 步骤 / 章节来源未提供
- 提示词 / 配置原文来源未提供
- 结果 / 数字来源未提供
- 风险提示有
- 相关条目有
— 表示来源没有给出，本站不补写。
- 来源原文摘录
Where does the bug appear (feature/product)? Grok Bot Describe the Bug Windows PC registered as JPA-GranVía. Since Grok Bot 0.43, local execution is broken in a new way: • Computer list shows connected • Local execution set to Always allow / Permitir siempre • Any command from the agent fails with “temporarily unreachable” (sometimes then “disconnected”) • Renaming the display label (accented í ↔ plain i) made no difference Before 0.43 it was also flaky, but different: it would connect for a fraction of a second, then drop. So it never fully worked for me, but 0.43 changed the failure mode
展开全文
from “brief connect then drop” to “listed as connected but never actually reachable.” Steps to Reproduce • Open Grok Bot on Windows with a registered local computer (JPA-GranVía) • Set Local execution to Always allow • Ask an agent to run a simple command on that PC (e.g. hostname) …RongleCat/awesome-grok-bot (GitHub) · 打开原文 ↗ 摘自论坛首帖，照录原文，未翻译。
- 提示词
来源没有给出可直接复制的提示词原文。
- 怎么复制
- 读原文：forum.cursor.com ↗
- 把原文里的步骤/提示词整理成一条消息交给 Bot
- 先手动跑一次，再决定频率
- 风险与限制
- 作者的结果不保证能复现，以原帖为准
- 用量预估
- 用金属计算器估一下