{"version":"2.1.323","anchor":"background-worker-no-longer-auto-restarts-after-a-settled-cr","canonical_anchor":"background-worker-no-longer-auto-restarts-after-a-settled-cr","heading":"Background sessions waiting for sign-in are no longer restarted after a crash","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/background-worker-no-longer-auto-restarts-after-a-settled-cr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Background sessions waiting for sign-in are no longer restarted after a crash\n\nA background session that crashes while held waiting for sign-in now stays crashed instead of being restarted\n\n**What**\n\nA background session is a Claude Code session that keeps running on its own. When one crashes, Claude Code can restart it. It already skipped the restart for a session held waiting on a gateway. It now also skips it for a session held waiting for sign-in: that session is marked as crashed and left alone.\n\nStarting a session also clears any sign-in it previously adopted, and one more kind of exit before startup finishes is now handled.\n\n**Why**\n\nA background session waiting for you to log in is no longer restarted over and over.\n\n- Flag `tengu_bg_settled_crash_restart`: 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: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}