{"version":"2.1.301","anchor":"memory-scope-filter-helper-and-git-in-progress-state-refacto","canonical_anchor":"memory-scope-filter-helper-and-git-in-progress-state-refacto","heading":"Claude Code now works out which memory scopes apply in the current session","tier":"internal","area":"Memory","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/memory-scope-filter-helper-and-git-in-progress-state-refacto","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Claude Code now works out which memory scopes apply in the current session\n\nClaude Code now decides which memory scopes are available from the current context, and Managed is always one of them\n\n**What**\n\nMemory is where Claude Code keeps instructions and notes that carry from one session to the next. Each place it can be kept is called a scope. Claude Code now decides which scopes are available in the current context:\n\n- User: available only when a certain condition does not hold\n\n- Project and Local: available only when there is a project\n\n- AutoMem: available when either of those applies\n\n- Managed: always available\n\nSeparately, the check that tells whether a git cherry-pick or revert is still in progress now reads its list of marker files from one shared place. What it detects is the same.\n\n**Why**\n\nThis may decide which memory scopes you can choose from.\n\n- Area: Memory\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}