{"version":"2.1.323","anchor":"memory-save-request-errors-when-forced-tool-choice-leaves-no","canonical_anchor":"memory-save-request-errors-when-forced-tool-choice-leaves-no","heading":"Memory-save requests that would leave Claude no usable tool now stop with an error","tier":"notice","area":"Memory","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/memory-save-request-errors-when-forced-tool-choice-leaves-no","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Memory-save requests that would leave Claude no usable tool now stop with an error\n\nClaude Code now stops a memory-save request with an error if its tool setup would leave Claude with no tool it can call\n\n**What**\n\nClaude Code now raises an error when a `memory_save` request includes either of these:\n\n- A tool that Anthropic's servers run on their own, rather than one Claude Code runs.\n\n- Tools from MCP servers, which are outside programs that give Claude extra tools.\n\nWith those included, Claude would be left with no tool it could actually call. The error message says to take them off that request.\n\n**Why**\n\nThis guards against a badly set up memory-save request. It now fails with a clear message instead of leaving Claude stuck with nothing to call.\n\n- Area: Memory\n- Names: `memory_save`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}