3 people reported
All time, since Sep 22.
Resume re-writes prompt cache
“This happens on every resume, with or without a gap, and with both the 5-minute and the 1-hour TTL.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/claude-code/issues/3270/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Print mode re-writes conversation history to prompt cache each resume. cache_read_input_tokens stays pinned at the system/tools prefix on some models while the whole conversation layer is re-written; Haiku or Sonnet sometimes unaffected.
Is this your bug?
File my report- Where
- Headless print mode
- Versions
- 2.1.280 to 2.1.292
- Platforms
- Linux, Windows
- How bad
- Breaks a normal workflow. Some reports say it used to work.
Part of: Prompt cache misses and re-writes11 bugs
- Interactive sessions get 5m cache TTL18 people
- Sleep re-sends full agent context4 people
- Warm prompt cache fully missed2 people
- CLAUDE.md cache not shared3 people
- Cross-session prompt cache misses2 people
- Prompt cache misses after system message3 people
- Subagent prompt cache expires2 people
- Background agent summary requests12 people
- Context after prompt breaks cache4 people
- Subagent resume cache miss4 people
Not quite your bug?
- Resume drops concurrent turns2 people
Original reports3, newest first
claude -pmisses the prompt cache after a turn without thinking (Opus 5.5, Fable 5.1, Sonnet 5.5)#100065- v2.1.290: --resume on opus-5-5/sonnet-5-5 re-writes the whole history to the prompt cache every time (haiku unaffected)#99833
- Opus 5.5 / Fable 5.1 in
-pmode re-write the whole conversation cache every turn (Sonnet caches fine;totalTokensReminder: offdoes not help)#96163