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.246 Home All releases olderv2.1.245 v2.1.247newer
Claude Code v2.1.246

Memory store errors say "available" instead of "connected"

You'll notice
Useful2 Signal2
Memory

Memory store errors now say no store is available and list the ids you can use.

What

There is no longer a connecting state when resolving a memory store. A session with no store bound says none is available, an unknown store id lists the ids you can use, and a personal id used where a project one is expected is rejected as unknown.

Details
  • Read-only stores still list the ids you can write to.
  • The resolver returns the store together with its backend instead of building one on the spot.
Evidence

No memory store is available in this session.

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.246 →