{"version":"2.1.293","anchor":"memory-extraction-person-prompt-captured-and-cited-and-ski","canonical_anchor":"memory-extraction-person-prompt-captured-and-cited-and-ski","heading":"Saved memories are now linked to the prompt that produced them","tier":"internal","area":"Memory","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/memory-extraction-person-prompt-captured-and-cited-and-ski","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Saved memories are now linked to the prompt that produced them\n\nWhen Claude Code saves memories from your conversation through MCP, it now passes along the prompt that led to them\n\n**Unclear.** It is not clear whether the change to the skip check alters when memories are written directly or only renames a value.\n\n**What**\n\nClaude 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.\n\nThe check that decides when to skip writing memories directly also changed which value it looks at.\n\n**Why**\n\nEach saved memory can now be traced back to the prompt that produced it.\n\n- Flag `tengu_bramble_lintel`: Not enough to say (read for one account on one subscription tier against v2.1.293; this account: no value returned, anonymous baseline: no value returned, compiled default: 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.\n- Area: Memory\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}