Team-memory multi-store sync gains a new materialization step and more detailed sync telemetry
The 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.
This 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.
tengu_typed_koala On for this account, and not off by defaultThe flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.
This account: on · anonymous baseline: on · compiled default in v2.1.275: 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.
Read once, for one account on one subscription tier, against v2.1.275. It isn't a statement about your account. What a flag value here can and cannot tell you
New in this build: tengu_typed_koala