tengu_concurrent_candle

One 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.

The earliest release whose published evidence quoted tengu_concurrent_candle was v2.1.274, 16 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 above.

Release	Resolved	This account	Anonymous	Compiled default
v2.1.274 read on another version	Off in both readings	off	off	not a boolean we can read

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.

Read as	Reading	From	Until	Version installed
this account	off	2026-09-15T21:00:07Z	2026-09-22T05:45:05Z	v2.1.273 to v2.1.278
anonymous	off	2026-09-15T20:55:04Z	2026-09-22T05:45:05Z	v2.1.273 to v2.1.278

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.

Every feature flag in the inventory starting tengu_concurrent, up to twelve of them.

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.