抄作业 / 警告 / Grok Bot

做了什么

Cursor forum bug report claiming grok-bot-default cache stops surviving 5–60 minute gaps after 2026-09-24 06:03 UTC, driving roughly 12× quota for the same traffic.

场景

周报 / 简报 盯 PR / 仓库

资料完整度

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

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

来源原文摘录

Where does the bug appear (feature/product)? Grok Bot Describe the Bug At 2026-09-24 06:03 UTC, grok-bot-default usage rows change in two ways at the same moment: • Almost every row starts reporting an explicit cache-write column (previously almost all input was “without cache write”). • Cache no longer survives a gap longer than about five minutes. Same traffic before and after that timestamp: • Gap 5–60 minutes: before 06:03 UTC most turns still hit cache; after 06:03 UTC almost every turn is a cold rewrite (cache read 0, full context written again). • Gap under ~5 minutes: hit rate is

展开全文

almost unchanged. • After 06:03 UTC a repeated row shape appears: cache read exactly 565 tokens, then a large cache write. Only a 565-token prefix is reused. This is not the usual “each turn re-reads the conversation.” That already appears as cache read. After 06:03 UTC a quiet 15–60 …

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

提示词

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

怎么复制

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

风险与限制

• 这是一条额度/故障反馈（警告），不是可复制的作业。
• 作者的结果不保证能复现，以原帖为准

用量预估

用金属计算器估一下