Unclear What the "recorded" mode does differently from the others is not clear.
What
Shared memory is a set of files Claude Code keeps and syncs so that Claude can remember things between sessions. Pushing is sending local changes to those files back out. The setting that controls how deletions are pushed has a new option.
CLAUDE_CODE_MEMORY_PUSH_DELETE_MODEnow acceptsrecorded, in addition toimmediate,neverandcorroborate. Any other value still falls back tocorroborate.- The mode is read from that environment variable first, then from the remote setting
tengu_mem_push_delete_mode, which defaults tocorroborate. - In
nevermode, deletions are recorded only when thetengu_cozy_teacupgate is on and the environment variable is not set. - Claude is now told that it can delete a file from shared memory by running a command that is only an
rmof the file's full path.
Nothing has been read about either tengu_mem_push_delete_mode or tengu_cozy_teacup.
Why
Deleting a shared-memory file can now be recorded and pushed as a named removal, not just handled by the earlier modes. If you set CLAUDE_CODE_MEMORY_PUSH_DELETE_MODE, recorded is now a valid value instead of falling back to the default.
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.318: 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.318. It isn't a statement about your account. What a flag value here can and cannot tell you
What the "recorded" mode does differently from the others is not clear.