{"version":"2.1.292","anchor":"memory-tool-results-can-now-carry-withheld-memory-entries","canonical_anchor":"memory-tool-results-can-now-carry-withheld-memory-entries","heading":"Tool results can now report memory entries that were held back","tier":"internal","area":"Memory","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/memory-tool-results-can-now-carry-withheld-memory-entries","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Tool results can now report memory entries that were held back\n\nTool results can now include a list of withheld memory entries, each with its path and a stated reason\n\n**What**\n\nClaude Code now accepts a new kind of tool result content, `withheld_memory`. It names who withheld the entries and lists them. Each entry gives a path, a path for display, and a reason from a fixed set of known reasons.\n\n**Why**\n\nThis points to memory entries being kept back from Claude with a stated reason.\n\n- Area: Memory\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}