{"version":"2.1.273","anchor":"new-automem-path-allowlist-gate-restricting-which-files-can","canonical_anchor":"new-automem-path-allowlist-gate-restricting-which-files-can","heading":"New AutoMem path-allowlist gate restricting which files can be scanned as pinned memory","tier":"internal","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/new-automem-path-allowlist-gate-restricting-which-files-can","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### New AutoMem path-allowlist gate restricting which files can be scanned as pinned memory\n\nAutoMem file scanning now filters candidate files against an allowed-paths list before reading them\n\n**What**\n\nA new function filters the files AutoMem and AutoMemPinned would scan as pinned memory, keeping only those within the workspace root's allowed paths. This filter runs before file headers are scanned, and is used both when building the AutoMem index and when identifying pinned memory candidates.\n\n**Why**\n\nThis prevents AutoMem from scanning memory files outside the paths it's permitted to read.\n\n- Area: Memory\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}