Sweep 19 Sep 2026 · 02:36Z Build v2.1.278 500 read Stable v2.1.267 Latest v2.1.278 Next v2.1.278 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.275 ·

Session 'context collapse' tracking replaced with 'memory mode' stamps

Claude Code replaced its old context-collapse (marble-origami) session tracking with a new memory-mode event system

TierNothing to try yethow much it should matter to you
Useful2my rating, 1 to 5
Signal3worth watching, 1 to 5
AreaSessionswhat it touches
KindIn Developmentin v2.1.275,
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-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.
  • 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.
  • Forking a conversation now carries these memoryModeStamps over 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.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhat triggers a memory-mode stamp once the writer is called, and what the feature is for, is not stated.

See this entry in the whole of v2.1.275 →