{"version":"2.1.267","anchor":"prompt-cache-break-diagnostics-reworked-with-a-new-bypass-p","canonical_anchor":"prompt-cache-break-diagnostics-reworked-with-a-new-bypass-p","heading":"Prompt-cache-break diagnostics reworked, with a new bypass path for one source","tier":"internal","area":"Compaction","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/prompt-cache-break-diagnostics-reworked-with-a-new-bypass-p","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Prompt-cache-break diagnostics reworked, with a new bypass path for one source\n\nInternal prompt-cache-break diagnostics were restructured, with a new bypass for one message source and for disk-seeded cache state\n\n**What**\n\nClaude Code's internal logic for detecting \"prompt cache breaks\" (when a cached prompt prefix stops being reusable) was reorganized: the threshold logic for deciding when a break occurred now lives in a shared helper. A new branch handles the case where a specific message source reports no session state, logging a diagnostic event with request ID and cache token counts instead of just returning early. There's also a new early exit that skips break diagnosis entirely when the cache state was seeded from disk.\n\n**Why**\n\nThis is internal diagnostic plumbing rather than a user-facing feature; it should make prompt-cache-break issues easier to trace by giving certain edge cases (missing session state, disk-seeded cache) their own explicit handling instead of falling through to generic logic.\n\n- Area: Compaction\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}