Unclear Whether the extraction settings turn this on for any account is not known.
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.
tengu_bramble_lintel Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.304: not a boolean we can read
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.
tengu_passport_quail Off in both readingsThe flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · compiled default in v2.1.304: 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.
Read once, for one account on one subscription tier, against v2.1.304. It isn't a statement about your account. What a flag value here can and cannot tell you
Whether the extraction settings turn this on for any account is not known.