Claude Code v2.1.232 ·
Cache-break diagnostics kept in a per-session file
Prompt cache-break diagnostics are written to a per-session temp file instead of only memory.
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
DiagnosticsArea: what it touches
Internal ChangesKind: in v2.1.232,
Internal ChangesSection of the release
What
Diagnostic state about prompt cache breaks is now written to a file in the temp directory named per session, instead of living only in memory.
Details
- The directory's permissions are checked before each access, loading is capped by both file size and entry count, and the file is deleted once empty.
- Entries belonging to other sessions are evicted first when the cap is hit.
- Writing is behind a separate enablement check, so persistence does not necessarily happen in every session.
Evidence
cache-break-state-
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
See this entry in the whole of v2.1.232 →
