Source Intelligence

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

All of v2.1.71 Home All releases olderv2.1.70 v2.1.72newer
Claude Code v2.1.71

Team Memory (Shared Persistent Knowledge)

Feature flag
tengu_herring_clock 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.71: 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.

Read once, for one account on one subscription tier, against v2.1.71. It isn't a statement about your account. What a flag value here can and cannot tell you

What

A 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.

Usage: Claude automatically manages team memory. Users can say:

  • "Remember this for the team" — saves to team memory
  • "Remember this" — saves to private user memory
  • Team memories are stored in .claude/team/ and synced via the cloud
Details
  • Two-tier memory system: private (per-user, persists across conversations) and team (shared, synced across the organization)
  • Team memory is synced at session start via an API endpoint and pushed after local changes
  • Memories use a frontmatter format with name: and description: fields, stored as individual .md files with a MEMORY.md index
  • Secret detection prevents accidentally syncing credentials, API keys, or tokens to team memory
  • Path traversal protection (PathTraversalError) prevents malicious file paths from escaping the memory directory
  • Requires OAuth authentication; team memory sync uses ETag-based caching to minimize bandwidth
  • Conflict resolution with retries when multiple team members push simultaneously
  • The UI shows real-time status indicators like "Recalled 2 team memories" or "Writing 1 team memory"
Evidence

Team memory sync infrastructure (search for "team-memory-sync: fetched successfully") — gi8 at line ~460253. Memory instructions (search for "team: memories that are shared")

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

Status

Gated by tengu_herring_clock feature flag — may be gradually rolling out.

See this entry in the whole of v2.1.71 →