Under the hood
Useful1 Signal2
Prompt cache-break diagnostics are written to a per-session temp file instead of only memory.
What's wrong with this entry?
Anonymous. No account, no email.
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.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.239
Stall detection separates real hangs from clock jumps
Both mention diagnostic
-
v2.1.239
Warn-once budgets are now tracked per host rather than per process
Both mention diagnostic
-
v2.1.239
Message list warnings and the permission bell join the per-host registry
Both mention diagnostic