Team memory bulk-inflate telemetry now only fires for non-account memory, plus a new bail-out
The 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.
This narrows telemetry to the cases it's meant to cover and avoids continuing a bulk-inflate operation on data that can't be trusted.
tengu_memory_bulk_inflate Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · 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
The `tengu_memory_bulk_inflate` gate is unread, so nothing can be said about whether it is active.