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

做了什么

Staff (deanrie): Launching a Cloud Agent from Grok Bot can falsely hit the “Privacy Mode (Legacy)” check after a recent release even when your account uses current Privacy Mode—Cursor Desktop launch still works; sign-out/reset won’t help; staff are tracking a server-side fix.

场景

安全与隐私 调研监控

资料完整度

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

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

来源原文摘录

Where does the bug appear (feature/product)? Grok Bot Describe the Bug Environment: macOS, Cursor Desktop (latest) Grok Bot desktop app Repo: private GitHub repo (JSG CMS) Issue: When I ask Grok Bot to launch a Cloud Agent, it fails with: “Cloud agents are not supported in Privacy Mode (Legacy).” However, my Privacy Settings are set to the current Privacy Mode (not Legacy). The setting reads: “Privacy Mode — Active — No training. Code may be stored for Cloud Agent, Team Rules, and other features.” (screenshot attached). Key finding: Launching a Cloud Agent from Cursor Desktop (Cloud dropdown)

展开全文

works perfectly on the same account, same repo, same moment. Only the Grok Bot launch path is broken. Steps to reproduce: Confirm Privacy Mode is set to current (not Legacy) in Cursor Settings → Privacy Launch a Cloud Agent from Cursor Desktop → works …

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

效果截图

提示词

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

怎么复制

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

风险与限制

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

用量预估

用金属计算器估一下