{"version":"2.1.71","anchor":"team-memory-shared-persistent-knowledge","canonical_anchor":"team-memory-shared-persistent-knowledge","heading":"Team Memory (Shared Persistent Knowledge)","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.71\/e\/team-memory-shared-persistent-knowledge","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.71","markdown":"### Team Memory (Shared Persistent Knowledge)\n\n**What**\n\nA new shared memory system that syncs learned context across all team members who work in the same project, enabling Claude to build up organizational knowledge over time.\n\nUsage: Claude automatically manages team memory. Users can say:\n\n- \"Remember this for the team\" \u2014 saves to team memory\n- \"Remember this\" \u2014 saves to private user memory\n- Team memories are stored in `.claude\/team\/` and synced via the cloud\n\n**Details**\n\n- Two-tier memory system: **private** (per-user, persists across conversations) and **team** (shared, synced across the organization)\n- Team memory is synced at session start via an API endpoint and pushed after local changes\n- Memories use a frontmatter format with `name:` and `description:` fields, stored as individual `.md` files with a `MEMORY.md` index\n- Secret detection prevents accidentally syncing credentials, API keys, or tokens to team memory\n- Path traversal protection (`PathTraversalError`) prevents malicious file paths from escaping the memory directory\n- Requires OAuth authentication; team memory sync uses ETag-based caching to minimize bandwidth\n- Conflict resolution with retries when multiple team members push simultaneously\n- The UI shows real-time status indicators like \"Recalled 2 team memories\" or \"Writing 1 team memory\"\n\n**Evidence**\n\nTeam memory sync infrastructure (search for `\"team-memory-sync: fetched successfully\"`) \u2014 `gi8` at line ~460253. Memory instructions (search for `\"team: memories that are shared\"`)\n\n**Status**\n\nGated by `tengu_herring_clock` feature flag \u2014 may be gradually rolling out.\n\n- Flag `tengu_herring_clock`: Off in both readings (read for one account on one subscription tier against v2.1.71; this account: off, anonymous baseline: off, compiled default: no gate table built for this version) 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."}