{"version":"2.1.267","anchor":"teampersonal-memory-sync-org-memory-connected-mode-gains-a","canonical_anchor":"teampersonal-memory-sync-org-memory-connected-mode-gains-a","heading":"Team\/personal memory sync: org-memory connected mode gains an active picker mount check","tier":"internal","area":"Memory Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/teampersonal-memory-sync-org-memory-connected-mode-gains-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Team\/personal memory sync: org-memory connected mode gains an active picker mount check\n\nMemory sync now also checks whether another process already owns the local memory endpoint before reporting the org-memory picker as ready\n\n**What**\n\nWhen `CLAUDE_MEMORY_STORES` isn't set, Claude Code's memory-store watcher now runs an extra check before firing the event that marks the org-memory picker as mounted, replacing a differently-named check it used before. Alongside store discovery, a new asynchronous check also runs to detect whether another process already owns the local memory endpoint, reported as `ownEndpointShadowed`.\n\n**Why**\n\nThis helps Claude Code avoid telling the interface the org-memory picker is ready when it isn't, and lets it notice when a different process is already using the local memory endpoint it would otherwise rely on.\n\n- Area: Memory Sync\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}