Subagents now start with their saved memory already loaded, unless you set the disable-auto-memory variable.
What's wrong with this entry?
Subagent system prompts are now built with the agent's saved memory read in advance and handed to the prompt builder, so an agent sees what it recorded previously without a separate lookup. This only happens when auto-memory is on and a stored memory file exists; setting CLAUDE_CODE_DISABLE_AUTO_MEMORY turns it off and prompts are built exactly as before.
- The memory text is read asynchronously before prompt construction and passed as
primedAgentMemoryinto every agent definition's prompt builder. - With auto-memory off or no stored memory present, the helper returns undefined and the prompt is unchanged.
primedAgentMemory
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.248
CLAUDE_CODE_ENABLE_AUTO_MODE is no longer required, or read at all
Both mention disable auto
-
v2.1.248
Auto-memory is off in restricted sessions
Both mention disable auto
-
v2.1.219
Org memory no longer auto-selects a lone candidate store
Both mention disable