{"version":"2.1.273","anchor":"auto-memory-loading-now-skipped-when-reads-are-fenced-outsid","canonical_anchor":"auto-memory-loading-now-skipped-when-reads-are-fenced-outsid","heading":"Auto-memory loading now skipped when reads are fenced outside the working directory","tier":"notice","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/auto-memory-loading-now-skipped-when-reads-are-fenced-outsid","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Auto-memory loading now skipped when reads are fenced outside the working directory\n\nAuto-memory loading is now skipped when a permissions setting fences reads outside the working directory\n\n**What**\n\nClaude Code's auto-memory feature (which automatically loads memory files) now checks an additional condition before running. If a permissions setting blocks reads outside the current working directory, auto-memory loading is skipped entirely. A new telemetry field, `read_block_fenced`, is recorded when this happens.\n\n**Why**\n\nAuto-memory files can live outside the working directory, so this keeps that read-restriction setting from being silently bypassed by the auto-memory feature.\n\n- Area: Memory\n- Names: `blockReadsOutsideWorkingDirectories`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}