{"version":"2.1.275","anchor":"team-memory-multistore-sync-gains-a-new-basis-materializatio","canonical_anchor":"team-memory-multistore-sync-gains-a-new-basis-materializatio","heading":"Team-memory multistore sync gains a new basis-materialization step and richer telemetry","tier":"internal","area":"Team Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/team-memory-multistore-sync-gains-a-new-basis-materializatio","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Team-memory multistore sync gains a new basis-materialization step and richer telemetry\n\nTeam-memory multi-store sync gains a new materialization step and more detailed sync telemetry\n\n**What**\n\nThe routine that syncs team memory across multiple stores now runs an additional step after it materializes the manifest (the record of what should be synced), when a certain internal setting is on. The telemetry event that summarizes each sync also gains three new fields: `off_retries`, `off_store_count`, and `off_pull_failure`, describing stores whose baseline data couldn't be used.\n\n**Why**\n\nThis gives more visibility into cases where a memory store's underlying data is unusable, and adds a step to handle rebuilding a usable basis for that store, which should make multi-store team-memory syncing more resilient to inconsistent stores.\n\n- Flag `tengu_typed_koala`: On for this account, and not off by default (read for one account on one subscription tier against v2.1.275; this account: on, anonymous baseline: on, 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: Team Memory\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}