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

做了什么

Staff (deanrie, 2026-09-11): New Bots keep routines on the server, and the desktop app currently does not fetch webhook POST URL, crsr_ secret, or Authorization—recreate and deep links stay empty; bot cannot emit them. Known issue; temporary wake options are Slack channel message triggers or a schedule (not webhook credentials).

场景

社媒排期 安全与隐私 日程会议 写代码上线

资料完整度

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

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

来源原文摘录

Where does the bug appear (feature/product)? Grok Bot Describe the Bug I created a webhook-triggered routine via the Bot. Opening the routine details on Windows desktop only shows: Enabled toggle, Instructions, “When a webhook fires”, empty run history. There is no gray box with the three click-to-copy fields (POST to URL, Secret crsr_…, Authorization header). Deep links for webhook-url/key/header also do not surface credentials. I am not on iOS—this is desktop 0.47.0. Recreating the routine does not help. The Bot cannot see or emit the URL/key, so external callers cannot use the webhook.

展开全文

Related: Webhook url missing on ios says credentials are desktop-only, but desktop still lacks the fields here. Also filed in-app feedback requesting a reply. Steps to Reproduce • Ask a Grok Bot to create a routine with webhook trigger type webhook. …

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

提示词

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

怎么复制

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

风险与限制

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

用量预估

用金属计算器估一下