tengu_curious_tower
A Claude Code feature flag, read out of the shipped bundle. It has been in the build since v2.1.265, including the newest one read.
New gated 'tether' system can thread API requests together server-side instead of resending full context each turn
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.265.
In the changelogs
2Releases whose published page names tengu_curious_tower.
-
v2.1.265
New "tether" request-threading protocol for API continuity (gated, off by default)
New gated 'tether' system can thread API requests together server-side instead of resending full context each turn
gate cited by this entry, found in this entry's text
-
v2.1.265
New telemetry: tether decision/outcome/echo-audit events
New telemetry events track the tether feature's threading decisions, outcomes, and echo audits
gate cited by this entry
Gate readings
1| Release | Resolved | This account | Anonymous | Compiled default |
|---|---|---|---|---|
| v2.1.265 | 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
15| Read as | Reading | From | Until | Version installed |
|---|---|---|---|---|
| this account | on | 2026-09-17T01:00:06Z | 2026-09-23T09:25:04Z | v2.1.274 to v2.1.280 |
| anonymous | on | 2026-09-17T00:50:04Z | 2026-09-23T09:25:04Z | v2.1.274 to v2.1.280 |
| this account | off | 2026-09-15T15:25:04Z | 2026-09-17T00:50:04Z | v2.1.272 to v2.1.274 |
| anonymous | off | 2026-09-16T22:35:04Z | 2026-09-17T00:35:04Z | v2.1.273 to v2.1.274 |
| anonymous | off | 2026-09-15T14:55:05Z | 2026-09-16T21:50:04Z | v2.1.272 to v2.1.273 |
| this account | on | 2026-09-12T19:15:05Z | 2026-09-15T15:15:04Z | v2.1.269 to v2.1.272 |
| anonymous | on | 2026-09-11T19:55:04Z | 2026-09-15T14:35:05Z | v2.1.269 to v2.1.272 |
| this account | off | 2026-09-12T19:13:54Z | 2026-09-12T19:13:54Z | v2.1.270 |
| this account | on | 2026-09-11T21:00:07Z | 2026-09-12T18:15:04Z | v2.1.269 |
| this account | off | 2026-09-11T20:55:57Z | 2026-09-11T20:55:57Z | v2.1.269 |
| this account | on | 2026-09-10T22:50:04Z | 2026-09-11T20:15:07Z | v2.1.268 to v2.1.269 |
| anonymous | off | 2026-09-08T21:35:04Z | 2026-09-11T19:35:04Z | v2.1.265 to v2.1.269 |
| this account | off | 2026-09-10T21:47:12Z | 2026-09-10T21:47:12Z | v2.1.268 |
| this account | no longer carried | 2026-09-10T21:46:45Z | 2026-09-10T21:46:45Z | v2.1.268 |
| this account | off | 2026-09-08T21:55:04Z | 2026-09-10T17:40:05Z | v2.1.265 to v2.1.267 |
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
1The earliest release whose published evidence quoted tengu_curious_tower was v2.1.265, 8 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
15One 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.