{"version":"2.1.219","anchor":"background-sessions-no-longer-respawn-when-the-running-one-i","canonical_anchor":"background-sessions-no-longer-respawn-when-the-running-one-i","heading":"Background sessions no longer respawn when the running one is newer","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219\/e\/background-sessions-no-longer-respawn-when-the-running-one-i","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219","markdown":"### Background sessions no longer respawn when the running one is newer\n\nBackground sessions stop needlessly restarting when your running build is already newer.\n\n**What**\n\nBackground session adoption compares the recorded session's cliVersion against the running build and skips the upgrade respawn when the running session is already newer, instead of treating any version difference as stale.\n\n**Details**\n\n- affects both background session adoption and the upgrade-respawn path\n- a version mismatch alone is no longer sufficient to force a respawn\n- applies to everyone\n\n**Evidence**\n\n`tengu_bg_adopt_upgrade_respawn`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}