{"version":"2.1.281","anchor":"memory-store-sync-first-pull-tracking-and-bounded-shutdown","canonical_anchor":"memory-store-sync-first-pull-tracking-and-bounded-shutdown","heading":"Memory store sync: first-pull tracking and bounded shutdown flush","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/memory-store-sync-first-pull-tracking-and-bounded-shutdown","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Memory store sync: first-pull tracking and bounded shutdown flush\n\nMemory syncing skips a startup step until its first pull is due, and waiting git syncs now stop within a time limit at shutdown\n\n**Unclear.** The finding does not give the length of the shutdown time limit.\n\n**What**\n\nClaude Code can keep its memory files in a store synced with git. This release changes that syncing in three ways:\n\n- The watcher that follows memory changes skips its after-startup step while `firstStorePullOwed` is set, meaning the first download from the store has not happened yet.\n\n- In interactive sessions, git syncs that were being held back are now given a time limit to finish when Claude Code shuts down. An interactive session is one where you type at Claude Code directly.\n\n- The notice that git is not on the startup path is shown once per path instead of repeatedly.\n\n**Why**\n\nQuitting Claude Code should no longer hang indefinitely on a waiting memory sync, and the git notice appears less often."}