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.238 Home All releases olderv2.1.237 v2.1.239newer
Claude Code v2.1.238

The memory-tools gate was renamed, so everyone is back on file-based memory

You'll notice
Useful3 Signal4
Memory

The memory-tools switch was renamed, resetting any rollout, so everyone is back on file-based memory.

The gate moved from one name to another, both defaulting off, with organization memory needing a second flag that is also off.

Feature flag
tengu_stone_shell 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.238: on

tengu_linen_orbit Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.238: on

tengu_haze_glass 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.238: on

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

What

The flag deciding whether Claude Code uses file-based memory or the newer memory tools changed name from tengu_stone_shell to tengu_linen_orbit, both defaulting to off. Renaming resets whatever rollout the old name carried, so without a new server value every install is on file-based memory. The organization-memory variant needs a second flag, tengu_haze_glass, also off by default.

Details
  • The decision is now latched per session: the first time it is resolved it is recorded, so the memory shape cannot change mid-session.
  • The committing form of the resolver is called at two memory entry points in this build.
  • If auto-memory is unavailable the resolver returns file-based memory immediately, without consulting the flag.
Evidence

tengu_linen_orbit

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