{"version":"2.1.251","anchor":"memory-context-fetched-in-the-background-before-a-turn-start","canonical_anchor":"memory-context-fetched-in-the-background-before-a-turn-start","heading":"Memory context fetched in the background before a turn starts","tier":"soon","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/memory-context-fetched-in-the-background-before-a-turn-start","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Memory context fetched in the background before a turn starts\n\nMemory context can be fetched in the background as a turn begins, behind an off flag.\n\n**What**\n\nNew code starts fetching memory context for the current host as soon as a query begins and joins the result later, recording how long the fetch took and how much of it overlapped with the start of the turn. It sits behind the same off-by-default memory flag as the stale-read warnings.\n\n**Details**\n\n- Timing is reported as a duration in milliseconds plus an overlap measure.\n\n**Evidence**\n\n`memory_context_fetch_ms`\n\n- Area: Memory\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}