CLAUDE_CODE_POST_TURN_MEMORY_CONFIG
A Claude Code environment variable, read out of the shipped bundle. It has been in the build since v2.1.269, including the newest one read.
Three new env vars configure an unreleased 'post-turn memory' feature
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.269.
In the changelogs
6Releases whose published page names CLAUDE_CODE_POST_TURN_MEMORY_CONFIG.
-
v2.1.315
Post-turn memory's
smaller_passgains aformsettingThe
smaller_passblock inCLAUDE_CODE_POST_TURN_MEMORY_CONFIGnow takesform(turnsorinline) and itsmodecan only beofforshadowfound in this entry's text, named in this entry
-
v2.1.304
Post-turn memory config gains a
carry_across_restartssetting, off by defaultCLAUDE_CODE_POST_TURN_MEMORY_CONFIGnow reads acarry_across_restartssetting that is off unless setfound in this entry's text, named in this entry
-
v2.1.283
Post-turn memory config accepts a
role_line_scansettingCLAUDE_CODE_POST_TURN_MEMORY_CONFIGnow reads arole_line_scansetting with three options, and hosted use checks it against its own rulesfound in this entry's text, named in this entry
-
v2.1.282
Post-turn memory config accepts an extract_transport choice
The post-turn memory config now takes an extract_transport option, "tools" or "text", defaulting to "tools"
found in this entry's text, named in this entry
-
v2.1.269
New CLI env var and control for post-turn memory
Three new env vars configure an unreleased 'post-turn memory' feature
found in this entry's text
-
v2.1.269
extractMemories can run through an MCP-based memory server instead of writing files
Background memory extraction can now send memories to an MCP memory server instead of writing local files
found in this entry's text, named in this entry
First cited
2The earliest release whose published evidence quoted CLAUDE_CODE_POST_TURN_MEMORY_CONFIG was v2.1.269, 11 Sep 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.
Presence across releases
1Build by build
49One row per release since the first build this name was read out of. Absent means the build was read and the name was not in it, never mined means no bundle for that release was ever archived, and a declared type or a default is only ever what that release's own bundle stated.
Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the environment variable does. All environment variables.