Under the hood
Useful1 Signal1
Prompt-history saves blocked by another process are now tracked separately from real write failures.
What's wrong with this entry?
Anonymous. No account, no email.
What
When saving prompt history fails because another process held the lock, it is reported under its own key rather than counted as a generic write failure.
Details
- Detected from the error's telemetry code being lock-contended or lock-acquire-failed; the distinct key is
history_save_lock_failed.
Evidence
history_save_lock_failed
Strings lifted out of the shipped bundle, so the claim above can be checked against them.