What it is
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.
Presence across releases
0The miner has never read a build containing this name. It is here because a changelog entry of ours names it, which is evidence that it existed and not evidence of which releases carried it. The inventory starts at v2.1.138 and everything older than that was never mined.
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.
Gate readings
0No release here has a gate table behind it for this flag. Most published releases have none at all: the readings exist only for versions the pipeline captured flag state on.
Names beside it
Every feature flag in the inventory starting tengu_tether, up to twelve of them.
tengu_tether_decisionNew gated 'tether' system can thread API requests together server-side instead of resending full context each turn never mined
tengu_tether_echo_auditNew telemetry events track the tether feature's threading decisions, outcomes, and echo audits never mined
tengu_tether_unrecognised_400Claude Code added a new telemetry event, tengu_tether_unrecognised_400, for the thread-continuation system never mined
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.