Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.219 ·

Org memory no longer auto-selects a lone candidate store

When only one org memory store is found, it is no longer picked for you automatically.

You'll notice No documentation found Improvements
JSON All of v2.1.219
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
MemoryArea: what it touches
ImprovementsKind: in v2.1.219,
ImprovementsSection of the release
What

Discovery finding exactly one candidate memory store no longer silently selects it; the choice is left to you.

Details
  • Three call sites that auto-set the store when a single candidate existed (onlyIfAbsent) were removed, and the helper is gone from the build.
  • Discovery still records org_memory_discovery telemetry and populates the candidate list.
  • Org memory overall still requires the tengu_haze_glass gate and respects CLAUDE_CODE_DISABLE_ORG_MEMORY.
Evidence

org_memory_discovery

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Feature flag
tengu_haze_glass Off in both readings

The flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.

This account: off · anonymous baseline: off · compiled default in v2.1.219: off

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.219. It isn't a statement about your account. What a flag value here can and cannot tell you

What has happened since
Flag reading moved The flag server now returns off for tengu_haze_glass, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns nothing at all, having stopped carrying it for tengu_haze_glass, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.

See this across every release →

See this entry in the whole of v2.1.219 →

Feedback