Source Intelligence
Reading a new release v2.1.251 Analysing changes · 2/5 Deeper second pass · 4/5 agents 427 findings $12.75 so far

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.172 Home All releases olderv2.1.170 v2.1.173newer
Claude Code v2.1.172

Team Memory: Two-Step Save Process Instructions

What

The team memory system prompt has been overhauled with clearer, step-by-step guidance for saving memories. When using indexed memory, the instructions now explicitly describe a two-step process (write the memory file, then add a pointer to the index).

Details
  • Step 1: Write memory to its own file using the frontmatter format
  • Step 2: Add a pointer entry (- [Title](file.md) — one-line hook) to the index file
  • Index entries are capped at ~150 characters
  • Clarified that team memory directories already exist — no need to run mkdir
  • Read-only sessions now receive: "If the user asks you to remember something, explain that memory is read-only in this session."
Evidence

New team memory prompt builder (search for "Step 1 — write the memory to its own file in")

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

See this entry in the whole of v2.1.172 →