{"version":"2.1.285","anchor":"turn-loop-gets-phase-tracking-and-early-memory-context-kick","canonical_anchor":"turn-loop-gets-phase-tracking-and-early-memory-context-kick","heading":"Memory context starts loading earlier in each session","tier":"notice","area":"Memory","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/turn-loop-gets-phase-tracking-and-early-memory-context-kick","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Memory context starts loading earlier in each session\n\nClaude Code now starts loading memory context early in a session, checks it again after each turn, and times each stage of a turn\n\n**Unclear.** It is not clear whether the setting that groups task notifications changed in this release or only appears differently in the code.\n\n**What**\n\nClaude Code now starts loading its memory context, the saved notes it brings into a conversation, early in the session, and checks it again after each turn. The loop that runs each turn also now records which stage it is in, such as waiting for the session to start, opening a turn, running tools and sitting idle.\n\nThe grouping of task notifications is controlled by a remote setting that falls back to on when the server sends nothing.\n\n**Why**\n\nMemory context should be ready sooner, and the time each stage of a turn takes can now be measured.\n\n- Flag `tengu_swirling_meteor`: Not enough to say (read for one account on one subscription tier against v2.1.285; this account: no value returned, anonymous baseline: no value returned, compiled default: on) 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.\n- Area: Memory\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}