{"version":"2.1.295","anchor":"memory-extraction-reports-a-pass-outcome","canonical_anchor":"memory-extraction-reports-a-pass-outcome","heading":"Memory saving now reports how each pass ended","tier":"internal","area":"Memory","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/memory-extraction-reports-a-pass-outcome","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Memory saving now reports how each pass ended\n\nEach memory-saving pass now reports whether it saved, stopped partway, was refused, found nothing to save, or failed\n\n**What**\n\nClaude Code can pull useful facts out of a conversation and save them as memory for later sessions. When one of these saving passes ends, Claude Code now reports how it went, as one of these outcomes:\n\n- saved\n\n- unfinished\n\n- writes refused\n\n- nothing to save\n\n- failed\n\nThe outcome is also reported when saving runs through MCP (a standard way for Claude Code to connect to outside tools) and when the pass hits an error. The report goes to an optional listener, so it only has an effect when a program built on Claude Code chooses to listen for it.\n\n**Why**\n\nPrograms that embed Claude Code can now see whether memory saving actually worked, without having to guess.\n\n- Flag `tengu_bramble_lintel`: Not enough to say (read for one account on one subscription tier against v2.1.295; 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: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}