Unclear It is not clear whether the change to the skip check alters when memories are written directly or only renames a value.
Claude Code can review your conversation and save useful points as memories. Both the pass that runs when the session goes idle and the pass that runs at the end now keep a copy of your prompt that led to those memories. In the mode that works through MCP, the Model Context Protocol for connecting outside tools, that prompt is passed along with the request as the event the memories cite.
The check that decides when to skip writing memories directly also changed which value it looks at.
Each saved memory can now be traced back to the prompt that produced it.
tengu_bramble_lintel 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.293: not a boolean we can read
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.293. It isn't a statement about your account. What a flag value here can and cannot tell you
It is not clear whether the change to the skip check alters when memories are written directly or only renames a value.