DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.
Auto-dream consolidation lock can be storage-backed
Under the hood
Useful2Signal3
Memory
Memory consolidation can take its lock through storage, with the owning process recorded and rollback on failure.
What's wrong with this entry?
Anonymous. No account, no email.
What
When a storage backend is supplied, the lock guarding memory consolidation becomes a stored record holding the owning process id and the last consolidation time, taken with a compare-and-set update, skipped while a live process still holds it, and rolled back if the work fails.
Evidence
[autoDream] rollback failed:
Strings lifted out of the shipped bundle, so the claim above can be checked against them.