What it is
Team memory sync adds structured failure reasons for loading its sync baseline, plus a new account-wide memory scope
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.274.
Presence across releases
0The miner has never read a build containing this name. It is here because a changelog entry of ours names it, which is evidence that it existed and not evidence of which releases carried it. The inventory starts at v2.1.138 and everything older than that was never mined.
First cited
0No release's published evidence quotes this name. The ledger indexes the Evidence lines of every changelog on this site, so this says nobody here has ever quoted it; it says nothing about how old the name is.
Gate readings
0No release here has a gate table behind it for this flag. Most published releases have none at all: the readings exist only for versions the pipeline captured flag state on.
Names beside it
Every feature flag in the inventory starting tengu_team_mem, up to twelve of them.
tengu_team_mem_conflict_recoveredShared memory conflict notices now distinguish a write that never saw the shared copy. never mined
tengu_team_mem_foreign_partition_recoveredShared team memory mounts stop clobbering each other and switch back on once a conflict clears. never mined
tengu_team_mem_multistore_syncYou now get told when a memory file is too big to sync to shared memory. never mined
tengu_team_mem_push_delete_deferredTeam memory sync can now skip an individual refused file without breaking the whole sync, and reports how many files were refused never mined
tengu_team_mem_push_suppressedFailed memory pushes no longer stay suppressed for your whole session; retries resume normally. never mined
Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the feature flag does. All feature flags.