tengu_stellar_drift
A Claude Code feature flag, read out of the shipped bundle. It has been in the build since v2.1.257, including the newest one read.
Two transcript debugging aids, raw tool inputs and exact wire block order, are computed but each sits behind its own gate.
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.257.
In the changelogs
4Releases whose published page names tengu_stellar_drift.
-
v2.1.281
CLAUDE_CODE_TETHER_LIVE=true now opts in to several related threads/tether features and bypasses first-party checks
CLAUDE_CODE_TETHER_LIVE=truenow also turns on related threads features and skips some endpoint checksgate cited by this entry, found in this entry's text
-
v2.1.281
Stellar-drift and humble-hammock features forced on when the CLAUDE_CODE_TETHER_LIVE opt-in holds
CLAUDE_CODE_TETHER_LIVEcan now force the stellar-drift and humble-hammock features on for first-party usegate cited by this entry, found in this entry's text
-
v2.1.257
Wire-format echo debugging fields (tool inputs + block order) are built but flag-gated off
Two transcript debugging aids, raw tool inputs and exact wire block order, are computed but each sits behind its own gate.
gate cited by this entry
-
v2.1.257
New gated experiment: tengu_stellar_drift
A new capability flag can be forced on with an env var, with no stated effect.
found in this entry's text, gate cited by this entry
Gate readings
1| Release | Resolved | This account | Anonymous | Compiled default |
|---|---|---|---|---|
| v2.1.281 read on another version | Off by default, switched on for this account | on | on | 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
20| Read as | Reading | From | Until | Version installed |
|---|---|---|---|---|
| this account | on | 2026-11-02T13:05:04Z | 2026-11-12T14:10:06Z | v2.1.316 to v2.1.322 |
| anonymous | on | 2026-10-17T05:30:04Z | 2026-11-12T14:10:06Z | v2.1.302 to v2.1.322 |
| this account | off | 2026-11-02T12:55:05Z | 2026-11-02T12:55:05Z | v2.1.316 |
| this account | on | 2026-11-01T20:45:05Z | 2026-11-02T12:40:07Z | v2.1.316 |
| this account | off | 2026-11-01T20:40:05Z | 2026-11-01T20:40:05Z | v2.1.316 |
| this account | on | 2026-11-01T20:25:04Z | 2026-11-01T20:30:06Z | v2.1.316 |
| this account | off | 2026-11-01T20:20:05Z | 2026-11-01T20:20:05Z | v2.1.316 |
| this account | on | 2026-10-07T18:00:12Z | 2026-11-01T19:30:06Z | v2.1.292 to v2.1.316 |
| anonymous | no longer carried | 2026-10-17T05:25:57Z | 2026-10-17T05:25:57Z | v2.1.302 |
| anonymous | on | 2026-09-11T19:55:04Z | 2026-10-17T05:10:04Z | v2.1.269 to v2.1.302 |
| this account | off | 2026-10-07T17:59:34Z | 2026-10-07T17:59:34Z | v2.1.293 |
| this account | on | 2026-09-12T19:15:05Z | 2026-10-07T17:10:05Z | v2.1.269 to v2.1.292 |
| 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
0No release's published evidence quotes this name. The ledger indexes the Evidence lines of every changelog on this site, so this says nobody here has ever quoted it; it says nothing about how old the name is.
Presence across releases
1Build by build
59One 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.