{"version":"2.1.257","anchor":"prompt-cache-break-diagnostic-state-persists-to-disk-but-on","canonical_anchor":"prompt-cache-break-diagnostic-state-persists-to-disk-but-on","heading":"Prompt cache-break diagnostic state persists to disk, but only in cowork\/desktop\/remote contexts","tier":"internal","area":"Prompt Caching","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/prompt-cache-break-diagnostic-state-persists-to-disk-but-on","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### Prompt cache-break diagnostic state persists to disk, but only in cowork\/desktop\/remote contexts\n\nPrompt cache-break diagnostics now persist to a file across restarts, but only in cowork, desktop and remote contexts.\n\nPer-agent \"prompt cache break\" diagnostic state, covering the system prompt, tool schema, and related cache diagnostics, can now be hydrated from and written back to a disk file named `cache-break-state-*.json`, so it survives restarts. This on-disk persistence is new, but it only runs in cowork, desktop, and remote contexts, gated behind a check that must resolve true before hydration or writes occur.\n\n- Area: Prompt Caching\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 3\/5"}