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
HomeReleasesv2.1.238entry #20

Claude Code v2.1.238 ·

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

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

You'll notice Nothing to try yet In Development
JSON All of v2.1.238
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
MemoryArea: what it touches
In DevelopmentKind: in v2.1.238,
What probably matters to youSection of the release

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

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.

Read from
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: off

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: off

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: off

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 has happened since
Flag reading moved The flag server now returns off for tengu_haze_glass, 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_haze_glass, 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 →

How sure we are
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: tengu_linen_orbit

See this entry in the whole of v2.1.238 →

Feedback