{"version":"2.1.314","anchor":"auto-memory-directory-gate-tengu-linked-cake-removed-from-th","canonical_anchor":"auto-memory-directory-gate-tengu-linked-cake-removed-from-th","heading":"The auto memory folder check can no longer be turned off remotely","tier":"notice","area":"Memory","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/auto-memory-directory-gate-tengu-linked-cake-removed-from-th","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### The auto memory folder check can no longer be turned off remotely\n\nClaude Code now always skips settings sources that fail its check when finding autoMemoryDirectory, with no remote switch to undo it\n\n**What**\n\nWhen Claude Code works out `autoMemoryDirectory`, the setting that chooses the folder where auto memory is stored, it skips settings sources that fail a check. That skipping used to sit behind a switch Anthropic's server could turn off. The switch is gone, and the skipping now always happens.\n\n**Why**\n\nThe protection that stops some settings sources from choosing where auto memory is written is now permanent and can no longer be disabled from the server.\n\n- Flag `tengu_linked_cake`: Not enough to say (read for one account on one subscription tier against v2.1.314; this account: no value returned, anonymous baseline: no value returned, compiled default: not a boolean we can read) 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: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}