{"version":"2.1.275","anchor":"team-memory-bulk-inflate-telemetry-now-scoped-to-non-account","canonical_anchor":"team-memory-bulk-inflate-telemetry-now-scoped-to-non-account","heading":"Team memory bulk inflate telemetry now scoped to non-account memory","tier":"internal","area":"Team Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/team-memory-bulk-inflate-telemetry-now-scoped-to-non-account","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Team memory bulk inflate telemetry now scoped to non-account memory\n\nTeam memory bulk-inflate telemetry now only fires for non-account memory, plus a new bail-out\n\n**Unclear.** The `tengu_memory_bulk_inflate` gate is unread, so nothing can be said about whether it is active.\n\n**What**\n\nThe team-memory bulk-inflate process (which loads memory data in bulk) now exits early when `rejoinWalkUntrusted` is set and its basis data is unusable. Its failure and incomplete-run telemetry event, `team_memory_multistore_bulk_inflate`, now only fires when the memory scope is not `account`.\n\n**Why**\n\nThis narrows telemetry to the cases it's meant to cover and avoids continuing a bulk-inflate operation on data that can't be trusted.\n\n- Flag `tengu_memory_bulk_inflate`: Not enough to say (read for one account on one subscription tier against v2.1.275; this account: no value returned, anonymous baseline: no value returned, 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: 1\/5\n- Signal: 1\/5"}