tengu_wild_tome
A Claude Code feature flag, read out of the shipped bundle. It has been in the build since v2.1.271, including the newest one read.
Memory extraction gets a new 'relayFork' execution mode, off by default
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.271.
In the changelogs
7Releases whose published page names tengu_wild_tome.
-
v2.1.318
Forked agents can be given a fixed effort level and close their own REPL sessions
Forked agents can now be started with a pinned effort level, and their REPL session is closed when they finish if a check allows it
gate cited by this entry
-
v2.1.286
Forked agents can swap individual tools and share a retry budget
Forked agents can now replace some of the main conversation's tools with altered copies and receive a count of API attempts left
gate cited by this entry
-
v2.1.283
Forked agents can report output as it streams
Forked agents can now pass on each piece of streamed output as it arrives, and are labelled as a worker by default for memory
gate cited by this entry
-
v2.1.281
Compaction forks carry a new advisorStripPlan
Compaction and other side runs now pass an
advisorStripPlanalongside the existingthinkingStripPlangate cited by this entry
-
v2.1.273
Teleport relay extended to forked (subagent) queries
The teleport relay mechanism now also handles forked (subagent) queries, not just the main thread
gate cited by this entry
-
v2.1.273
Forked-agent relay eligibility gated by tengu_wild_tome (default off)
A new flag decides if a forked agent's query is eligible for the teleport relay, based on the tengu_wild_tome setting
gate cited by this entry, found in this entry's text
-
v2.1.271
Memory-extraction forked query gets a new 'relayFork' mode, off by default
Memory extraction gets a new 'relayFork' execution mode, off by default
gate cited by this entry, found in this entry's text
Gate readings
6| Release | Resolved | This account | Anonymous | Compiled default |
|---|---|---|---|---|
| v2.1.318 read on another version | Off by default, switched on for this account | on | on | off |
| v2.1.286 read on another version | Off by default, switched on for this account | on | on | off |
| v2.1.283 read on another version | Off by default, switched on for this account | on | on | off |
| v2.1.281 read on another version | Off by default, switched on for this account | on | on | off |
| v2.1.273 read on another version | Off by default, switched on for this account | on | on | off |
| v2.1.271 read on another version | Not enough to say | no value returned | no value returned | 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
6| Read as | Reading | From | Until | Version installed |
|---|---|---|---|---|
| anonymous | on | 2026-10-17T05:30:04Z | 2026-11-06T13:45:04Z | v2.1.302 to v2.1.318 |
| this account | on | 2026-09-15T16:00:07Z | 2026-11-06T13:45:04Z | v2.1.272 to v2.1.318 |
| anonymous | no longer carried | 2026-10-17T05:25:57Z | 2026-10-17T05:25:57Z | v2.1.302 |
| anonymous | on | 2026-09-15T16:05:05Z | 2026-10-17T05:10:04Z | v2.1.272 to v2.1.302 |
| anonymous | off | 2026-09-15T14:35:05Z | 2026-09-15T16:00:07Z | v2.1.272 |
| this account | off | 2026-09-15T15:25:04Z | 2026-09-15T15:55:04Z | v2.1.272 |
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_wild_tome was v2.1.271, 14 Sep 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
1Build by build
45One 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.