Hey, thanks for the report.
Cache read tokens are generally expected. They mean previously cached context is being reused at a much lower cost than regular input tokens. For example, with Claude Opus 4.6, cache reads cost $0.50 per 1M tokens vs $5.00 per 1M tokens for regular input, so 924K cache read tokens cost roughly the same as about 92K input tokens. More details here: Someone please explain - Why are cache read and write chargeable?
That said, 924K cache read with 0 cache write in what you describe as a new chat is unusual. To investigate, could you share:
- Which model are you using, and is Max mode enabled?
- Do you have any project rules (
.cursorrulesor.cursor/rules) or any MCP servers configured? - A Request ID from one of these high cache read chats. You can get it from the chat context menu (top right) then Copy Request ID.
0 cache write suggests the context was already cached from a prior session. Prompt caching works across chats within a time window, so it’s likely hitting a prefix cache from previous requests. But the size of the cache hit on a simple request is worth looking into.
Let me know and we’ll dig deeper.