Unclear What real-world condition the new check (a combination of two internal helpers) actually detects is not stated.
What
The background pass that extracts memories now bails out earlier in more cases:
- It skips extraction when auto-memory is disabled, via the
CLAUDE_CODE_DISABLE_AUTO_MEMORYenvironment variable or theautoMemoryEnabledsetting. - It also skips extraction when
permissions.blockReadsOutsideWorkingDirectoriesis set and a sandbox-like mode is active, meaning reads are locked to the working directory.
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.
tengu_passport_quail Off in both readingsThe 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 real-world condition the new check (a combination of two internal helpers) actually detects is not stated.