{"version":"2.1.285","anchor":"memory-saved-rows-can-be-rendered-for-account-memory","canonical_anchor":"memory-saved-rows-can-be-rendered-for-account-memory","heading":"Conversation shows a summary when memory is saved to your account","tier":"notice","area":"Memory","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/memory-saved-rows-can-be-rendered-for-account-memory","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Conversation shows a summary when memory is saved to your account\n\nSaved-memory notices in the conversation now say when memory is local, and memory saved to your account gets its own summary\n\n**Unclear.** It is not clear what turns on account memory or who can use it.\n\n**What**\n\nWhen Claude Code saves something to memory, it shows a notice in the conversation. Memory is the notes Claude Code keeps so it can recall them later. These notices now say when the memory was saved locally, on your own machine.\n\nMemory saved to your account now gets its own summary with:\n\n- a header\n\n- a short hint\n\n- the paths of the files that were saved\n\n- lines from the saved content\n\nIn the previous build these notices fell back to an older, plainer layout.\n\n**Why**\n\nYou can now see where a memory went and what was stored in it, so a save to your account is easier to tell apart from a local one.\n\n- Area: Memory\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}