{"version":"2.1.295","anchor":"automemorydirectory-setting-ignored-from-untrusted-settings","canonical_anchor":"automemorydirectory-setting-ignored-from-untrusted-settings","heading":"Some settings files can no longer choose where auto memory is stored","tier":"notice","area":"Memory","scope":"both","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/automemorydirectory-setting-ignored-from-untrusted-settings","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Some settings files can no longer choose where auto memory is stored\n\nWhen finding autoMemoryDirectory, Claude Code now skips settings sources that fail a new check, so they cannot move the memory folder\n\n**Unclear.** It is not stated which settings sources fail the new check, so it is unclear whether a project-level autoMemoryDirectory is still honored.\n\n**What**\n\nWhen Claude Code works out the `autoMemoryDirectory` setting, which chooses the folder where auto memory is stored, it now skips settings sources that fail a new check. Before, it looked through every source in order and used the first one that set it.\n\nThe skipped sources may be project-level ones, such as settings stored in a repository. This behaviour is on unless it is switched off remotely.\n\n**Why**\n\nThis stops a repository's own settings from redirecting where Claude Code writes its memory files.\n\n- Flag `tengu_linked_cake`: Not enough to say (read for one account on one subscription tier against v2.1.295; this account: no value returned, anonymous baseline: no value returned, compiled default: on) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Memory\n- Names: `autoMemoryDirectory`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: both\n- Heads-up: yes"}