What
Claude 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.
Why
Auto-memory files can live outside the working directory, so this keeps that read-restriction setting from being silently bypassed by the auto-memory feature.
Names in the bundleblockReadsOutsideWorkingDirectories
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up blockReadsOutsideWorkingDirectories, on Claude Code changelog.
* Added Claude apps gateway support for newer Claude Desktop keys in `desktop` policy blocks, including `blockReadsOutsideWorkingDirectories` and `disableBypassPermissionsMode`changelog see the edit
Added since
A small documentation edit on How Claude remembers your project touched a line naming blockReadsOutsideWorkingDirectories after this was published.
When you set it in a project's `.claude/settings.json` or `.claude/settings.local.json`, Claude Code honors it under the same [workspace trust rule as hooks in settings files](/docs/en/permissions#what-runs-before-you-trust-a-folder). Whil…memory see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
A small documentation edit on How Claude remembers your project touched a line naming blockReadsOutsideWorkingDirectories after this was…