{"version":"2.1.305","anchor":"memory-save-mcp-calls-get-dedicated-rendering","canonical_anchor":"memory-save-mcp-calls-get-dedicated-rendering","heading":"Memory saves get their own rows in the conversation view","tier":"notice","area":"Memory","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/memory-save-mcp-calls-get-dedicated-rendering","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Memory saves get their own rows in the conversation view\n\nTool calls that save to memory can now show as their own memory-save rows and in tool summaries, and a security warnings list joins the status area\n\n**What**\n\nMCP servers are add-ons that give Claude Code extra tools. Some MCP tools are only shown, not run. Claude Code can now show those as memory-save rows, meaning lines that say something was saved to memory.\n\n- Summaries of a group of tool calls now include their memory-save parts.\n\n- Saves to cloud memory are recognised when messages are drawn on screen.\n\n- The status area gains a list of security warnings.\n\n**Why**\n\nSaves to memory stand out in the conversation instead of looking like any other tool call.\n\n- Area: Memory\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}