What probably matters to youSection of the release
Unclear It is not known exactly what is kept across a restart when carry_across_restarts is true.
What
Claude 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.
When it is on, the extractor that works through an MCP server saves and restores where it was:
its cursor, meaning how far through the conversation it has read
its turn count
the time of its next scheduled pass
A 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.
Why
In 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.
