tengu_typed_koala
A Claude Code feature flag, read out of the shipped bundle. It has been in the build since v2.1.275, including the newest one read.
Team memory sync now holds onto local-only files instead of dropping them when its sync record is broken
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.275.
In the changelogs
5Releases whose published page names tengu_typed_koala.
-
v2.1.277
Multi-store-sync's empty-receipt handling loses its tengu_typed_koala gate and moves inline
Clearing a stale empty store receipt before syncing no longer depends on the tengu_typed_koala flag
gate cited by this entry, found in this entry's text
-
v2.1.275
Team memory sync can now hold local-only files through a broken manifest instead of dropping them
Team memory sync now holds onto local-only files instead of dropping them when its sync record is broken
gate cited by this entry
-
v2.1.275
Team-memory multistore sync gains a new basis-materialization step and richer telemetry
Team-memory multi-store sync gains a new materialization step and more detailed sync telemetry
gate cited by this entry
-
v2.1.275
New tengu gates: tengu_typed_koala, tengu_zinc_harbor, tengu_tranquil_crescent
Claude Code adds three new internal feature gates: typed_koala, zinc_harbor, tranquil_crescent
gate cited by this entry, found in this entry's text
-
v2.1.275
New gate tengu_typed_koala, defaults on, gates a string-comparison helper
A new internal check flags any non-empty string value other than 'empty_store'
gate cited by this entry, found in this entry's text, named in this entry
Gate readings
2| Release | Resolved | This account | Anonymous | Compiled default |
|---|---|---|---|---|
| v2.1.277 read on another version | On for this account, and not off by default | on | on | on |
| v2.1.275 read on another version | On for this account, and not off by default | on | on | on |
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
4| Read as | Reading | From | Until | Version installed |
|---|---|---|---|---|
| anonymous | on | 2026-10-17T05:30:04Z | 2026-11-06T13:15:04Z | v2.1.302 to v2.1.318 |
| this account | on | 2026-09-15T15:25:04Z | 2026-11-06T13:15: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-15T15:15:04Z | 2026-10-17T05:10:04Z | v2.1.272 to v2.1.302 |
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_typed_koala was v2.1.275, 17 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
41One 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.