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

做了什么

Staff (kevinn, 2026-09-15): Slack-triggered Grok Bot routines never see messages from a private channel unless the Cursor Slack app is a member. Test Run bypasses Slack entirely; Slack plugin replies use a different app than the routine listener—so both can work while the trigger stays silent. Fix: in the private channel run /invite @Cursor, wait ~1 min, post a canary message, then check the routi

场景

社媒排期 写代码上线

资料完整度

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

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

来源原文摘录

Where does the bug appear (feature/product)? Grok Bot Describe the Bug A Slack-triggered Grok Bot routine is enabled and Active, but a matching Slack message never starts a routine run. Manual/Test execution of the same routine path succeeded. The Grok Bot Slack plugin successfully wrote back to Slack and readback succeeded. Slack write works. Grok Bot routine execution works. Grok Bot Slack plugin return works. Only Slack event ingestion into the active Grok Bot routine fails. This resembles the previously reported class of dropped Grok Bot routine triggers. I am not claiming it is the same

展开全文

root cause without evidence. Please inspect the backend event subscription / routine-trigger delivery for this Grok Bot account and routine. Grok Bot account for this report: natearizona@icloud.com Steps to Reproduce Product: Grok Bot Grok Bot version: current live version on this account …

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

提示词

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

怎么复制

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

风险与限制

• 定时运行会持续消耗额度：频率从低开始，跑稳再加
• 作者的结果不保证能复现，以原帖为准

用量预估

用金属计算器估一下