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

做了什么

Staff (deanrie, 2026-09-23): “Route traffic through this computer” only relays to public internet addresses—desktop rejects CONNECT when the hostname resolves to private ranges (192.168/10/172.16–31); public cloud hosts still work. Docs currently imply internal hosts should work; mismatch filed with the team (no ETA).

场景

未归类

资料完整度

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

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

来源原文摘录

Where does the bug appear (feature/product)? Grok Bot Describe the Bug Toggle ON on desktop (hostname 9VS4T44). UI shows routed traffic this session (e.g. “37 routed this session”). From Grok Bot’s computer, our internal DEV hostname (split-horizon DNS) fails: browser ERR_CONNECTION_CLOSED (“unexpectedly closed the connection”); curl TLS unexpected EOF. Bot DNS → public 38.97.236.88 Same host on my PC → internal 192.168.201.34 and HTTPS works Public internet-facing hosts work from the bot; this internal DEV host does not. Local egress tunnel present; HTTP CONNECT to DEV:443 returns 200, then

展开全文

TLS still dies. Steps to Reproduce • On a desktop that can reach an internal/split-horizon host (ours resolves to 192.168.201.34 on the desktop, public IP on the bot), open Grok Bot. • Settings → Computer. • Confirm current computer selected; Execution on this computer allowed. …

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

提示词

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

怎么复制

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

风险与限制

• 用到浏览器或网页登录：最耗额度，能用 connector 就别开浏览器
• 作者的结果不保证能复现，以原帖为准

用量预估

用金属计算器估一下