{"version":"2.1.274","anchor":"auto-memory-memory-index-now-returned-alongside-status","canonical_anchor":"terminal-dialog-schema-gains-a-memories-listing","heading":"Memory dialogs and control responses now include a full list of saved memories","tier":"notice","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/auto-memory-memory-index-now-returned-alongside-status","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Memory dialogs and control responses now include a full list of saved memories\n\nThe memory status dialog and its control-protocol response now list every saved auto-memory file, not just folder counts\n\n**What**\n\n- The terminal's status dialog schema now includes an optional `memories` field, listing saved auto-memory entries drawn from the `MEMORY.md` index and each file's modification time, capped at 200 entries.\n\n- The status call that reports auto-memory\/auto-dream status now also returns a `memories` array whenever memory folders are present.\n\n- A new schema describes a single memory entry: its name (a relative path, or `\"MEMORY.md\"` for the index file), its absolute path, an optional description and type (`user`, `feedback`, `project`, or `reference`) from its frontmatter, and its last-modified time.\n\n- The `get_memory_dialog` control-protocol response, used by hosts that build their own `\/memory` UI, now includes this same `memories` array alongside the existing folder list.\n\n**Why** Tools and custom UIs built on top of Claude Code can now show users exactly which memories are saved, with descriptions and types, instead of only folder-level summaries.\n\n- Area: Memory\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}