{"version":"2.1.304","anchor":"post-turn-memory-config-gains-a-carry-across-restarts-option","canonical_anchor":"post-turn-memory-config-gains-a-carry-across-restarts-option","heading":"Memory extraction can keep its place across worker restarts","tier":"use","area":"Memory","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/post-turn-memory-config-gains-a-carry-across-restarts-option","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Memory extraction can keep its place across worker restarts\n\nA new carry_across_restarts option lets post-turn memory extraction save and restore its progress when its worker restarts\n\n**Unclear.** It is not known exactly what is kept across a restart when `carry_across_restarts` is true.\n\n**What**\n\nClaude Code can pull memories out of a conversation after each turn. The settings for this, read from `CLAUDE_CODE_POST_TURN_MEMORY_CONFIG` or a hosted config, gain a yes\/no option, `carry_across_restarts`, exposed as `carryAcrossRestarts`. It is false when absent, and forced off when `CLAUDE_CODE_POST_TURN_MEMORY_SYNC` is set.\n\nWhen it is on, the extractor that works through an MCP server saves and restores where it was:\n\n- its cursor, meaning how far through the conversation it has read\n\n- its turn count\n\n- the time of its next scheduled pass\n\nA stored record holds turns, cursor, tail and passAt. A resumed worker logs \"[extractMemories] (mcp) resumed from the previous worker:\" with how many turns have ended since the last pass and whether the cursor was restored. Before, this was kept only in memory and lost on a restart.\n\n**Why**\n\nIn practice, a memory worker that restarts can pick up where the last one stopped instead of starting from scratch. Nothing changes unless the config turns the option on.\n\n- Area: Memory\n- Names: `CLAUDE_CODE_POST_TURN_MEMORY_CONFIG`, `carry_across_restarts`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}