{"version":"2.1.275","anchor":"new-memory-mode-session-log-entry-type-has-no-writer-call","canonical_anchor":"new-memory-mode-session-log-entry-type-has-no-writer-call","heading":"Session 'context collapse' tracking replaced with 'memory mode' stamps","tier":"soon","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/new-memory-mode-session-log-entry-type-has-no-writer-call","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Session 'context collapse' tracking replaced with 'memory mode' stamps\n\nClaude Code replaced its old context-collapse (marble-origami) session tracking with a new memory-mode event system\n\n**Unclear.** What triggers a memory-mode stamp once the writer is called, and what the feature is for, is not stated.\n\n**What**\n\n- A new `memory-mode` session-log entry type records when memory mode turns on or off, along with a reason (`paused`, `session_shape`, or `server_off`) and the account involved; these entries are appended to a per-session ledger and merged with an \"accumulate\" policy.\n\n- The old `marble-origami-commit`\/`snapshot`\/`reset` tracking, and its `contextCollapseCommits`\/`contextCollapseSnapshot` fields, have been removed entirely from session state, sync broadcasts, and serialization, replaced by these `memory-mode` entries and a new `memoryModeStamps` array threaded through session loading, resuming, and merging.\n\n- Forking a conversation now carries these `memoryModeStamps` over into the new forked session's metadata.\n\n**Why**\n\nThis 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.\n\n- Area: Sessions\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}