{"version":"2.1.280","anchor":"memory-mcp-tool-errors-get-a-larger-truncation-cap-plus-a-re","canonical_anchor":"memory-mcp-tool-errors-get-a-larger-truncation-cap-plus-a-re","heading":"Memory MCP tool errors get a larger truncation cap plus a rewrite hint","tier":"notice","area":"Memory","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/memory-mcp-tool-errors-get-a-larger-truncation-cap-plus-a-re","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Memory MCP tool errors get a larger truncation cap plus a rewrite hint\n\nErrors from the memory tool now allow more text before truncating and tell Claude to re-read the file before rewriting it\n\n**What**\n\nThe built-in `memory` MCP server (Claude Code's system for writing and reading notes that persist across turns, using actions like `memory_read`, `memory_list`, `memory_write`, `memory_str_replace`, `memory_append`, and `memory_delete`) now has a higher limit on how many characters an error message from these actions can contain before it gets cut off. When an error is still long enough to be truncated, Claude Code now appends a note instructing the model to call `memory_read` again on the affected file before attempting to rewrite it.\n\n**Why**\n\nThis reduces the chance that Claude acts on an incomplete error message when a memory operation fails, and steers it to refresh its view of the file's current contents before making further edits, lowering the risk of overwriting or corrupting saved memory.\n\n- Area: Memory\n- Names: `memory_read`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}