Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Team MemoryArea: what it touches
Internal ChangesKind: in v2.1.275,
Internal ChangesSection of the release
Unclear The tengu_memory_bulk_inflate gate is unread, so nothing can be said about whether it is active.
What
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.
Why
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.
Read from
Feature flag
tengu_memory_bulk_inflateNot enough to say
Nothing 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.
