Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.308 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.198 ·

Memory Stores Env Var

Entry
JSON All of v2.1.198
EntryKind: in v2.1.198,
New FeaturesSection of the release
What

A new CLAUDE_MEMORY_STORES environment variable activates expanded memory storage, alongside the tengu_moth_copse feature flag.

Usage
export CLAUDE_MEMORY_STORES="..."
Details
  • Feature-flagged via tengu_moth_copse; setting that flag OR providing a non-empty CLAUDE_MEMORY_STORES value enables the multi-store subsystem (qat() returns true in either case)
  • The env var accepts a JSON array; each element is either a bare path string or an object with fields: path (absolute, required), mode ("rw" | "ro", default "rw"), scope ("user" | "team", default "team"), mount (optional alphanumeric name auto-derived from the last path segment if omitted), promptIndex (optional relative path), promptIndexMaxBytes (optional integer)
  • Validation is strict: the JSON must parse cleanly, all paths must be absolute and must not override the host, mount names must match /^[A-Za-z0-9_-]+$/, duplicate mount names throw, and only one scope:"user" entry is permitted
  • At startup, successfully parsed stores are logged at debug level: "memory-stores: parsed N store(s): mount(mode), ..."
  • When active, the multi-store router (uL()) supersedes the default single-directory memory path, routing reads and writes to the configured stores based on scope
Evidence

qat() function (search for "CLAUDE_MEMORY_STORES" and tengu_moth_copse flag); eue() parser and zqd schema (search for "CLAUDE_MEMORY_STORES is not valid JSON" and "CLAUDE_MEMORY_STORES has duplicate mount")

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

Read from
Feature flag
tengu_moth_copse 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.198: off

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.198. It isn't a statement about your account. What a flag value here can and cannot tell you

What has happened since
Flag reading moved The flag server now returns off for tengu_moth_copse, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns nothing at all, having stopped carrying it for tengu_moth_copse, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.

See this across every release →

See this entry in the whole of v2.1.198 →

Feedback