抄作业 / 警告 / Grok Bot

做了什么

Staff: local-CLI orchestration (including Cursor CLI), always-allow local execution, and authenticated browser sessions are intended Grok Bot use; third-party ToS stay separate, bots share one computer, and a continuous Pro orchestrator burns the weekly pool fast.

场景

周报 / 简报

资料完整度

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

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

来源原文摘录

I’m exploring Grok Bot since it has came to Cursor Pro - as a persistent personal-computing orchestrator and want to confirm that the intended workflow is acceptable under Cursor’s ToS before I automate it. The intended setup is: • Grok Bot has owner-authorized Execution on Local Computer access to my own PC. • A persistent Manager Bot periodically observes local project/workflow state using read-only filesystem, Git, process, and application inspection. • It runs my own local scripts and coordinates coding/research tools that I already have legitimately installed and authenticated Codex CLI,

展开全文

Cursor CLI, Antigravity CLI, and OpenCode. • It may invoke those CLIs to perform work that I have delegated under standing local authority policies. • …

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

效果截图

提示词

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

怎么复制

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

风险与限制

• 这是一条额度/故障反馈（警告），不是可复制的作业。
• 用到浏览器或网页登录：最耗额度，能用 connector 就别开浏览器
• 定时运行会持续消耗额度：频率从低开始，跑稳再加
• 作者的结果不保证能复现，以原帖为准

用量预估

用金属计算器估一下