{"version":"2.1.281","anchor":"memory-tools-mode-can-now-turn-on-while-the-org-memory-pol","canonical_anchor":"memory-tools-mode-can-now-turn-on-while-the-org-memory-pol","heading":"Org memory policy check gains a 'held' state while the verdict loads","tier":"soon","area":"Memory","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/memory-tools-mode-can-now-turn-on-while-the-org-memory-pol","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Org memory policy check gains a 'held' state while the verdict loads\n\nThe organization memory sync check can now be open, closed or held, and tools-based memory mode no longer waits for the policy verdict to load\n\n**What**\n\nOrganization memory lets memory be synced for a team rather than kept only on one machine. The check that decides whether it is allowed used to answer only yes or no. It now has three states: `open`, `closed` and `held`. `held` means the organization's policy verdict has not arrived yet. `open` is returned only when the policy permits `allow_memory_sync`.\n\n- The memory watcher, which starts syncing, now waits for the verdict before it starts. It stays off when HIPAA evidence or another problem means no verdict can be obtained. The `allow_memory_sync` policy is denied under HIPAA and zero data retention (ZDR) arrangements.\n\n- Memory has a 'tools' mode and a 'files' mode. The choice now also picks tools mode whenever the policy state is anything but `closed`, including while it is still `held`. Before, tools mode needed `allow_memory_sync` up front, so it can now start before the verdict loads. The `tengu_linen_orbit` switch can still turn tools mode on as before.\n\n- The discovery of synced project memory now returns quietly when the state is `held`, instead of logging that the gates are closed.\n\nThe policy check itself depends on the `tengu_haze_glass` flag and on `CLAUDE_CODE_DISABLE_ORG_MEMORY` being unset. `CLAUDE_MEMORY_STORES` is also part of the discovery chain.\n\n**Why**\n\nIn practice, organizations where synced memory is being rolled out can get tools-based memory without waiting for the policy verdict, and sync does not start until that verdict is known. Setting `CLAUDE_CODE_DISABLE_ORG_MEMORY` still turns the organization memory check off.\n\n- Flag `tengu_linen_orbit`: Not enough to say (read for one account on one subscription tier against v2.1.281; this account: no value returned, anonymous baseline: no value returned, compiled default: 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.\n- Flag `tengu_haze_glass`: Off in both readings (read for one account on one subscription tier against v2.1.281; this account: off, anonymous baseline: off, compiled default: 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.\n- Area: Memory\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}