Sweep 19 Sep 2026 · 02:36Z Build v2.1.278 500 read Stable v2.1.267 Latest v2.1.278 Next v2.1.278 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.273 ·

Auto-memory loading now skipped when reads are fenced outside the working directory

Auto-memory loading is now skipped when a permissions setting fences reads outside the working directory

TierYou'll noticehow much it should matter to you
Useful1my rating, 1 to 5
Signal1worth watching, 1 to 5
AreaMemorywhat it touches
KindImprovementsin v2.1.273,
You'll notice

Auto-memory loading is now skipped when a permissions setting fences reads outside the working directory

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.

Read from
Names in the bundleblockReadsOutsideWorkingDirectories
Since it was published

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.

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
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesA small documentation edit on How Claude remembers your project touched a line naming blockReadsOutsideWorkingDirectories after this was…

See this entry in the whole of v2.1.273 →