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

做了什么

Staff (deanrie, 2026-09-16): with correct repo access and filters, the GitHub issue-assigned trigger still does not fire for github.com repos (known server-side); filter matches the assigner; no user-facing event log yet; temporary workaround is a scheduled routine (webhook may also be blocked by the 171324 panel bug until 0.53.0).

场景

盯 PR / 仓库 日程会议

资料完整度

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

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

来源原文摘录

Where does the bug appear (feature/product)? Grok Bot Describe the Bug A Bot-owned routine with a GitHub “issue assigned” trigger never starts, even though the assignment event exists on GitHub, the Cursor GitHub App has access to the repository, and the Bot handles the same issue fine when asked in chat. Setup • A Bot owns one routine, shown in the routine panel as: When an issue is assigned in <my-account>/<private-repo> (by @<second-account>), no schedule, status Active. • <second-account> is a separate GitHub user added as a collaborator on that private repo. A server-side job uses its

展开全文

token to create an issue via the REST API with assignees: ["<my-account>"], plus labels. • The issue timeline confirms the event: assigned, actor <second-account>, assignee <my-account>. …

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

提示词

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

怎么复制

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

风险与限制

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

用量预估

用金属计算器估一下