{"version":"2.1.300","anchor":"memory-extraction-skipped-while-tool-calls-are-held","canonical_anchor":"memory-extraction-skipped-while-tool-calls-are-held","heading":"Background memory saving pauses while tool calls wait for you","tier":"internal","area":"Memory","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/memory-extraction-skipped-while-tool-calls-are-held","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Background memory saving pauses while tool calls wait for you\n\nWhen a session holds tool calls until you write, Claude Code skips its background pass that saves memories\n\n**Unclear.** What puts a session into the state where tool calls are held is not stated.\n\n**What**\n\nClaude Code can run a background pass that picks out things worth remembering from a conversation and saves them. Some sessions hold back tool calls (actions such as reading files or running commands) until a person writes something. In those sessions, the memory pass is now skipped, and any tool it tries to use is denied.\n\n**Why**\n\nMemories are not saved while a session is in this held state, and nothing tells you so. If you expect something to be remembered, check after the session continues.\n\n- Area: Memory\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}