{"version":"2.1.232","anchor":"cache-break-diagnostics-kept-in-a-per-session-file","canonical_anchor":"cache-break-diagnostics-kept-in-a-per-session-file","heading":"Cache-break diagnostics kept in a per-session file","tier":"internal","area":"Diagnostics","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/cache-break-diagnostics-kept-in-a-per-session-file","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Cache-break diagnostics kept in a per-session file\n\nPrompt cache-break diagnostics are written to a per-session temp file instead of only memory.\n\n**What**\n\nDiagnostic state about prompt cache breaks is now written to a file in the temp directory named per session, instead of living only in memory.\n\n**Details**\n\n- 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.\n- Entries belonging to other sessions are evicted first when the cap is hit.\n- Writing is behind a separate enablement check, so persistence does not necessarily happen in every session.\n\n**Evidence**\n\n`cache-break-state-`\n\n- Area: Diagnostics\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}