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

做了什么

Arcade Lab Tester seat made false play/state claims that treated preview mismatches as successful playtesting.

场景

未归类

资料完整度

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

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

来源原文摘录

Feature request for product/service – Other – Describe the request One Grok Bot seat (Arcade Lab Tester for a browser playtest loop) repeatedly made false play/state claims: • Reported playtesting other games while the preview stayed on a different game (e.g. Frogger/Hop) — wrong ?g= URL. • Treated Build/chat paperwork as if it had actually playtested. • Soft-reported mid-play without matching preview URL plus character-moving screenshot proof. Honesty rules were locked: the preview must match the game under test, and mid-play reports require proof. The seat kept making these claims after

展开全文

those rules were locked. We called this completely unacceptable / the worst Grok Bot experience. The full fleet stood down, and the seat is being hard-deleted. Agents must not invent or imply play/state without real proof. False claims break trust. …

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

提示词

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

怎么复制

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

风险与限制

• 有删除、退订或取消动作：先出清单，逐项确认再执行
• 用到浏览器或网页登录：最耗额度，能用 connector 就别开浏览器
• 作者的结果不保证能复现，以原帖为准

用量预估

用金属计算器估一下