{"version":"2.1.248","anchor":"background-daemon-can-retire-a-same-version-instance","canonical_anchor":"background-daemon-can-retire-a-same-version-instance","heading":"Background daemon can retire a same-version instance","tier":"internal","area":"Background Daemon","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/background-daemon-can-retire-a-same-version-instance","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Background daemon can retire a same-version instance\n\nThe background daemon can now retire a same-version instance; build is 2.1.248.\n\n**What**\n\nThe background daemon takeover now folds in an extra caller-supplied condition, so a transient daemon running the same version can be retired instead of being left in place. Build metadata moves to 2.1.248.\n\n**Details**\n\n- Gated by `tengu_bg_binary_takeover`, which falls back to on.\n\n**Evidence**\n\n`tengu_bg_daemon_binary_takeover`\n\n- Flag `tengu_bg_binary_takeover`: Not enough to say (read for one account on one subscription tier against v2.1.248; this account: no value returned, anonymous baseline: no value returned, compiled default: on)\n- Area: Background Daemon\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}