Unclear It is not stated which settings sources fail the new check, so it is unclear whether a project-level autoMemoryDirectory is still honored.
When Claude Code works out the autoMemoryDirectory setting, which chooses the folder where auto memory is stored, it now skips settings sources that fail a new check. Before, it looked through every source in order and used the first one that set it.
The skipped sources may be project-level ones, such as settings stored in a repository. This behaviour is on unless it is switched off remotely.
This stops a repository's own settings from redirecting where Claude Code writes its memory files.
tengu_linked_cake Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.295: on
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.295. It isn't a statement about your account. What a flag value here can and cannot tell you
It is not stated which settings sources fail the new check, so it is unclear whether a project-level autoMemoryDirectory is still honored.
New in this build: tengu_linked_cake