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

做了什么

Staff (deanrie, 2026-09-07): When every send fails with “Couldn’t send / Failed to send” on all devices but the Agent Computer screen stays visible, it can be a temporary server-side loss of connection for some Grok Bot computers—not Mac/Android/app 0.44.0; connection usually returns without data loss, so message staff before Reset; Reset rebuilds from the last snapshot and may drop the newest uns

场景

写代码上线

资料完整度

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

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

来源原文摘录

Where does the bug appear (feature/product)? Grok Bot Describe the Bug Cannot send any Grok Bot message. Every send fails with “Couldn’t send your message. Check your connection and try again.” / “Failed to send”. Messages stay local only (no requestId / sendAcceptance ack). Bots never reply. Roster/history still sync. The same account also cannot send on Android. This is not one bad chat and not a local Mac-only attach issue. Started 2026-09-07 09:55 CST (UTC+8), immediately after desktop auto-update to 0.44.0 (ShipIt replaced the app ~09:55:53–09:56:02). Last successful bot replies were

展开全文

2026-09-06 evening. Looks like the same class as Grok Bot fails to generate replies; Agent Computer screen is still visible and Grok Bot 0.43.0 — Bot failed to respond; Reset Agent Computer stuck in partial state : shared cloud computer stuck; client reconnect cannot fix it. Steps to Reproduce …

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

提示词

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

怎么复制

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

风险与限制

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

用量预估

用金属计算器估一下