Team memory sync now holds onto local-only files instead of dropping them when its sync record is broken
Team and organization shared-memory sync now has a "held" state. If a memory store's local folder loses its usable record of what's already been synced (its .memory-sync manifest becomes untrustworthy), Claude Code no longer discards or overwrites the local memory files. Instead it keeps them on disk, tracks them in a heldLocal list, and notifies the user that "Memory sync for the ... memory store is off for now." When sync recovers, it reconciles which held files were edited, deleted, or already appeared on the server, tells the user sync "is back on," and records a new tengu_team_mem_rejoin telemetry event.
This protects local memory edits from being silently lost when sync state gets corrupted, and gives a clear signal to the user about when sync has paused and resumed.
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