Unclear What the confirmation check requires before a file missing on disk is deleted from shared memory is not clear.
Claude Code can keep its memory files, notes it saves between sessions, in sync with shared stores. It scans the files on disk to work out what to sync. In "corroborate" mode, a file that is missing on disk and passes a confirmation check is now queued for deletion from shared memory on the first scan.
Before, a deletion needed one of these:
- the file to be missed on two scans, plus a time delay
- immediate mode
The mode comes from a remote setting. When the server sends nothing, it falls back to "corroborate".
This changes when synced memory files are removed from shared memory. A file that goes missing on your machine can now be deleted remotely sooner than before.
tengu_mem_push_delete_mode Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.323: not a boolean we can read
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.323. It isn't a statement about your account. What a flag value here can and cannot tell you
What the confirmation check requires before a file missing on disk is deleted from shared memory is not clear.