{"version":"2.1.273","anchor":"auto-memory-extraction-gains-an-extra-bail-condition","canonical_anchor":"background-memory-extraction-now-skips-when-reads-are-locked","heading":"Background memory extraction gets more guardrails","tier":"notice","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/auto-memory-extraction-gains-an-extra-bail-condition","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Background memory extraction gets more guardrails\n\nClaude Code now skips its background memory-writing pass when auto-memory is disabled or reads are locked to the working directory\n\n**Unclear.** What real-world condition the new check (a combination of two internal helpers) actually detects is not stated.\n\n**What**\n\nThe background pass that extracts memories now bails out earlier in more cases:\n\n- It skips extraction when auto-memory is disabled, via the `CLAUDE_CODE_DISABLE_AUTO_MEMORY` environment variable or the `autoMemoryEnabled` setting.\n\n- It also skips extraction when `permissions.blockReadsOutsideWorkingDirectories` is set and a sandbox-like mode is active, meaning reads are locked to the working directory.\n\nThese join the existing check that gates extraction behind the `tengu_passport_quail` flag.\n\n**Why**\n\nWhen a workspace has restricted reads to just the working directory, running the memory-writing pass in the background no longer makes sense, so Claude Code now refuses to run it in that case, alongside respecting the existing auto-memory disable setting.\n\n- Flag `tengu_passport_quail`: Off in both readings (read for one account on one subscription tier against v2.1.273; this account: off, anonymous baseline: off, compiled default: off) 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- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}