{"version":"2.1.323","anchor":"background-sessions-held-back-from-stale-version-respawn-whe","canonical_anchor":"background-sessions-held-back-from-stale-version-respawn-whe","heading":"Background sessions are not restarted when your sign-in setup has changed","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/background-sessions-held-back-from-stale-version-respawn-whe","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Background sessions are not restarted when your sign-in setup has changed\n\nClaude Code no longer restarts or upgrades an outdated background session when its sign-in settings differ from your current ones\n\n**What**\n\nClaude Code can run sessions in the background in a separate process. When that process is from an older version, Claude Code normally restarts it on the new version. Now Claude Code first compares the sign-in environment variables (settings passed to a program when it starts) the background process was started with against the current ones. On Linux and WSL it reads these from the running process.\n\nIf they differ:\n\n- the outdated background session is not restarted\n\n- a background session Claude Code has taken over is not upgraded automatically\n\n- Claude Code records that the restart was held back\n\nThis is controlled by a remotely managed switch.\n\n**Why**\n\nAn upgrade restart could otherwise move a background session onto a different account or profile without you noticing.\n\n- Flag `tengu_tethered_buoy`: Not enough to say (read for one account on one subscription tier against v2.1.323; this account: no value returned, anonymous baseline: no value returned, compiled default: on) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}