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 ·

Background memory extraction gets more guardrails

Claude Code now skips its background memory-writing pass when auto-memory is disabled or reads are locked to 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,
Group of 2 You'll notice

Claude Code now skips its background memory-writing pass when auto-memory is disabled or reads are locked to the working directory

What

The background pass that extracts memories now bails out earlier in more cases:

These join the existing check that gates extraction behind the tengu_passport_quail flag.

Why

When 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.

Read from
Names in the bundleblockReadsOutsideWorkingDirectories
Feature flag
tengu_passport_quail Off in both readings

The flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.

This account: off · anonymous baseline: off · compiled default in v2.1.273: 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.

Read once, for one account on one subscription tier, against v2.1.273. It isn't a statement about your account. What a flag value here can and cannot tell you

What the documentation says
permissions.blockReadsOutsideWorkingDirectories Claude Code changelog modified, high confidence * Fixed Bash commands with two directory changes, a subshell, or a `cd`+`git` chain skipping the prompt under `permissions.blockReadsOutsideWorkingDirectories` in bypass and auto mode see the edit
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
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agreespermissions.blockReadsOutsideWorkingDirectories on Claude Code changelog
Anthropic's release notes agreeFixed Bash commands the permission checker cannot fully analyze skipping the prompt under permissions.blockReadsOutsideWorkingDirectories…

See this entry in the whole of v2.1.273 →