Group of 5 Nothing to try yet
Claude Code replaced its old context-collapse (marble-origami) session tracking with a new memory-mode event system
What
- A new
memory-modesession-log entry type records when memory mode turns on or off, along with a reason (paused,session_shape, orserver_off) and the account involved; these entries are appended to a per-session ledger and merged with an "accumulate" policy. - The old
marble-origami-commit/snapshot/resettracking, and itscontextCollapseCommits/contextCollapseSnapshotfields, have been removed entirely from session state, sync broadcasts, and serialization, replaced by thesememory-modeentries and a newmemoryModeStampsarray threaded through session loading, resuming, and merging. - Forking a conversation now carries these
memoryModeStampsover into the new forked session's metadata.
Why
This replaces an older mechanism for tracking memory/context state with a clearer one that records why memory mode changed, and preserves that history when a session is forked.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
What triggers a memory-mode stamp once the writer is called, and what the feature is for, is not stated.