抄作业 / 做成了什么 / Grok Bot
Forum: desktop take-over stuck on "connecting" and Screenshot blocked under high load on a shared box
标题与摘要为原文，未翻译。
- 做了什么
- Bug report with logs: on a box shared by several agents, idle Chrome renderers drove load to 70–80, one agent's take-over hung, Screenshot failed the credential-fill guard, and box-doctor timed out.
- 资料完整度
- 作者与原链接有
- 做了什么有
- 来源原文摘录有
- 截图 / 媒体来源未提供
- 步骤 / 章节来源未提供
- 提示词 / 配置原文来源未提供
- 结果 / 数字来源未提供
- 风险提示有
- 相关条目有
— 表示来源没有给出，本站不补写。
- 来源原文摘录
Where does the bug appear (feature/product)? Grok Bot Describe the Bug Several agents share one box, each with its own desktop and browser. On Sun Oct 4 between about 1:30 and 2:48 PM ET, one agent’s desktop stopped responding. Symptoms: • The take-over screen stayed on “connecting”. • That agent’s Screenshot calls failed with “The box could not confirm that no saved credential is being filled into its browser”. • box-doctor hung for more than 105 s. • An “Update” button showed for that agent for a few minutes (about 2:40 to 2:46 PM ET) and then disappeared without us pressing it. What the box
展开全文
showed: • Load average reached roughly 70 to 80 on 8 cores, starting around 1:30 PM ET. Most of it came from long-lived Chrome renderer processes in other, idle agents’ browsers, with tabs open since the previous day using hours of CPU time. …RongleCat/awesome-grok-bot (GitHub) · 打开原文 ↗ 摘自论坛首帖，照录原文，未翻译。
- 提示词
来源没有给出可直接复制的提示词原文。
- 怎么复制
- 读原文：forum.cursor.com ↗
- 把原文里的步骤/提示词整理成一条消息交给 Bot
- 先手动跑一次，再决定频率
- 风险与限制
- 用到浏览器或网页登录：最耗额度，能用 connector 就别开浏览器
- 多个 Bot 并行：额度按 Bot 数叠加，先合并职责相近的 Bot
- 作者的结果不保证能复现，以原帖为准
- 用量预估
- 用金属计算器估一下