Whether org memory loads is now decided in one place, driven by a kill-switch variable and a setting.
tengu_haze_glass Off in both readingsThe 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.223: 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.223. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
The org-memory kill switch, setting and gate are now evaluated in a single shared place rather than as repeated per-call checks.
- the stack of "gates_closed" checks in the memory sync path was removed in favour of shared predicates
- the inputs are
CLAUDE_CODE_DISABLE_ORG_MEMORY, theorgMemoryReadsetting, and thetengu_haze_glassgate
CLAUDE_CODE_DISABLE_ORG_MEMORY
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.219
Org memory no longer auto-selects a lone candidate store
Both mention disable
-
v2.1.224
Artifact kill switch now applies to more artifact paths
Both mention disable
-
v2.1.228
Artifact is disabled by its own switch, not the Workflows one
Both mention disable