{"version":"2.1.300","anchor":"memory-extraction-skipped-in-coordinator-mode-when-memory-se","canonical_anchor":"memory-extraction-skipped-in-coordinator-mode-when-memory-se","heading":"Memory saving can be skipped in coordinator mode with a memory server","tier":"internal","area":"Memory","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/memory-extraction-skipped-in-coordinator-mode-when-memory-se","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Memory saving can be skipped in coordinator mode with a memory server\n\nIn coordinator mode with an MCP memory server, Claude Code now skips background memory saving when no suitable tool is visible\n\n**Unclear.** Which tool counts as suitable, and so whether memory saving still runs in a given setup, is not shown.\n\n**What**\n\nClaude Code can save memories in the background, pulling details from your conversation to keep for later. Memories can be kept by an MCP server, a separate program Claude Code connects to for extra tools. In coordinator mode, Claude Code now checks the tools it can see. If none of them is a suitable tool for this, it skips the memory saving and notes that in its log.\n\n**Why**\n\nCoordinator-mode sessions that keep memories on an MCP memory server will not save memories in the background unless a suitable tool is visible.\n\n- Flag `tengu_passport_quail`: Off in both readings (read for one account on one subscription tier against v2.1.300; this account: off, anonymous baseline: off, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Memory\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}