tengu_server_classifier_no_result_latched
A Claude Code feature flag, read out of the shipped bundle. No mined inventory carries it: everything below comes from what this site has written about it.
An analytics event, not a feature flag. Claude Code logs it when the server-side auto mode classifier (the arbiter) returns no classification result and auto mode switches to classifying locally for the rest of the session, with the fields isSubagent and reason (the no-result reason such as server_unsupported, or other).
Not Anthropic's. Written by Claude Opus 5.5 from reading the v2.1.286 bundle, and it can be wrong.
In the changelogs
0No changelog entry here has ever named it. That is a statement about what has been written, not about the name: nothing here says which builds carried it either.
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.
First cited
1The earliest release whose published evidence quoted tengu_server_classifier_no_result_latched was v2.1.278, 19 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
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.
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.