What it is
New startup telemetry tracks managed-config readiness and an optional live identity check
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.269.
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
1The earliest release whose published evidence quoted tengu_managed_config_ready was v2.1.269, 11 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.
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_managed, up to twelve of them.
tengu_managed_settings_loadedManaged settings logging now records which admin config tiers applied and whether env union was opted out. never mined
tengu_managed_settings_os_readReading administrator-set settings now records how the OS policy lookup went. never mined
tengu_managed_settings_security_dialog_shownThe managed-settings security consent dialog retries on another surface before giving up. never mined
tengu_managed_settings_validation_errorsManaged-settings startup output now separates non-error notices from actual errors 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.