{"version":"2.1.277","anchor":"new-boot-latency-metrics-for-orgteam-memory-store-sync","canonical_anchor":"new-boot-latency-metrics-for-orgteam-memory-store-sync","heading":"New boot-latency metrics for org\/team memory store sync","tier":"internal","area":"Team Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/new-boot-latency-metrics-for-orgteam-memory-store-sync","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### New boot-latency metrics for org\/team memory store sync\n\nNew timing metrics track how long syncing org\/team memory takes at startup\n\n**What**\n\nClaude Code now measures how long it takes to pull the team and user memory store when it starts up, recording this as `memory_store_pull_ms`. It also records `memory_store_pull_boot_spillover_ms`, which measures how much of that pull happened after Claude Code had already reported itself ready for input. These mirror an existing pair of metrics, `memory_context_fetch_ms` and `memory_context_boot_spillover_ms`, that measured similar timing for memory context fetches.\n\n**Why**\n\nThese are internal diagnostics that help identify when memory-store syncing is slow enough to spill over into the time a user is already able to start typing, rather than finishing before startup completes.\n\n- Area: Team Memory\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}