{"version":"2.1.323","anchor":"memory-extraction-fork-errors-if-the-api-runs-tools-itself","canonical_anchor":"memory-extraction-fork-errors-if-the-api-runs-tools-itself","heading":"Memory saving refuses tools that run on the API's side","tier":"internal","area":"Memory","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/memory-extraction-fork-errors-if-the-api-runs-tools-itself","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Memory saving refuses tools that run on the API's side\n\nBehind a feature check, the memory-saving pass now allows no API-run tool calls and saves nothing if a request includes such tools\n\n**Unclear.** The feature check was not identified, so whether memory saving stops for you when MCP servers are set up is unknown.\n\n**What**\n\nClaude Code runs a separate pass that picks out things worth saving to memory from your conversation. Behind a feature check, that pass now tells the API that no server-run tool calls are allowed. A server-run tool is one the API carries out itself rather than Claude Code.\n\nIf a request in the pass includes such a tool or MCP servers, it records an error and may save nothing. MCP servers are add-ons that give Claude extra tools through the Model Context Protocol.\n\n**Why**\n\nThe memory pass can no longer make tool calls on the API's side.\n\n- Area: Memory\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}