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

做了什么

Staff (kevinn): “Bot failed to respond” on every bot—including fresh copies—means the shared cloud computer is stuck, not something you can fix by restarting or recreating bots; after staff recovery, fully quit (Cmd+Q / force-close iOS), update every install, keep one open, and test in a new chat.

场景

未归类

资料完整度

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

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

来源原文摘录

Where does the bug appear (feature/product)? Grok Bot Describe the Bug Where does the bug appear (feature/product)? Grok Bot Describe the Bug I’m experiencing what appears to be the same issue others have reported with Grok Bot becoming stuck and failing to respond. I have already: Restarted my computer. Confirmed Cursor is up to date. Created a fresh copy of the affected Grok Bot. Tested the new copy with a very simple health check that uses no tools, connectors, search, or memory. The issue persists. The bot repeatedly returns “Bot failed to respond — Something went wrong while generating

展开全文

the reply. Try again.” even in the newly created copy. Other Grok Bots also appear to be affected, so this does not seem isolated to a single conversation or bot configuration. …

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

提示词

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

怎么复制

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

风险与限制

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

用量预估

用金属计算器估一下