{"version":"2.1.273","anchor":"automem-file-scanning-gated-off-in-a-new-lu-mode-and-restr","canonical_anchor":"automem-file-scanning-gated-off-in-a-new-lu-mode-and-restr","heading":"AutoMem file scanning gated off in a new 'LU' mode and restricted by directory allow-list","tier":"soon","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/automem-file-scanning-gated-off-in-a-new-lu-mode-and-restr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### AutoMem file scanning gated off in a new 'LU' mode and restricted by directory allow-list\n\nAutoMem file scanning now checks a new mode condition and restricts which files it can scan\n\n**Unclear.** The finding does not say what the new mode condition represents or when it evaluates to false.\n\n**What**\n\nAutoMem (Claude Code's automatic memory-file handling) now runs an extra condition check before scanning for pinned or automatic memory files, in addition to its existing checks. It also now filters candidate files against a computed list of allowed directories, so only files whose path falls under that allowed set can be scanned as memory headers.\n\n**Why**\n\nThis narrows where AutoMem will look for memory files, reducing the chance it picks up files outside the intended locations.\n\n- Area: Memory\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}