tengu_stone_shell
A Claude Code feature flag, read out of the shipped bundle. It was in the build from v2.1.212 and was gone by v2.1.286.
Rewritten memory rules would make Claude save corrections and environment quirks immediately, before replying.
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.219.
In the changelogs
10Releases whose published page names tengu_stone_shell.
-
v2.1.286
A server-controlled switch is now locked off in code
A check that used to ask the server whether to turn on a feature now always answers off, so no server setting can switch it on
gate cited by this entry, found in this entry's text
-
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.
gate cited by this entry, found in this entry's text
-
v2.1.232
Two feature decisions moved onto the shared process config object
The memory prompt variant and the skill-suggestion rollout are now fields on the process config.
gate cited by this entry, found in this entry's text
-
v2.1.224
An auto-generated index of your memory files
Claude can auto-generate an index of your memory files and feed it in as a source.
gate cited by this entry, found in this entry's text
-
v2.1.219
Rewritten memory system prompt
Rewritten memory rules would make Claude save corrections and environment quirks immediately, before replying.
gate cited by this entry, found in this entry's text
-
v2.1.219
Memory subagent's delete permission narrowed
The memory cleanup agent could only delete plain memory files, never anything with flags or outside the folder.
gate cited by this entry, found in this entry's text
-
v2.1.219
Memory truncation warning now covers ordinary memory files
Oversize memory warnings would finally say something sensible about ordinary files, not just index entries.
gate cited by this entry, found in this entry's text
-
v2.1.219
Compact recall/remember summaries in the transcript
Memory recall notes could show as a compact grouped line in normal sessions, but that view is off.
gate cited by this entry, found in this entry's text
-
v2.1.219
Pinned memories are injected into the session
Adding
pinned: trueto a memory file's frontmatter would apply it to every session automatically.gate cited by this entry, found in this entry's text
-
v2.1.212
Persistent File-Based Memory (tengu_stone_shell) [Gradual Rollout]
gate cited by this entry, found in this entry's text
Gate readings
6| Release | Resolved | This account | Anonymous | Compiled default |
|---|---|---|---|---|
| v2.1.286 read on another version | Off in both readings | off | off | not a boolean we can read |
| v2.1.238 | Off in both readings | off | off | off |
| v2.1.232 read on another version | Off in both readings | off | off | off |
| v2.1.224 read on another version | Off in both readings | off | off | off |
| v2.1.219 read on another version | Off in both readings | off | off | off |
| v2.1.212 read on another version | Off in both readings | off | off | off |
Two arms, because they disagree: this account is the one account this site reads and anonymous is a baseline with no identity attached. A reading says nothing about your account, and off cannot rule out a rollout both readings sit outside of. What these readings can and cannot show.
Flag server, over time
12| Read as | Reading | From | Until | Version installed |
|---|---|---|---|---|
| anonymous | off | 2026-10-17T05:30:04Z | 2026-10-22T19:05:05Z | v2.1.302 to v2.1.308 |
| this account | off | 2026-09-10T21:47:12Z | 2026-10-22T19:05:05Z | v2.1.268 to v2.1.308 |
| anonymous | no longer carried | 2026-10-17T05:25:57Z | 2026-10-17T05:25:57Z | v2.1.302 |
| anonymous | off | 2026-08-19T04:25:04Z | 2026-10-17T05:10:04Z | v2.1.233 to v2.1.302 |
| this account | no longer carried | 2026-09-10T21:46:45Z | 2026-09-10T21:46:45Z | v2.1.268 |
| this account | off | 2026-09-08T20:36:15Z | 2026-09-10T17:40:05Z | v2.1.263 to v2.1.267 |
| this account | no longer carried | 2026-09-08T20:34:58Z | 2026-09-08T20:34:58Z | v2.1.265 |
| this account | off | 2026-09-06T02:40:05Z | 2026-09-08T18:45:05Z | v2.1.261 to v2.1.263 |
| this account | no longer carried | 2026-09-06T02:36:19Z | 2026-09-06T02:36:19Z | v2.1.263 |
| this account | off | 2026-08-14T22:10:05Z | 2026-09-06T01:55:04Z | v2.1.232 to v2.1.261 |
| anonymous | no longer carried | 2026-08-19T04:20:14Z | 2026-08-19T04:20:14Z | v2.1.233 |
| anonymous | off | 2026-08-14T22:10:05Z | 2026-08-19T03:45:04Z | v2.1.232 to v2.1.233 |
One row per unbroken stretch of one reading, newest first, from snapshots taken every twenty-five minutes or so. No longer carried is not off: it means the flag server stopped returning the gate at all, which is what a retired experiment looks like. The version column is what was installed when the reading was taken, not what caused it.
First cited
2The earliest release whose published evidence quoted tengu_stone_shell was v2.1.212, 16 Jul 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.
Presence across releases
2Build by build
85One row per release since the first build this name was read out of. Absent means the build was read and the name was not in it, never mined means no bundle for that release was ever archived, and a declared type or a default is only ever what that release's own bundle stated.
Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the feature flag does. All feature flags.