What it is
Replacing a stale daemon lock now reports the proof type, holder age and whether it ran a different version.
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.257.
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_daemon_stale_lock_replaced was v2.1.257, 1 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_daemon, up to twelve of them.
tengu_daemon_controlNo description from anybody. v2.1.138
tengu_daemon_installNo description from anybody. v2.1.138
tengu_daemon_refuse_stale_upgradeNo description from anybody. v2.1.203
tengu_daemon_startup_crashThe background daemon now restores Cloud gateway sign-in early at startup v2.1.138
tengu_daemon_upgrade_defer_busyThe background service waits for your turn to finish before restarting for an upgrade. v2.1.248
tengu_daemon_upgrade_deferred_busyThe background service waits for your turn to finish before restarting for an upgrade. never mined
tengu_daemon_upgrade_respawn_unreachableNo description from anybody. v2.1.203
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.